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

Several fields in MOSS profiles are mapped to fields in active directory and we have given the user the ability to modify these.

But when the incremental profile import runs it overwrites these with the old values from active directory.

How do we make it so that AD is updated with the new values from the profile?

Thanks for any suggestions.

share|improve this question

You can either populate the values from AD, Feed (typically BDC) or User.

If you specify that the content is taken from AD but allow the user to edit, then the changes will be overwritten next time SSP syncronizes with AD the changes will be lost. This is per design.

There is no Out Of The Box way of synchronizing the change back to AD (you could also consider if you really want end users to update data in your AD, i would be very carefull about that).


share|improve this answer
Yes, I know there's no out of the box way. But we do really do want our users to be able to update some fields in AD, e.g. their mobile number. – Anonymous Nov 24 '09 at 9:22
well do you need these data other places than in my site? you can just make them User only, so they dont get overwritten. Another way is to store them in an external database and integrate them using BDC. You could then create a front end for the DB where users could add their own information. Accessing the AD directly is possible using C#, but it would require good reasons to do this. – Anders Rask Nov 24 '09 at 11:54

We wrote our own set of controls to take care of this situation. When the user clicks save, we instantly update sharepoint, our hr system, and ad.

share|improve this answer

I agree with Anders on the ootb solution. It's read only or overwrite on update. The first thing I would do would be to mark the fields so that they can't be updated in SharePoint and then allow the users to update them another way. If there is no other way, you might choose not to import those properties from AD anymore.

share|improve this answer

Note: The functionality you want is OOTB in SharePoint 2010.

share|improve this answer

I built a free solution for 2007 and a low cost solution for 2010 called Active Directory Tools For SharePoint. It does exactly what you are referring to and includes password management. 2010 will do this out of the box, but you do have to enable my sites and personalization which many companies just don't want to get into.

You can checkout Active Directory Tools For SharePoint 2010 Here...

share|improve this answer

By default, you can map the fields between AD and SharePoint in either EXPORT or IMPORT mode.

  • EXPORT: Any field set to export will replace the AD field upon next sync. There is no concept of "more recent change".
  • IMPORT: Any field set to import will be replaced by the AD value upon next sync. Anything changed in SharePoint will be replaced.
share|improve this answer

Your Answer


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