Your SlideShare is downloading. ×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

High-level Guide: Upgrading to SharePoint 2013


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. 1© 2000 - 2013 C5 Insight All rights reserved.Proprietary and confidential. May not be reproduced or distributed without written permission.Upgrading to SharePoint 2013A High-level Guide for Upgrading toMicrosoft’s Latest SharePoint Platform
  • 2. 2Non Disclosure AgreementFor the purposes of this document, and except as otherwise expressly provided in this document,"Confidential Information" means any information that C5 Insight, Inc. (“C5 Insight”) desires toprotect against unrestricted disclosure by the receiving party (“Recipient”).The Recipient agrees that it will hold in confidence the Confidential Information disclosed withinthis document and any documents, presentations, software, methods or other information sharedby C5 Insight in print, electronic, verbal or any other format. The Recipient shall exercisereasonable care to protect the Confidential Information from unauthorized disclosure, which careshall in no event be less than the Recipient takes to protect its own Confidential Information of alike nature. The Recipient may disclose Confidential Information only to its employees or agentswho need to know such information for purposes of this agreement, and shall inform suchemployees and agents, by way of policy and agreement, that they are bound by obligations ofconfidentiality.The entire content of this statement of work is classified as Confidential Information and byreading any further content within this document, the recipient is bound by the terms of this non-disclosure agreement.
  • 3. 3About Us
  • 4. 4Our Agenda
  • 6. 6Upgrades CycleLearn• Upgrademethods• New capabilities• DowntimemitigationPrepare• Documentenvironment• Managecustomizations• Plan upgradestrategy• Make itemsupgradableTest• Build test farms• Use real data• Evaluatetechniques• Find issues earlyImplement• Build/upgradefarms• Deploycustomizations• Minimizedowntime• MonitorprogressValidate• Troubleshooting• Upgrade eventfailures• UI/UX issues• Data issues
  • 7. 7SharePoint 2013 General RequirementsHardware• 8GB - 24GB of RAM (varies by server role)• No dynamic memory!• 64bit, 4 cores• 80GB system driveSoftware• Operating System• Windows Server 2008 R2 SP1 Std, Ent, Datacenter• Windows Server 2012• SQL• SQL 2008 R2 SP1 64bit• SQL 2012 64bit
  • 8. 8Upgrade Pre-Requisites• For any upgrade, SharePoint 2010 must be SP1• 14.0.6029.1000• SharePoint 2010 and 2013 can’t be on same server• SharePoint Designer• SharePoint Designer 2010 -> v14 sites• SharePoint Designer 2013 -> v15 sites• Client• Office 2010 or Office 2013 highly recommended• IE 8 or higher
  • 9. 9Upgrade Paths
  • 10. 10Upgrade Methodologies• Microsoft• DB Attach• In-Place Upgrades removed• Search First• Popular to move from 2007 to 2010• Use when going from 2010 FAST Search -> SharePoint 2013• 3rd Party ToolsMetalogix – Content MatrixQuest (Dell) – Migration SuiteAvePoint – Migration ToolsAxceler - DaVinchi MigratorMetaVis - Migration SuiteShare-gatedSHIFT (Xavor) - Migrator
  • 11. 11What’s New with Upgrades in 2013• No in-place upgrade• DB Attach available for Service Application DBs• Deferred site collection upgrade• True SP2010 instead of visual upgrade• Site collection health checker• Upgrade evaluation site collections• With notifications for life-cycle• Throttling for site collection upgrade• Log files are now in ULS format (Verify phase)
  • 12. 12Deferred Site Collection Upgrade• No more Visual Upgrade. It’s been replaced…• Now a true upgrade process• Databases are mounted, schema is upgraded, but site collections areNOT upgraded at time of attach/mount• Cannot be forced during upgrade (mainly performance reasons)• Site collections work unchanged in 2010 mode, but hosted in 2013• Creates a side-by-side 14 and 15 hive in 2013, allows existing featuresand solutions to function as they did• Site collections admins (if allowed) can controlupgrade• PLAN for performance
  • 13. 13Site Collection Health Checker• Checks a site collection and lists potential upgrade issues, such asmissing or unsupported elements• Included rules:• Conflicting content types• Customized files• Missing galleries• Missing parent content types• Missing site templates• Unsupported language pack references• Unsupported MUI references• Run in UI• Site Settings -> Site Collection Administration -> Site collection health checks• PowerShell• Test-SPSite and Repair-SPSite
  • 14. 14Upgrade Evaluation Site Collections• Site Collection admins can request upgradeevaluation site collection to preview in 2013• Temporary• SQL snapshots big advantage to avoiddowntime, but requires SQL Enterprise• Request an Evaluation Site Collection• Site Settings -> Site Collection Admin -> Site collectionupgrade, click Try a demo upgrade• User receives email when timer job “Create upgradeEvaluation Site Collections” creates site collection,then sends an email with URL• Expires after 30 days, auto deleted
  • 15. 15Logging Changes• Site Collection upgrade logs visible by site collection admins• In ULS log format• Stored in Maintenance Logs library that’s locked down asGallery
  • 16. 16Overview of Microsoft’s Upgrade Process
  • 18. 18Review the Existing Environment• You don’t know what you don’t know• What I mean is, plan and do your homework• Take an Inventory• Customizations• Content• Farm• Service Accounts and passwords• Cleanup• Large lists/libraries• Unused site collections• Broken or unused features / customizations / solutions• Remove orphaned or corrupt sites
  • 19. 19Inventory – What to Gather• Customizations• Solutions, Features and web parts• Branding – master pages, CSS and page layouts• Content• Large lists/libraries• Site topology• Old or unused webs / site collections• Farm Environment & Settings• Servers, farm info, farm passphrase, service accounts and passwords• Alternate access mappings, URLs• Service Application information• Don’t forget the secure store passphrase!• Use Upgrade Planning worksheet•
  • 20. 20Inventory – Gathering Methods• Manually / UI• PowerShell• Test-SPContentDatabase –name dbname –webapplication URL• Get-SPDatabases• Get-SPContentDatabase• Document farm settings scripts (• For 2007, find all FAB40 sites (• STSADM• Stsadm –o enumallwebs –includefeatures –includewebparts (use Feb 2011 CU for cmd updates)• Tools• PinPoint by Axceler (• Metalogix Blobulator (• SPSFarmReport ( or SPDocGen• Documentation Toolkit for SharePoint (
  • 21. 21Clean up the Environment• See TechNet• Large lists or lists with lots of columns (varies by column)• Remove Unsupported Sites• PPT Broadcast sites• FAST Search Center sites• Convert all 2007 Visual Upgrade to 2010 v4 UI• Clean up Databases to remove orphaned sites or corruption• Rearrange topology• FAB40 Sites• Extraneous document versions
  • 22. 22Cleanup – Details• Remove Unsupported Sites• PPT Broadcast Sites• Get-SPSite | Where-Object{$_.RootWeb.Template -eq"PowerPointBroadcast#0"} | Remove-SPSite• FAST Search Centers• Will upgraded, but is recommended to remove and re-create in2013• Convert all 2007 Visual Upgrades to 2010 v4• Get list with status• Get-SPSite | ForEach-Object{$_.GetVisualReport()}• Convert all• Get-SPSite | ForEach-Object{$_.VisualUpgradeWebs()}
  • 23. 23Clean up – Details Cont’d• Clean up databases• Corruption in database or corrupted list• Stsadm –o databaserepair or forcedeletelist• PowerShell – Get-SPContentDatabase | foreach {$_.Repair($false)}• False reports any corruption, True will repair the corruption• Duplicated / Orphaned sites / Deleted sites• Stsadm –o enumallwebs to view, then use Remove-SPSite (PowerShell)• SP2010 SP1 has Remove-SPDeletedSite cmdlet• Rearrange topology• Move-SPSite (between site collections), Export-SPWeb / Import-SPWeb• FAB40 Sites• Use this script to find all sites -• Extraneous Document versions• Use code, Versions web service
  • 24. 24Check Authentication• 2013 creates claims-based authentication for web apps by default• Only create classic via PowerShell• Recommended to convert 2010 Classic to Claims BEFORE upgradingto 2013• Use TechNet article with scripts• Can upgrade after using Convert-SPWebApplication• When creating web apps in 2013, create with same authenticationas in 2010• Use Test-SPContentDatabase to find mismatched authentication• Also checked on DB attach
  • 25. 25Object Cache Users• Don’t forget those site cache users!• Otherwise might get Access Denied$wa = Get-SPWebApplication -Identity "<WebApplication>"$wa.Properties["portalsuperuseraccount"] = "<SuperUser>"$wa.Properties["portalsuperreaderaccount"] = "<SuperReader>“$wa.Update()• Be sure to use the new claims-based name for the user likei:0#.w|domainusername
  • 26. 26Upgrade Considerations – All• Performance• Many factors• Topology• Office Web Apps now separate server• Our friendly neighborhood URL• In a perfect world, don’t change• Use old URLs even in TEST environment (use HOSTS file on server)• Patch your 2010 farm!• April 2012 CU works well
  • 27. 27Upgrade Considerations – Performance• Databases could grow as much as 50% during upgrade• Best way to estimate is to do a trial upgrade• The log files contain the duration for an upgrade — look for TotalElapsed Time at the bottom of the upgrade log file -%COMMONPROGRAMFILES%Microsoft Sharedweb serverextensions15LOGSupgrade.log• Database• # site collections, lists, libraries, overall size, etc.• Environment• Parallel upgrades, SQL, network, server resources• Consider all steps in upgrade process• backup/restore databases, search crawl, verifying environment• Plan for performance during upgrade (TechNet) -
  • 28. 28Customizations• Are your features, solutions and customizations compatiblewith 2013?• Have you checked to see if any can be removed prior toupgrade?• Is there new out of the box functionality that replacescustomizations?• Do customizations need to be re-done?• Branding, site provisioning, web templates…• Use SP Diagnostic Tool to find installed features•
  • 30. 30Build Test Environment• Build your SharePoint 2013 test environment• Use same URLs as production• Build as close to production as resources allow• Use real data• Destination• If staying on premise, use either on premise for 2013 or Azure• If going to online, sign up for a trial• Tips• Don’t ignore errors!• Test the environment AFTER the upgrade, not just the process
  • 31. 31Why You’re Testing• To verify migration strategy and processes• Test methods and scripts• Find issues• Test customizations• To be able to better estimate how long it will take• Be able to plan actual downtime for production migration• Build confidence from having done it• Know what to expect
  • 33. 33Upgrade Process – Create 2013 Farm
  • 34. 34A Quick Note on Virtualization• Be sure to read the SharePoint 2013 virtualizationarticles and best practices• This applies to SharePoint and SQL• Quick Tips• For SQL, don’t use dynamically expanding disks (bad for performance),may be called thin provisioned disks• For SQL and SharePoint, thou shall NOT use dynamic memory!• For SQL, only SQL Enterprise supports HOT memory adds• For SharePoint 2013, MS guidance is not to use it because ofdistributed cache (new in 2013) and Search services••
  • 35. 35Upgrade Process – Create 2013 Farm #1• Make sure you have all your inventory collected for farmsettings• Remove or stop the following services to avoid errors• Web Analytics• PowerPoint Broadcast Sites• Make sure you have collected• Passphrase for Secure Store• Export encryption key for User Profile service app• Stored in <root directory drive>Program FilesMicrosoft OfficeServers14.0Synchronization ServiceBin• Run miiskmu.exe (will need sync account credentials)
  • 36. 36Upgrade Process – Create 2013 Farm #2• Install new SQL Server• SharePoint 2013 no longersupports SQL 2005• Must be SQL 2008 R2 SP1 orSQL 2012 (SP1)• Not a bad thing, lots ofimprovements, especially in SQL2012 and Business Intelligence• Follow good SQL practices• Set max degree of parallelism to1 from 0 – SP install will error!
  • 37. 37Upgrade Process – Create 2013 Farm #3• Install SharePoint 2013• Run prereqs (read TechNet for all hotfixes!!)• Install the bits (setup.exe)• Can slipstream March 2013 PU, then install April 2013 CU• Run Psconfig• but don’t run the farm config wizard!• Don’t forget to create SQL alias!• Create any service applications that aren’t being upgraded• Apps, Machine Translation, etc.• Configure farm settings• SMTP email• Diagnostic logging, etc.• Check state of timer job “Workflow Auto Cleanup” in 2010• Runs daily, deletes workflow history older than 60 days• If disabled in 2010, disable in 2013 to avoid workflow associations issues
  • 38. 38Upgrade Process – Copy Databases
  • 39. 39Upgrade Process – Copy Databases #1• Set DB to read only (optional)• SQL Mgmt Studio, database properties, set Database Read-only to True• Backup Databases for content and service applications• All content databases• Service applications (if used)• BCS• Managed Metadata• PerformancePoint• Search• Secure Store• User Profile (all 3)• Note: If full recovery model, best to do transaction log active backup first(option in transaction log backup settings)
  • 40. 40Upgrade Process – Copy Databases #2• Restore all databases to SharePoint 2013 SQL Server• Right click databases, click Restore Database• Restore -> to database• Type new database name in To Database in the box• Check the “Restore the database files as” path and filenames• Ensure all set for read-only to false
  • 41. 41Upgrade Process – Upgrade Service Applications
  • 42. 42Upgrade Process – Upgrade Service Apps #1• Start Service Instances for service apps that are being upgraded• Perform in Central Admin• Search can’t be in the UI, only in PowerShell• Create Service Applications, use existing DB names• Upgrade happens at this point• Must use PowerShell• Create Service App Proxies (all but BCS), add to default group• For Secure Store, restore passphrase• For UPS, import encryption key• Use PowerShell from TechNet•
  • 43. 43Upgrade Process – Upgrade Content Databases
  • 44. 44Upgrade Process – Upgrade Content DBs #1• Create new web apps• Use same URL• Use same authentication method (convert from classic before migration)• Recreate all same settings like managed paths, quota templates, emailsettings, self-service site creation, web application policies• For My Site host, create /personal wildcard managed path• Install / re-apply customizations• Don’t forget web.config changes!• To install to both 14 and 15 hives, use CompatibilityLevel parameter onInstall-SPSolution cmdlet
  • 45. 45Upgrade Process – Upgrade Content DBs #2• Run Test-SPContentDatabase before attach• Test-SPContentDatabase -Name DatabaseName -WebApplication URL• Attach content databases to web application• This is when database is actually upgraded (not site collection)• MUST use Mount-SPContentDatabase, UI not supported for upgrading• If webapp spans databases, be sure to restore DB with root site collection first• Once completed, remove databases that were created by webapp creation• For MySites, mount MySite host first• After first db mount, check upgrade status in CA• Central Admin -> Upgrade and Migration -> Check upgrade status• You can mount multiple content DBs in parallel
  • 46. 46Upgrade Process – Upgrade DB Cleanup• Verify site collections work in 2010 mode• Check links in InfoPath form templates• Configure Search topology• Perform full crawl• Good time to do backups• Test, test, test and then test some more
  • 47. 47Upgrade Process – Upgrade site collections #1• Run site collection healthchecks• Create site collectionevaluation sites• Test functionality in 2013 mode• Upgrade the site collections• Site settings -> Site collectionadministration -> Site collectionupgrade, then click Upgrade thissite collection
  • 48. 48Upgrade Process – Upgrade site collections #2• Use PowerShell to upgrade site collections• To upgrade a single site collection immediately and bypass the upgradequeue:• Upgrade-SPSite <http://site> -VersionUpgrade –Unthrottled• To upgrade ALL site collections in a database at once:• Get-SPSite -ContentDatabase <DBName> -Limit All | Upgrade-SPSite -VersionUpgrade –QueueOnly• Plan what sites Farm admins will upgrade, and which site collectionadmins will do• High-priority• Highly customized• Very large
  • 49. 49Upgrading My Sites• High Level Process• Be sure User Profile and Metadata service appsis already upgraded and functioning• Create new webapp for My Sites• Attach DB to new My Site Host• Migrate My Site Host site collection• Personal site collections upgraded automatically• Be sure to migrate the My Site host sitecollection FIRST• As each user visit’s their My Site (if exists), itwill get queued to be upgraded• If the user doesn’t have a My Site yet, it will spinup a 2013 My Site• If a user visit’s their My Site before the Host isupgraded, they will get 2010 My Site
  • 51. 51Checking the Upgrade• Make sure all sites and pages render• If pages don’t render, add ?contents=1 to load web part maintenancepage• Might be due to master page, can change with PowerShell or SPD ifnecessary• Check all sites, lists, libraries• Check site settings pages• Try adding web parts to pages• Verify services• Check for errors
  • 52. 52Troubleshooting Failures• Always check upgrade logs!• In site collection• http://<SiteName>/_catalogs/MaintenanceLogs/YYYYMMDD-HHMMSS-SSS.txt• On server - %COMMONPROGRAMFILES%Microsoft SharedWeb serverextensions15LOGS• SiteUpgrade-YYYYMMDD-HHMMSS-SSS.log• Review upgrade error log first, then full upgrade log, then ULS logs• Check event viewer logs• Are all customizations installed?• MS Recommended troubleshooting order• Authentication -> missing files/customizations -> content issues
  • 53. 53Finishing Up• Confirm successful upgrade state• Verify services and content rendering• Enable/disable self-service upgrades as required• Default allows upgrades and creation of 2010 site collections• Change web application CompatibilityRange property• Old, OldVersions, or 14 will prevent 2013 site collection creationexcept for farm administrators• Old, NewVersion, or 15 will prevent 2010 site collection creationexcept for farm administrators, but will allow upgrade of 2010 sitecollections by site collection admins• All, AllVersions, or “14,15” will allow both 2010 and 2013 sitecollection creation and upgrade by site collection admins
  • 54. 54Key Takeaways• Do you have your documentation?• Test-spcontentdatabase and stsadm to find issues• Test the migration• Work with your users, involve them in UAT and training,goes a long way for user adoption• Check all important sites to validate any customfunctionality• Does 2013 have functionality that can replacecustom?
  • 55. 55Helpful Links & ResourcesOverview of SharePoint 2013 Upgrades for database-attach upgrade to SharePoint 2013 First migration from FAST Search 2010 to 2013 for performance during upgrade to SharePoint 2013 and Migration SharePoint 2013 Resource Center 2013 known Issues database issues in SP 2013 site collection issues in SP 2013 2013 Upgrade Process 2013 Test Your Upgrade Process model 2013 Upgrade Worksheet to Upgrade in SharePoint 2013 by Bill Baer 2013 IT Pro Training
  • 56. 56Contact Us