We have noticed that when we change a username in Active Directory (usually due to a marital status change), we run into some issues on the SharePoint side of the house. After we change things in Active Directory we typically wait for a full import/crawl to be done by the Search Services Administration schedules. Once both of those run, the user is able to log into the SharePoint site and have the "welcome" link reflect the new Display Name. However, if we search for the user using People search, it returns the right display name but still tied to the old SAM Account ID. We also have some online forms that utilize an Exchange Address Book lookup. If we look the user up, they show up twice (once as the old Account ID and once as the new Account ID). We have also tried deleting the user object out of the User Profile Service in Central Admin adn out of the "All People" groups. If we allow another import/crawl after that, everything seems to be okay, but the user does not get populated back into the "all Users" SharePoint group (they can log in and access everything they are supposed to).Since we are kind of grasping at straws for an "official" process here, can anyone help us to see if what we are doing is right, wrong, or indifferent? Thanks!Brandon

Whoever has logged in once has an entry in the user list. Remoce from the web application home site > User list.Sara

Whoever has logged in once has an entry in the user list. Remove from the web application home site > User list. Sara

I think you are referring to the "All People" group, which we do remove them from (see above). I have tested some more and found that we do not need to remove them from Central Admin (user profile service) - only the "All People" group (which is in agreement with Sara's comment). My remaining question is how do they get back into the "All People" group? Does it happen automatically or is it triggered by another event (i.e. upload, logging in, etc). Thanks!

We are still seeing some inconsistencies and would love some feedback. Here is our process:1. we change all applicable values in Active Directory and ADSI Edit for the new display name and SAM Account name2. we delete them from the "All People" group (which deletes them from the site collection)3. Allow a full user profile import and people search crawl to happen (in our case overnight)At this point the user logs in and the "Welcome xxxx" link at the top of the page will update to the new display name, however if you look at the settings it still points to the old Account ID. also, if you search for them to add permissions, you see double entries (one for the old account ID and one for the new account ID, but both using the updated Display Name). Finally, they no longer show up in the "All People" group.We have found that if a user does an action in SharePoint (upload a file, check something out, etc) they do show back up in the "All People" group - however the other two problems above still exist. I am going to delete the account from the User Profile database (from Shared Services Administration) - but not sure if that will help, and may be counterproductive if they lose some of the values attached to the user profile (picture URL, About me section, etc). Any ideas? Thanks!Brandon

You may want to cleanup your sharepoint config file:Make sure Timer Job is not running. go toC:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\AFolder select all the xml files and delete.(make sure you don't delete cache.ini.)open cache.ini. change it to 1 and save.Also, I am wondering if this is an Active Directory issue. You may try to open a ticket in the related forum with AD admins.You may consult on how to give a person new name in AD.Then, reperform a cleanup, and full crawl on AD users.Sara

When you are talking about deleting the temp files, which servers do you do that on (we have a back end index server and two front end SharePoint servers that "run" the site). Also, we have disabled the "My Sites" feature (management decision) - could that have any effect on this?All of our testing shows that everything hinges around the "Account" field for the user object (when you look at the user information window). If it has the old account name, the duplicate entry exists. If it updates to the new account name, the duplicate disappears. Everything else seems to work fine with our process (and I don't think it is an Active Directory issue). It has to be caching that information somewhere (which may be the temp files you are referring to). Thanks!

we found that if you delete them out of the site collection after the import crawl everything matches up. Our issue was deleting them out before the import/crawl which tended to cause some minor issues. Our process has been verified and tested several times since this with great success. Thanks for the replies!Brandon

Brandon, so are you saying that all one has to do is delete the user from the "all people" listing after the full import has run? That's it? I've been trying all sorts of things off and on for months.

Oh, never mind, the user isn't listed in "all people"with the bad name OR the correct name. Our "all people" listing seems to mostly contain a profile import from whenwe migrated from 2003 to MOSS 2007. I've tried deleting usersfrom the SSP and then letting the profile importadd them in again, which doesn't work. (Shared Services Administration: MOSSP_SharedServices1 > User Profile and Properties > View User Profiles > Edit User Profile)SharePoint holds on to the old info as far as what it displays to the user. Alternatively, sometimes, for noreason I can tell,the SharePoint user name sometimes corrects itself weeks later - but we run a full profile import every night.Any suggestions would be welcome.

Hello, This worked immediately for us: stsadm -o migrateuser -oldlogin domain\olduser -newlogin domain\newuser –ignoresidhistory (Run on Sharepoint server) It appears that for any name change, getting married changes, even spelling corrections, the SharePoint database will fingerprint the profile with whatever their username when the SharePoint profile is created. After changing it in AD, the display names, email addresses etc... will all look correct but underneath the hood in SharePoint’s database the original wrong Username is still in effect. Lady of the LAN