SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In the 2010 world, you used to be able to set the SharePoint user property PreferredName to import an Active Directory user property. In 2013, I can still set the property to import from Active Directory and run a full sync to pull the property in, however if I leave it overnight the property reverts to the default (no mapping). I am a bit perplexed as to why this is happening. Has anyone else noticed this behavior?

UPDATE: I have checked the FIM mappings for the User Profile Service (miisclient.exe) and found that the mapping still exists, but SharePoint indicates that there is no mapping. Very perplexing...

share|improve this question
What is the build number of the farm and what property are you setting PreferredName to map to? – Trevor Seward Jun 7 '13 at 21:58
The farm is running the March 2013 Public Update (15.0.4481.1017). I have mapped PreferredName to extensionAttribute1 in the past to get around a naming convention we have in my company. The AD property displayName is of the format "LastName, FirstName" for every user (Outlook Global Address List reasons). My solution was to write a script that checks for and updates each user's extensionAttribute1 to "FirstName LastName" format for SharePoint. – JCardenas Jun 10 '13 at 16:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.