Monday, January 21, 2013

Method for migrating or upgrading Sharepoint 2010 to 2013.

On new server
  1. Create new Web Application
    1. Use the same exact websitename as the original site.
    2. Use the sameport as orginal site.
    3. Make sure the same authentication method is used. In Sharepoint 2013 the new default method is Claims Based Authentication which can cause problems.
        1. To deactivate Claims based Authentication using Powershell:
          /> $setcba = Get-SPWebApplication http://YourSiteURL
          />$setcba.UseClaimsAuthentication = 1;

    4. Make sure e-mail settings are configured
    5. Take care not to not configure any Site Collections for the new site. This will solve itself when old site is restored.
  2. On Original server
  3. Take backup of contentdatabas for the site using SQL Management Studio.
    1. The Databas can be set to Read-Only before taking backup to make sure no changes are made to database after backup. Users will still be able to access and read from site, but not change or upload.
  4. Copy contentdatabas to new server.
  5. On the new server
  6. Restore contentdatabas using SQL Management Studio
  7. Make sure Sharepoint Service account and the current user account (usually Sp_admin) has Databas Owner Permissions on the newly restored database.
  8. Verify that all required components are installed, like languagepacks and custom webparts etc.
    1. Run />test-spcontentdatabas –name yourcontentdatabase –webapplication http://yourwebsite:80 (sometimes, with many errors, it’s easier to read if piped to txt document by adding > myerrors.txt
    2. Identify and correct as many as possible. This can be difficult cause only application ID is shown for most features.
        1. To identify installed features it’s sometimes easier to compare the missing features to IDs found on the original sharepointsite.
          Using powershell:
          />get-spfeature –webapplication http://yourwebsite:80
          Or if you want a more complete list use good old stsadm
          /> stsadm –o enumallwebs –includefeatures > featurereport.txt

    3. This features might not be critical but you’ll know soon enough if you go forward without them. Trial and error is the way to go.
  9. Mount the contentdatabas to the webapplication
    1. />mount-spcontentdatabase –name yourcontentdatabas –databaseserver yourserver\sharepoint –webapplication http://yourwebsite:80
    2. Its optional to add: -upgradeuserexperience to above, but it’s usually advisable to check so everything works before upgrading through GUI instead.
    3. If for some reason mounting needs to be redone, you can use command below to verify that all been upgraded properly
    4. /> upgrade-spcontentdatabase –identity yourcontentdatabase
  10. Through Central Administration, make sure to verify that the Collection Admin for your website is something you can work with.
  11. You might also want to verify that all went as it should through Central Admin > Upgrade and Migration > Check Upgrade Status
  12. Test and see if your site is working as it should.
  13. Upgrade the visual experience to sharepoint 2013
- When restoring a site using SSL-certificate, don’t use the built in IIS 7.0 Certificate when testing out the site. Better to use a internal CA and distribute a correct cert. Otherwise things can’t get a bit funky.
- When restoring site using SSL-Certificate. If images seems to be missing from the website, try to deactivate the SSL function and see if it works better. Then activate SSL again. This worked for me for some reason. Though it might been an consequence from using the built in certificate in IIS7 and then switching.
- If the site looks funky after restore, give it a minute. I’ve had experiences when all looked wrecked and then 30min later all is fine. Might be a slow upstart of the Application Pool service or some accounts that need to be recreated.

No comments: