I'm new into SharePoint and I'm facing the following problem.I'm runnig Office SharePoint Server 2007. I created a new Web Application using Central Administration and then restored a backup copy from an old SharePoint site that was hosted with a third party provider. I restored using stsadm.exe -o restore -url. The site was restored successfully but when I go to people and groups and try to find and add users I see the old usernames. I used the stsadm.exe -o migrateuser to migrate the old accounts with the new ones and it worked fine. However, my problem started when trying to add new users that didn't exist in the old SharePoint site. When I try to look users it just displays the old users accounts and I just can't add new users and it always gives me the No exact match was found error.I thought I was doing something wrong in the restroring process so I tested it out by just creating a new web application and then create a site collection. When I tried to add users to the new site collection it didn't find any users. I'm pretty sure I'm missing some configuration to link SharePoint to users Active Directory.Can anyone help me...

Hi, The stsadm -o migrateuser will only update the login name not other properties. You need to modify the user information in the site. 1: Site Settings 2: Under Site Collection Admin select View Site Collection User Information 3: Modify the user information You could also try this: http://yoursharepointsite /_catalogs/users/simple.aspx Delete the old users and add in the new ones. Cheers Geoff

I'm new into SharePoint and I'm facing the following problem. I think you must deploy SharedServices Provider and User Profiles Import from current Active Directory MCTS

This is a forum for questions regarding SharePoint 2010. Your question needs to be asked in the SharePoint 2007 forums.SharePoint 2007 Forums: http://social.technet.microsoft.com/Forums/en-us/category/sharepointBlog: http://sptwentyten.wordpress.com

People Picker get user information directly from active directory and it runs under the credentials of the application pool the site is running in. Make sure the application pool identity is a domain account with the right permissions to query active directory. If not, change the application pool identity to some domain account which can query AD.

Thanks guys, I tried pretty much everything you told me and nothing worked. However, I found the solution to my problem that wasn't very obvious.I used the stsadm -o getsiteuseraccountdirectorypath -url to check the path value and it had the old server UO and DC. I changed this property with the new server information and now it's working like a charm.