Hi,

I have an issue where we have upgraded a site collection to SharePoint 2010 Mode. So have done Test-SPContentDatabase and Mount etc. I then moved these as host url sites collections under one Web application as recommended by Microsoft. Problem I have is when I view the site in SharePoint 2010 mode I am able to login as myself as I was added wioth script below. However, when I try and login as the Site Collection Owner i.e. sp_admin. I get Access Denied. So I go into the site Collection and add sp_admin again then I can login.

Is this a case of SIDs gettiung corrupt? Here is the script I ran after mounting each web application.

$WebApp = Get-SPWebApplication "http://mysitecoll"

$WebApp.UseClaimsAuthentication = 1;
$webApp.Update()

$account = "ourdomain\mypersonallogin"
$account = (New-SPClaimsPrincipal -identity $account -identitytype 1).ToEncodedString()
$wa = get-SPWebApplication $WebApp
$zp = $wa.ZonePolicies("Default")
$p = $zp.Add($account,"PSPolicy")
$fc=$wa.PolicyRoles.GetSpecialRole("FullControl")
$p.PolicyRoleBindings.Add($fc)
$wa.Update()

$wa = $WebApp
$wa.MigrateUsers($true)
$wa.ProvisionGlobally()

Am I doing this correctly? Is this going to be expected behaviour in SharePoint 2010 mode?

Thanks.

John.

• Edited by John Guilbert Friday, January 30, 2015 10:00 AM

Sounds like a classic web app being migrated to claims but not moving the user IDs over correctly. Check the hidden user information list to see if you've got duplicate entries for the admin user you added.

Have a look at this article again and check you're using the right steps. Those are for a 2010 Classic to 2010 Claims migration. If you're going 2010 Classic to 2013 classic you want different steps.

https://technet.microsoft.com/en-us/library/gg251985(v=office.15).aspx

Hi Alex,

Looks like I have used the wrong method - I think????. Can you confirm that if you are migrating from SharePoint 2010 farm (Classic) to test SharePoint 2013 farm (Host Url Site Collections)(Claims) as per Microsoft Migration instructions you should be using:

In the first you are performing the migration from classic to claims and from 2010 to 2013 in one go. In the second you break it into two stages, the classic to claims migration is done in 2010 and only then do you move it to 2013.

• Edited by Alex BrassingtonMicrosoft community contributor 2 hours 36 minutes ago punctuation