SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is a slightly unusual situation. I have a MOSS 2007 farm. I do a database backup and restore to our dev farm and then do a database attach to our 2010 farm.

I'm secondary site collection secondary admin on all the site collections in the MOSS farm, and if I go to Central Admin on the 2010 farm, I'm still secondary site collection admin, according to CA. However if I navigate to the site I get permission denied. The fix is to go through central admin>Site Collection Adminsitrators and hit OK on each page, which seems a bit odd for me.

I've tried assigning myself site collection admin in powershell and, although I can change who's listed as the site collection admins, it has no effect until I go into Central Admin and hit OK.

Which is all a bit confusing, have I missed something?

share|improve this question
After some reflection and exploration I've decided that it's best to go around this likley bug than though it. What I did was go to the web application in Central Admin and edited the Uer Policy to add myself with full control over everything on the web application. – Dan May 30 '11 at 7:25
Is your new Web Application a claims based one? – Wictor Wilen MCA MCM MVP May 30 '11 at 8:23
Yes, but the web application isn't new. It's just sitting there waiting for me to do a database attach. – Dan Jun 2 '11 at 9:23
up vote 1 down vote accepted

You need to migrate the users from classic to claims notation. Read the "Upgrade Notes" in Bill Baer's post:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.