I recently had to move one of our sites to a different farm and domain. The migration was not a smooth, as I would have liked. After attaching the content db to a fresh site collection and upgrading the database, I kept on getting access denied when I tried logging in. This is after I set myself as a primary site collection admin, adding my account to the user policy to have full control and operate as system, and updated my domain login for all the site collection groups. What ended up being the problem was with the superuser and reader account not being set. I did check the old farm and the superuser accounts were not set there either, but I never had the login problem on the old farm. Would any of you know why I would of ran into this problem on the new farm/domain?
Yes, they are blanked when I checked the properties on the old farm. Unless that means it’s set to the local system account or some default account.
Hi Anthony,
I had problems with this as well recently, but mine was a bit worst. It would work after an iisreset.. but stop working every night.
Took me a while to find out the problem was, someone set NTL Superuser/reader accounts on a claim based Webapp….
Are you sure they weren’t set on the old farm? you can find out like this:
$w = Get-SPWebApplication http://sitename
$w.Properties
