Upgrade to SharePoint 2013

1. Upgrade to SharePoint 2013 Robi Vončina SharePoint Server MVP

2. Kompas Xnet d.o.o. • Servicesweoffer • SharePoint projects • Azure, Web, desktopandphonedevelopment • HelpDesk

3. Me time… Degree in economics Started as MS Office instructor System administrator I startedworkingwith SharePoint from 2003 version on Leader ofSloSPUG Diver, poolplayer

4. Agenda • Prerequisites • Upgrademethods • Authentication • Site Collection Upgrades • Deferring Site Collection Upgrade • Site Collection Health Checks • Evaluation Site Collections • Self-Service Site Collection Upgrades • Queuing Site Collection upgrades • Demo • System Notifications • System Status Bar • Miscellaneous Upgrade Items • Upgrade Log Improvements • Maintenance Log • Farm Upgrade Overview • Planning • Preparing • Executing • Finishing

5. Introduction

6. Server Prerequisites • 2010 or earlier SharePoint products must not be installed • To use existing 2010 SharePoint Farm hardware: • Backup your farm using SharePoint backup tool • Ensure your backup of farm and databases • Ensure SharePoint 2010 or earlier is not installed • Either uninstall old products • This includes dependent products like Project Server and language packs • Or pave the operating system

7. Client Minimum Software Requirements • Office 2010 or Office 15 • For full offline and integrated experience • SharePoint Designer 2010 only works for 14 mode sites • SharePoint Designer 15 works for both 14 and 15 mode sites • SharePoint Workspace 2010 and 15 work for both 14 and 15 mode sites • Web Browser • Internet Explorer 7 or higher

8. Upgrade Methods • Database Attach Upgrade • Only available method for version to version (V2V) upgrades • Works for both version to version (V2V) and build to build (B2B) upgrades • Works for content and services databases • In-Place Farm Upgrade • Only available for build to build (B2B) upgrades

9. Databases Supporting Database Attach Upgrade • Content databases • Project databases • Note: Four 2010 merged to one during upgrade • Search admin database • Profile database • Social database • Managed Metadata database • Secure Store database • Note: Passphrase required to retain passwords in store • Access databases • Note: Supported for B2B upgrades only

10. Databases Not Supporting Database Attach Upgrade • Configuration database • Unsupported for both V2V and B2B upgrades • Has never been supported in prior versions • Search index databases • Unsupported for V2V upgrades only • Sync database • Unsupported for V2V upgrades only

11. Authentication Mode Support & Upgrade • Windows Classic Support (Legacy) • SP2013 supports this with some issues • Windows Claims Support • Migration before upgrade recommended • Forms Auth Support • No changes from 2010 • Ensure provider installed with same name before database attachment • Database to Web Application authentication mode mismatches • Database attach in SP2013 detects mismatched auth support • Test-SPContentDatabase in SP2013 also detects this • Fix before attaching is best advice

12. Claims Migration Best Practices WRT Upgrade • Should not group both events together • Prevent stacked faults that could confuse troubleshooting • Ideally migrate to claims before upgrade • Alternately do so after upgrade is completed and verified successful • Find authentication mode mismatch issues between content databases and web applications with Test-SPContentDatabase first • If partial migration within content database, solve that before continuing • If misconfigured web application, fix before doing database attach/upgrades • Ensure all external data source/web services work as expected after claims migration

13. Upgrade process • Backupcontentdb on a SP2010 farm • Claims • Classic Windows Authentication on SP2013 • Restorecontentdb on SQL for SP2013 • MountandUpgradecontentdb • Site collectionupgrade

14. Demo Createweb app Test, MountSPContentdatabase

15. Site Collection Upgrades

16. Deferred Site Collection Upgrade • Eliminate big bang upgrades • Upgrade database now, upgrade site collections later • Keep existing customizations, updated ones can wait • Move forward at a manageable pace • Initially let users stay with 2010 experience: • Stay with the familiar • Keep using existing customizations • Gradually move users over to 2013 experience: • As training occurs (e.g. incrementally for each team) • As users decide to adopt new experience/features • As new version compatible customizations are available • Provide self-service site collection upgrade capability • Site collection admins can easily do the upgrade • Admins can still do upgrades or prevent users from doing them

17. Site Collection Health Checks • Rules can detect and in some cases repair issues • Rules can exist for use in 14 and/or 15 modes • Same or different rules may apply • Runs automatically in repair mode during version upgrade • Errors block site collection version upgrade • Can be run without doing upgrade • Give advanced notice of potential future issues

18. Evaluation Site Collections • Copy of existing site collection • Copy not intended for long term use; Evaluation site collection cannot become permanent • Version upgraded automatically as default • Copy made using snapshot or site collection backup/restore • Can only have one evaluation site collection for a given source site collection • Self-service creation only for small site collections • Maximum size configurable by farm admin controlled web application level settings • Large ones need farm admin to do create the evaluation site collection • Farm admin can copy any site collection as an evaluation site collection • PowerShell command to Request-SPUpgradeEvaluationSite queues creation • Evaluation site collections expire • Expiration date tracked on each evaluation site collection • Expiration date based on creation date and farm admin controlled expiry delay

19. Self-Service Site Collection Upgrades • Site collection admin chooses when to upgrade • Self service user interface to start and review upgrade • Health checks help ensure site is ready for upgrade • Health checks run in repair mode during version upgrade • Farm admin chooses if upgrade is available or not • Can block or allow all or specific site collection upgrades at the following levels: • Web application using SPWebApplication.CompatibilityRange • Site Collection using SPSite.AllowSelfServiceUpgrade • Can set parameters on max upgrade limits and upgrade parallelism

20. Queuing Site Collection Upgrades • Throttles limit the number of parallel upgrades • In web application worker process: • Maximum in process site collection upgrade limits • IIS Process parallel site collection upgrade limit • In any process: • Content database parallel site collection upgrade limit • Upgrade requests are always queued • Web application worker process overload will wait for process and database space • Note: This will never upgrade oversize site collections in the web application process • Timer jobs pick up queued items in content database jobs • Note: This includes queued oversize site collections • An unexpected failed site collection upgrades will resume automatically • Correctly failed upgrades will not resume as intervention is required • Status of all queued upgrades are tracked within the queue • Eventually every site collection will have a single queue entry once it gets upgraded

21. System Notifications

22. System Status Bar Notification bar at top of browser Shows two messages at most due to impact on screen real estate Tied to core rendering control Cannot easily be customized out Helps ensure this shows up even on heavily customized sites Custom messages not supported Optional link to more information can point to custom locations Can be closed for page viewing Shows up on next full page refresh or cross page navigation Can be hidden per site collection Will be all or nothing change, cannot show any messages if hidden Note: Only intended for use in special Internet facing scenarios • Displays system level information to end users: • Upgrade in progress • Upcoming maintenance window planned • Maintenance in progress • Site read only (i.e. Creating evaluation/copying/moving/backing up) • Database read only • Site collection read only at Farm admin request • Site collection read only at Site collection admin request • Site collection is for evaluation purposes and will expire • Displays important system level details to administrators: • Site upgrade available • Optional notify later link to hide message for a while

23. System Status Bar Notification Examples

24. Miscellaneous Upgrade Improvements

25. Upgrade Log Improvements • ULS Logging • TSV format with headers, easily imported into Excel • Separate Site Collection level upgrade logs (SiteUpgrade_DateTime.log) • Correlation Ids • Helps track specific upgrade sessions into ULS • Also helpful tracking unique sessions from merged parallel upgrade logs • Error Codes • Can help determine error cause/location/fix in debugging (Binging for answers) • Some progress at RTM, more codes will follow • Categorization of Operations • Better detail to track when entering/exiting sequences and actions • Planned for future update

26. Maintenance Log • Gallery added during any upgrade • Only added if it doesn’t exist • Will add during both version to version and build to build upgrades • Contains site collection upgrade logs • Only contains local site collection’s reduced logging level upgrade log • Full site collection and database logs still on file system for farm admin access • Logging level is separate from file system upgrade logs • Less detail than file system logs, not configurable

27. Demo Healthchecks Evaluationsites Site collectionupgrade Upgradelogs

28. Farm Upgrade Overview

29. Planning Farm Upgrades • Learn about upgrade (how it works, what to plan for) • Documentation/posters • Training • Try it out on a test environment • Gather data on existing farms (i.e. farm surveys) • Collect all settings within the farm • Get report on farm state including services, databases, and sites • Collect all customizations with installation/configuration documents • Plan business continuity • Outage length planning and mitigation methods

30. Preparing Farm Upgrades • Remove orphaned items • PowerPoint Broadcast sites • Web analytics • Customizations you can’t move forward (e.g. incompatible with 2013) • Build-out new 2013 farm(s) • If using federated services on different farms, target the services farm first • If possible leave old farms running while upgrading to new ones (for outage reduction) • Set farm CompatibilityRange as appropriate • Install customizations onto new farm • Ensure you install customizations for both 14 and 15 mode as appropriate

31. Executing Farm Upgrades • Backup everything • Upgrade services first • Search Administration database • Profile, Social, and Sync databases • Managed Metadata/Taxonomy database • Secure Store database • Remember to have Secure Store passphrase or you will lose all existing passwords • Project Server databases • Remember to merge the four 2010 Project databases before attempting upgrade • Upgrade content databases • Site collection upgrade automatically deferred • Upgrade site collections at your leisure

32. Finishing Up Farm Upgrades • Confirm successful upgrade state • Verify services and content rendering • Fix issues if necessary • Enable/disable self-service upgrades as required • Default allows upgrades and creation of 2010 site collections • Change web application CompatibilityRange • Old, OldVersions, or 14 will prevent 2013 site collection creation except for farm administrators • Old, NewVersion, or 15 will prevent 2010 site collection creation except for farm administrators, but will allow upgrade of 2010 site collections by site collection admins • All, AllVersions, or “14,15” will allow both 2010 and 2013 site collection creation and upgrade by site collection admins • Re-index existing content

33. Questions?