Hi, We have a user that has been given a new username, and I have run the STSADM -o migrateuser command, specifying the oldusername and newusername as parameters. When I open one of the sites the user has access to, I can see under Site Permissions that the account has successfully changed from oldusername to newusername. The permissions are also maintained (Full Control). However, when the user tries to log in to this site, he gets the Access denied page. Any idea why this is so?

I wonder if there are some assetts on the page that have rights assigned to the "old" user acct. You might want to try using fiddler or wireshark to monitor what's going on with the page and what exactly is generating the "access denied" issue. The logs will also be your friend here to see what SharePoint is stating around the "access denied".I hope this helps and answers your question-Jeff DeVerter, MCSERackspaceblog:http://www.social-point.comtwitter: http://www.twitter.com/jdeverter

Hi, Does this issue occur after you migrate users between domains or not? What version is your SharePoint server? What about the SP version? Are you using form-based authentication? NTLM or Kerberos? Do you encounter the same issue if you use another user? If you try to use the new username log in SharePoint site, what is the result? If you just want to change a user’s username, you don’t need to run stsadm –o migrateuser command. You can change user’s login name in Active Directory Users and Computers. After that, open your SSP admin site, start incremental import, then click view user profile to check whether the user’s name is changed. Hope this helps. Rock WangRock Wang MSFT

Hi, Thank you for help so far. This is not an isolated case on one site, but all sites the user has access to. So it's definitely related to the user itself, not the front page of the site. We're running MOSS 2007 SP1 with Kerberos authentication. This is the only user encountering this behaviour. When the user tries to access a site he should have access to, the following redirect happens: http://intranet/workspace/teamsite/_layouts/AccessDenied.aspx?Source=http%3A%2F%2Fintranet%2Fworkspace%2Fteamsite%2Fdefault%2Easpx (FYI: the names intranet and teamsite are in this case fictional, and the name workspace is a valid managed path) So far, the only workaround has been deleting the user from the site, and then adding him again.

Hi there, Do you guys know if the migrateuser command works in SP 2010 to move the permissions across moss 2007 to SP 2010? Or is there anyways to move the permissions across domains? Thanks Vishwas Vishwas

Hi Vishwas, If you're doing an upgrade from 2007 to 2010, then the users and their permissions should follow. Changing for example the domain name or usernames in the upgrade scenarion, however, I don't think that is supported. Hope this helps.

Is there any other way to fix access denied issue after running migrateuser powershell command. it is looking like bug in microsoft?? I am really in trouble as we are running migration project of sharepoint 2007 to 2010 we are using both third party migration and Microsoft approach tool. Third party tool do not have any feature to migrate Windows user to claim based user and Microsoft upgrade approach not doing it automatically and when i run the powershell command to migrate Windows user to Claim based then all existing users int this sites getting ' Access Denied' is there any microsoft patch or hotfix been released to fix this issue. it really painful and critical.. URGENT HELP.Vaibhav Jain SharePoint Solution Architect