Wednesday, November 28, 2012

Upgrading from SharePoint 2010 Windows classic Authintecation to SharePoint 2013 Claims

  • SharePoint 15 continues to offer support for both claims and classic authentication modes
  • However claims authentication is THE default authentication option now
    • Classic authentication mode is still there, but can only be managed in PowerShell – it’s gone from the UI
    • Support for classic mode is deprecated and will go away in a future release, so we recommend moving to Claims
    • There also a new process to migrate accounts from Windows classic to Windows claims
  • The MigrateUsers method in SharePoint 2010 is no longer the correct way to migrate accounts – it is now deprecated
  • A new cmdlet has been created called Convert-SPWebApplication
  • A simple example – you have a Windows classic web application
    • Run Convert-SPWebApplication -Identity "http://yourWebapp" -To Claims –RetainPermissions [-Force]
        Other Claims Migration Scenarios:
§  You have an existing Windows claims application and you want to bring over content from a SharePoint 2010 Windows classic web app
§  Option 1 (the safest):
§  Create a web application in o15 that uses Windows classic authentication
§  Attach the SharePoint 2010 content database to this o15 web app
§  Attaching it will upgrade it to the o15 database format, so verify that it is working correctly after attach
§  Run the Convert-SPWebApplication command on the o15 web app to convert the users from Windows classic to Windows claims
§  Detach the content database from the o15 Windows classic web app
§  Attach the content database to it’s final o15 Windows claims web app
§  Option 2 (the quickest):
§  Attach the content DB to an existing Windows claims web application Run the Convert-SPWebApplication cmdlet again on the web app

1 comment:

  1. Hi,

    Why we need to detach and attach the database to different web app after converting to claims ?