MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Sync AD/Profile/UserInfo

  Asked By: Ravi    Date: Nov 29    Category: MOSS    Views: 2154

When a user needs a name change (example: she just got married), how
does the new name propogate from Active Directory down to a website's
user information in the Content Database?

I know the MOSS Profiles are synced from AD with a Job from the Shared
Services Provider (Full/Incremental import), which can be scheduled to
run daily, etc.

Should some job sync new Profile info to the Content Database User
Info ?

My problem is that when a name change occurs in AD, it gets to MOSS
profiles, but IS NOT updating the "Welcome" message on her sites.

Any ideas?



7 Answers Found

Answer #1    Answered By: Delilah Mcpherson     Answered On: Nov 29

I don't think it is propagated. You have to go change  their name
everywhere it is used.

Answer #2    Answered By: Gobinda Navalagi     Answered On: Nov 29

Correct. We had that problem  a few times and had to (ahem) modify the
database - which, I have to immediately note, is an unsupported action
by Microsoft. If you need the SQL statements, contact me off-list.

Answer #3    Answered By: Rose Silva     Answered On: Nov 29

The Account Synchronization feature of DeliverPoint will update the User

Answer #4    Answered By: Maegan Ellison     Answered On: Nov 29

Nooo don't do this!

Everytime a user  visits a site in a site collection,
SharePoint 'caches' the user info. This saves a lot of trips to the AD.
When you change  the surname of a user in the AD, the change will
propagate to the profiles, but you won't see the change in the sites.
You will have to go to the "All People" page of the site collection and
DELETE the entry for the specific user; this is the cached user info.
Upon next visit of the user, SharePoint will notice that the info  of
the user is not in the cache and retrieve fresh data, including the

Answer #5    Answered By: Yahaira Shannon     Answered On: Nov 29

Well, but there's a problem  of scale with that solution - if someone
is a member of enough sites, this becomes fairly cumbersome to do for
each..and..every...single...site.... It also puts the burden on the
site admins rather than the system admins to do the updates (which, I
suppose you may be correct, that may be where such a thing belongs,
unless - as in our case - the update request is sent to the help

Correct me if I'm wrong - if you force an update that way, don't you
also lose any document modification information  that's associated with
that user's account? I know that when my account got screwed up
recently, all my document data got reverted to a user  rather
innocently labeled "Person".

Answer #6    Answered By: Doris Leach     Answered On: Nov 29

Note the difference with sites  and Site collections. A site
collection can hold a lot of subsites, which don't cache the user
info each.
In SPS 2003, and likely 2007 as wel, user  info is tracked primarily
by its SID (AD security id), user account and/or email adress
(the "alias" fields). The account itself is not deleted, just cached
info (the All People list is actually a "this-user-visited-this-site-
collection list).
The SID remains the same (if you didn't delete and recreate the
account in AD), and thus you don't loose all document modification
Fingers crossed, because I don't know if changing the email address
may have side-effects.

If you meant sites that are created in a Managed path (eg /sites/),
then yes, you will have to go by the site root site of every site
collection this user has visited...

Answer #7    Answered By: Sumitra 2004     Answered On: Nov 29

I describe this scenario in a couple of different posts for V2 (Still
applies to V3)

I'm not updating  SPUserUtil for V3, but rather we're working on a
similar feature in DeliverPoint

Handling Login Name Changes


Synchronizing Display Names and Email Addresses


Didn't find what you were looking for? Find more on Sync AD/Profile/UserInfo Or get search suggestion and latest updates.