NZSPC 2013 - Upgrading to SharePoint 2013


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

NZSPC 2013 - Upgrading to SharePoint 2013

  1. 1. Michael Noel CCO
  2. 2.  Author of SAMS Publishing titles “SharePoint 2013 Unleashed,” “SharePoint 2010 Unleashed”, “Windows Server 2012 Unleashed,” “Exchange Server 2013 Unleashed”, “ISA Server 2006 Unleashed”, and a total of 19 titles that have sold over 250,000 copies. Partner at Convergent Computing ( / +1(510)444-5700) – San Francisco, U.S.A. based Infrastructure/Security specialists for SharePoint, AD, Exchange, Security
  3. 3. 3 Upgrade Fundamentals  Requirements for Upgrade  Version to Version and Build to Build Specifics  Third-Party vs. MS Approach Pre-Upgrade Tasks Claims Upgrade Content Upgrade Service Application Upgrade  Managed Metadata Upgrade  User Profile Synch Upgrade Post-Upgrade Tasks
  4. 4. 4Understanding the Best Practices around SharePoint 2013 Upgrade
  5. 5. 5 In-PlaceUpgrade is NOT Supported Database Attach is the only supported MS upgrade option Only the following databases can be upgraded:  Content Databases  Business Data Connectivity  Managed Metadata  PerformancePoint  Secure Store  Search  User Profile (Profile, Social, and Sync DBs)
  6. 6.  Just because you can upgrade a Service Application DB, doesn‟t mean that you necessarily should Only upgrade those SAs that have critical data in them. If you haven‟t invested anything into UPA or the Managed Metadata store, simply create new ones in SP 2013. This will keep the process simple. A content-only migration can be made relatively simple by following this rule
  7. 7.  Microsoft Approach ONLY allows upgrade from SharePoint 2010 directly to SharePoint 2013 Upgrades from SharePoint 2007 or SharePoint 2003 must first upgrade to SharePoint 2010 first. 3rd Party tools remedy this, but for additional cost
  8. 8.  Build to Build and Version to Version are Supported But can‟t move „down‟ in versions… For example, the following is supported:  SP Foundation 2010 to SP Foundation 2013  SP Foundation 2010 to SP Server 2013 (Std. or Ent)  SP Server 2010 Std. to SP Server 2013 Std.  SP Server 2010 Std. to SP Server 2013 Ent.  SP Server 2010 Ent. to SP Server 2013 Ent. But the following is NOT supported:  Ent to Std.  Server to SPF
  9. 9.  Design completely new farm based on Best Practices Move to new version of SQL (2012 ideally,) including moving off of SQL Express Incorporate High Availability and Disaster Tolerance Prepare the new farm in tandem, while the old one is running – test for functionality and upgrade
  10. 10.  Run a „dry run‟ of the migration process on the newly built SharePoint farm Test out migration of all content, ideally At a minimum, a „spot migration‟ of content should be performed Have content owners identify if migration was successful When complete, delete the databases and migrate again
  11. 11. 12A Cautioned Approach
  12. 12.  Recreate the following on the new farm:  Alternate access mappings  Authentication providers and authentication modes that are being used  Quota templates  Managed paths  Self-service site management settings  Incoming and outgoing e-mail settings  Customizations (solution packages, etc.)  Certificates Clean up the SP 2010 farm for upgrade:  Check for and repair all database consistency errors.  Turn off Web Analytics service application  Remove PowerPoint Broadcast Sites
  13. 13.  DB Schema upgrade and Site Collection Upgrade is now separate, allows Site Collection owners to „preview‟ the new visuals before comitting. Upgrade keeps SharePoint 2010 in „native‟ format, by providing both a „14‟ and a ‟15‟ hive on the web role servers Avoids the majority of issues that have affected SharePoint upgrades in the past by allowing them to be previewed Not a long term solution, preferred to move to SharePoint 2013 mode quickly, and administrators can force site collection upgrades by a certain point in time
  14. 14. 15Classic mode Auth to Claims Auth Migration
  15. 15. 16 ClassicMode Auth Web Apps in SharePoint 2010 (the default) need to be migrated to Claims first before Upgrade Exception is if you create a Classic-Auth Web App in SharePoint 2013 (not recommended) Requires PowerShell scripting to be done on the SP2010 Server in advance Alerts may need to be regenerated after the claims migration and Search may have issues (known work-arounds exist)
  16. 16. 17 $WebAppName = "" $wa = get-SPWebApplication $WebAppName $wa.UseClaimsAuthentication = $true $wa.Update() $account = "COMPANYABCSHAREPOINTADMIN" $account = (New-SPClaimsPrincipal -identity $account - identitytype 1).ToEncodedString() $wa = get-SPWebApplication $WebAppName $zp = $wa.ZonePolicies("Default") $p = $zp.Add($account,"PSPolicy") $fc=$wa.PolicyRoles.GetSpecialRole("FullControl") $p.PolicyRoleBindings.Add($fc) $wa.Update() $wa.MigrateUsers($true) $wa.ProvisionGlobally()
  17. 17. 18Core Upgrade Concerns
  18. 18. 191. Test Upgrade Process using Test-SPContentDatabase cmdlet2. Create new SP 2013 Farm with same AAMs3. Create a web application (delete default DB)4. Set source DB to „Read-Only‟5. Backup existing Content DB6. Restore Content DB to new SQL Server7. Run Mount-SPContentDatabase cmdlet to upgrade DB schema8. Run Get-SPSite –ContentDatabase CONTENTDBNAME – Limit All | Upgrade-SPSite –VersionUpgrade to upgrade Site Collections
  19. 19. 20 Test the Content Databases for upgrade using the Test- SPContentDatabase cmdlet Address issues before migrating Example: Test- SPContentDatabase - ServerInstance SQLSERVERNAME -Name DBNAME - WebApplication http://webapptargetnam e
  20. 20.  Afterissues have been resolved, use Mount- SPContentDatabase to mount DB in SharePoint 2013 Percentage indicator will show how long the upgrade will take
  21. 21.  Second set of PowerShell commands continues the upgrade Get-SPSite –ContentDatabase CONTENTDBNAME –Limit All | Upgrade-SPSite -VersionUpgrade
  22. 22.  Check the status of the upgrade using Get- SPSiteUpgradeSessio nInfo Syntax: Get- SPSiteUpgradeSessio nInfo – ContentDatabase CONTENTDBNAME – ShowInProgress – ShowCompleted - ShowFailed
  23. 23. 26Proceed with Caution
  24. 24. 27 Some Service Apps DBs can be Upgraded  UPA (Sync, Social, and Profile Databases)  Project Databases (all 4 databases get merged into 1 in SharePoint 2013)  Secure Store Database  Social Database  Search Admin Database  Managed Metadata Database Web Analytics is Retired Other Service Apps do not store any data that requires migration Process for migrating each Service App is as follows:  Create or Declare existing Application pool for Service Application  Restore Service Application database  Create Service Application Proxy
  25. 25.  Createthe new Service Application Pool on the 2013 Server that will house the old 2010 DB Use New-SPServiceApplicationPool cmdlet
  26. 26.  2nd step is to reference the restored database for upgrade Use New-SPMetadataServiceApplication cmdlet to create the connection between the S.A. and the DB
  27. 27.  3rdstep is to create the Service Application Proxy Use the New- SPMetadataServiceApplicationProxy cmdlet
  28. 28.  TheManaged Metadata Service Application should then be visible in SPCA
  29. 29.  And the Term Store should then be visible
  30. 30.  Finally, change the Content Type Hub URL using the following cmdlet (note that –HubUri is used…the „i‟ is accurate.)
  31. 31. 1. Export MIIS encryption Key (optional if not recreating the Sync DB)2. Create Web Application for UPS3. Create User Profile Service4. Restore User Profile databases to new SharePoint 2013 farm (Sync DB optional)5. Import MIIS encryption key (optional)
  32. 32.  Use the miiskmu tool to export out the UPA key
  33. 33.  Run through the MIISKMU tool and export the key sets
  34. 34.  Enter Credentials that run the current SP2010 UPA
  35. 35.  Create the new Service Application Pool for the UPA
  36. 36.  You must find the GUID of the new UPA using a SQL Query
  37. 37.  The GUID is then used in the creation of the new Service Application Proxy for the UPA
  38. 38.  The UPA will then be visible as a Service Application from within SPCA
  39. 39.  Copy the encryption key to the bin folder Use the /? to find the GUID of the key
  40. 40.  Inject the key using the GUID provided and the command syntax below
  41. 41. Company Site: www.cco.comTwitter: blog:
  42. 42. Thank you to our sponsors