Upgrading to SharePoint 2013

5,393 views
5,266 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
5,393
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
64
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Upgrading to SharePoint 2013

  1. 1. Upgrade to SharePoint 2013 Presented by:
  2. 2. About Me Veenus Maximiuk, MCITP, MCTS, MCPD, vTS SharePoint Managing Architect spvee.wordpress.com @SharePointVee Linkedin.com/in/vmaximiuk vmaximiuk@iccohio.com2 © 2013, Information Control Corporation
  3. 3. Agenda Things to Know Claims Service Application Before Upgrade Migration & Content Upgrade Upgrade Improvements Demos Q&A3 © 2013, Information Control Corporation
  4. 4. Things to Know Before Upgrade4 © 2013, Information Control Corporation
  5. 5. Supported Upgrade SharePoint 2007 SharePoint SharePoint (MOSS) Server 2010 Server 2013 Windows SharePoint SharePoint SharePoint Foundation Foundation Services 3.0 2010 20135 © 2013, Information Control Corporation
  6. 6. Upgrade Requirements Server Requirements Client Requirements • SharePoint Server • Office 2010 or Office 2013 – Windows Server 2008 R2 SP1, – For full offline and integrated or experience – Windows Sever 2012 – Office 2007 – limited Datacenter or Standard integration – NO Previous Versions of • Browser SharePoint – Internet Explorer 8, 9, and 10 • Database Server – Chrome – SQL Server 2008 R2 SP1 (x64), – Firefox or – Safari – SQL Server 2012 (x64)6 © 2013, Information Control Corporation
  7. 7. Upgrade to SharePoint 2013 • In-Place Upgrade is NOT Supported • Database Attach is the only supported upgrade option • Only the following databases can be upgraded: – Content Databases – Business Data Connectivity – Managed Metadata – PerformancePoint – Search Administration – Secure Store – User Profile (Profile, Social, and Sync DBs)7 © 2013, Information Control Corporation
  8. 8. Assessing What to Upgrade • Just because you can upgrade a Service Application Database, doesn’t mean that you necessarily should • Only upgrade those Service Applications that have critical data in them – If you haven’t invested anything into User Profile Service Application or The Managed Metadata store, simply create new ones in SP2013. • This will keep the process simple • A content-only migration can be made relatively simple by following this rule8 © 2013, Information Control Corporation
  9. 9. Claims Migration9 © 2013, Information Control Corporation
  10. 10. Authentication Modes • Windows Classic Support (Legacy) – SP2013 supports this with some issues – Migration before upgrade is recommended • Forms Authentication Support – No changes from 2010 – Ensure provider is installed with same name before attaching database • Database to Web Application authentication mode mismatches – Database attach in SP2013 detects mismatched authentication support – Test-SPContentDatabase in SP2013 also detects this – Fix before attaching is best advice10 © 2013, Information Control Corporation
  11. 11. Service Application & Content Upgrade12 © 2013, Information Control Corporation
  12. 12. Upgrading Managed Metadata Service Step-by-Step 1. Restore the database 2. Get the Managed Account 3. Create a new Service Application Pool 4. Create the new Managed Metadata Service using the restored database 5. Create the new Managed Metadata Service Application Proxy 6. Start Managed Metadata Service13 © 2013, Information Control Corporation
  13. 13. Managed Metadata Service Upgrade Results14 © 2013, Information Control Corporation
  14. 14. Managed Metadata Service Term Store Upgrade Results15 © 2013, Information Control Corporation
  15. 15. Upgrading User Profile Service Step-by-Step 1. Restore the databases 2. Get or create Managed Account 3. Get or create Service Application Pool 4. Create the new User Profile Service using the restored databases 5. Create the new User Profile Service Application Proxy 6. Start User Profile Service 7. IISRESET (Just in case, because 9 times out of 10 this fixes rogue SharePoint errors)16 © 2013, Information Control Corporation
  16. 16. User Profile Service – Service Application Upgrade Results17 © 2013, Information Control Corporation
  17. 17. User Profile Service – Managed Profile Service Upgrade Results18 © 2013, Information Control Corporation
  18. 18. Upgrade Managed Metadata Service Application Demo19 © 2013, Information Control Corporation
  19. 19. Prepare for Content Upgrade • Clean up the SP2010 farm for upgrade: – Check for and repair all database consistency errors – Turn off web analytics service application – Remove PowerPoint Broadcast Sites • Recreate the following on the new farm – Alternate Access Mappings (AAMs) – 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.) – Certificates20 © 2013, Information Control Corporation
  20. 20. Content Upgrade Overview 1. Prepare SP2010 and SP 2013 Farms 2. Create a SP2013 Web application 3. Backup SP2010 Content DB 4. Restore SP2010 Content DB to SP2013 SQL Server 5. Test Upgrade Process using Test-SPContentDatabase cmdlet 6. Run Mount-SPContentDatabase cmdlet to upgrade DB schema 7. Run Get-SPSite –ContentDatabase CONTENTDBNAME –Limit All | Upgrade-SPSite – VersionUpgrade to upgrade Site Collections 8. Check the Status of the Upgrade Get-SPSiteUpgradeSessionInfo –ContentDatabase CONTENTDBNAME –ShowInProgress – ShowCompleted -ShowFailed21 © 2013, Information Control Corporation
  21. 21. Upgrade Content Databases Demo22 © 2013, Information Control Corporation
  22. 22. Upgrade Improvements23 © 2013, Information Control Corporation
  23. 23. Upgrade Improvements • Deferred Site Collection Upgrade • Site Collection Health Checks • Upgrade Evaluation Site Collections • System Event Notifications • Logging Changes • Site Collection Upgrade Throttling24 © 2013, Information Control Corporation
  24. 24. Deferred Site Collection Upgrade • No more Visual Upgrade – Was just a fake upgrade – The site was already upgraded – Lots of UI problems • SharePoint 2013 can host “real” SharePoint 2010 sites – Installation adds both 14 and 15 root folders – Solutions can be deployed in 14 and/or 15 mode – You can (but shouldn’t) create new 2010 mode sites25 © 2013, Information Control Corporation
  25. 25. Site Collection Health Checks • Check the health of the Site Collection – Customized files – Missing galleries – Missing Site Templates – Unsupported Language Pack References – Unsupported MUI References • PowerShell cmdlets – Test-SPSite –Identity <URL> – Repair-SPSite Identity <URL> [-RuleID <GUID>]26 © 2013, Information Control Corporation
  26. 26. Site Collection Health Checks27 © 2013, Information Control Corporation
  27. 27. Evaluation Site Collections • Allows upgraded preview of existing site in 15 mode – Request-SPUpgradeEvaluationSite –Identity <URL> • Makes side by side copy of existing site collection • Limited lifetime – Default 30 days • When Eval site is OK, the original site can be upgraded28 © 2013, Information Control Corporation
  28. 28. Request for Site Evaluation29 © 2013, Information Control Corporation
  29. 29. Creates Upgrade Evaluation Site Collections Timer Job30 © 2013, Information Control Corporation
  30. 30. Site Collection Evaluation Site31 © 2013, Information Control Corporation
  31. 31. Using Self-Service Site Collection Upgrades Demo32 © 2013, Information Control Corporation
  32. 32. Upgrade Logging • Changed to ULS format – TSV format allows improved parsing – Can be imported into Excel – Includes Correlation ID • Logs can be made available to Site Collection admins – Uses separate logging level control than rest of upgrade – Shows reduced set of information by default – Created for both B2B and V2V upgrades – Stored as content within Site Collection33 © 2013, Information Control Corporation
  33. 33. Site Collection Upgrade Throttling • Prevents overload from self-service site collection upgrade – SPWebApplication.SiteUpgradeThrottleSettings.AppPoolConcurrentUpgradeSessionLimit – SPWebApplication.SiteUpgradeThrottleSettings.UsageStorageLimit – SPWebApplication.SiteUpgradeThrottleSettings.SubwebCountLimit – SPContentDatabase.ConcurrentSiteUpgradeSessionLimit • Site upgrades are placed in a queue • Check the queue using: – Get-SPSiteUpgradeSessionInfo –ContentDatabase <ID> -ShowInProgress – ShowCompleted –ShowFailed • Check a site using: – Get-SPSiteUpgradeSessionInfo –Site <URL> • Remove a site from the queue – Remove-SPSiteUpgradeSessionInfo –Identity <URL>34 © 2013, Information Control Corporation
  34. 34. Some Bonus Stuff • Always update My Site Host first – My Sites cannot be upgraded before My Site Host – My Sites will automatically be upgraded when users hit them – Upgraded My Sites is required for new Social features • Get-SPUpgradeActions – Shows all upgrade actions in the farm • Get-SPPendingUpgradeActions – Shows all pending upgrades for a given root object – Get-SPFarm | Get-SPPendingUpgradeActions -Recursive35 © 2013, Information Control Corporation
  35. 35. Thanks to Our Sponsors36 © 2013, Information Control Corporation
  36. 36. Questions?37 © 2013, Information Control Corporation

×