sharepoint 2013 – the upgrade story
DESCRIPTION
Speaker: Wictor Wilén; This session will cover what you need to do an upgrade from SharePoint 2010 to SharePoint 2013, You’ll learn the upgrade planning, methods and execution through a number of demos. During the session we will do a live upgrade from SharePoint 2010 to SharePoint 2013. We’ll also cover the Site Collection upgrade previews and health checks, which allows the site collection owner to determine when they are ready to move on to the new version.TRANSCRIPT
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS
ZAGREB, 11/28/2012
SharePoint 2013 – The Upgrade StoryWICTOR WILÉN, CONNECTA ABSWEDEN
sponsors
Wictor Wilén
• Senior SharePoint Specialist
• Connecta AB, Sweden
• Microsoft Certified Architect – SharePoint 2010
• Microsoft Certified Solutions Master – SharePoint
• Microsoft Certified Master – SharePoint 2010
• Microsoft Most Valuable Professional – SharePoint
• www.wictorwilen.se
• @wictor
Agenda
Requirements
Preparation
Upgrade Farm and Services
Upgrade Content Databases
Upgrade Sites – Deferred Site Collection Upgrade
…and some tips and tricks
Upgrade process
Requirements Prepare Test Upgrade Upgrade Farm Validate Eval Upgrades Upgrade Sites Validate
REQUIREMENTS
SharePoint 2013 Requirements
Understand the new Hardware and Software requirements for SharePoint 2013
You need a new set of hardware
• No V2V in-place upgrades anymore!
• Typically SharePoint 2013 requires more tin than SharePoint 2010
Operating System
• Windows Server 2008 R2
• Windows Server 2012
SQL Server
• SQL Server 2012 (SP1 for BI stuff)
• SQL Server 2008 R2 SP1
Internet Explorer 7.0 not longer a supported browser
Training
Make sure you get training on SharePoint 2013
• For your IT-pros
• For your Administrators
• For your End-users*
• For your Developers
• For your Consultants(!)
Learn PowerShell if you haven’t done it before!
PREPARATION
Plan
Make sure you have a plan – and understand it!
Communicate early!
• Inform the users about your plan
Always have a backup plan
Plan and communicate major changes
• URL’s (avoid if possible)
• UI – Metro – Modern UI
Survey your old farm
Check for this…
• Customizations and Solution packages (WSP)
• Service Applications
• Web Applications
• Databases
• Large lists
• Configurations
• Language Packs
• Infopath forms
• Proxy Groups
• …
Document it!
• There are some really nifty tools available for this!
Fix your old farm, even before considering
upgradeClaims!
• It’s better to convert to Claims before upgrading
• Test/Fix/Upgrade custom Claims Providers
• Document custom claims encodings!
Remove orphaned items
Remove deprecated things
• PowerPoint Broadcast sites
Remove stuff you don’t need
• Solutions
• Sites
Patch!
• CU June 2011 contains a MigrateUsers fix (post SP1 CU)
• CU April 2012– optimal CU, least impact during DB Attach
DEMO: CONVERT TO CLAIMS
Prepare new 2013 farm
Install SharePoint 2013 in a new farm
• Pre-reqs
• SharePoint 2013
• Language Packs
Do NOT use the Farm Configuration Wizard
• You should never do this anyway….
“Copy” farm-level configuration from old farm
• Don’t forget the custom claim encodings!
Install your old solutions/customizations into the new farm
•Install-SPSolution … -CompatibilityLevel “14,15”
• For custom code you can use SPSite.CompatibilityLevel
Backup databases
Content Databases
Service Applications
• Business Data Connectivity
• Managed Metadata
• PerformancePoint
• Search (only the Search Admin DB)
• Secure Store
• User Profile (Profile, Social and Sync DBs)
Restore databases
Restore the databases in the new farm
Do not yet remove the old databases!
You will do this many times!
Last time set old databases to read-only!
DEMO: BACKUP AND RESTORE A CONTENT DATABASE
TEST AND UPGRADE
Create New Service Applications
New Service Applications
• State Service
• App Management Service
• Work Management Service
• Machine Translation Service
• Access Services 2013
• PowerPoint Automation Service
Service Applications without (upgradeable) Databases
• Excel Services
• Visio Graphic Services
• Word Automation Service
Upgrade Service Applications
Create new Service Applications
• Use PowerShell – you will do this several times
• Reference the restored databases
• Make sure that you time all upgrades!
Create Service Application Proxies
Add Proxies to the correct Proxy groups
What about Service Farms?
Always upgrade Services Farms first
• SharePoint 2010 can consume services from a SharePoint
2013 Services farm
Only see this as an intermediate solution!
Upgrade Content Databases 1/2
Create a new Web Application
• Use Claims if you already converted to Claims
• Use Classic if you want to switch to claims later (PowerShell
only)
• Do convert and upgrade at the same time!
• Apply Web Application configuration (Blob cache, policies etc)
Use Test-SPContentDatabase
• Fix ALL warnings and errors
Upgrade Content Databases 2/2
Use Mount-SPContentDatabase
• Don’t forget the Super User and Super Reader
accounts!
• You can do several mounts in parallel
• Time it!
• Always do test mounts on production (like) hardware!
DEMO: TEST AND MOUNT A CONTENT DATABASE
SITE COLLECTION UPGRADE
Deferred Site Collection upgrade 1/2
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 even create new 2010 mode sites
Deferred Site Collection upgrade 2/2
Site Collection owner can do the upgrade
• Another feature with huge cloud focus
Site Collection Health Check
Evaluation Sites
• Don’t forget to configure outgoing e-mail!
Throttling rules
• Application Pool
• Content Database
PowerShell cmdlets for the Farm Admins
• If the Site Collection owner refuses to upgrade
Site Collection Health Check
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>]
Upgrade Evaluation sites
Site Collection owner can request an Evaluation Site
• Request-SPUpgradeEvaluationSiteCollection –Identity <URL>
A real copy of the Site Collection
Limitied lifetime
• Default 30 days
• $wa.DaysToExpire = <days>
• $site.EvaluationExpiry
Can be done several times
When Eval site is ok, the original site can be upgraded
Upgrade and Eval Site configurations
Web Application settings
• $wa.UpgradeReminderDelay
• $wa.UpgradeMaintenanceLink
• $wa.SendSiteUpgradeEmails
• $wa.AllowSelfServiceUpgradeEvaluation
• …
Self Service Site Collection Upgrades
• $site.AllowSelfServiceUpgrade
• …
Compatibility settings (Web Application)
• $wa.CompatibilityRange
Do the Site Collection upgrade
Site Collection Owner
• Site Settings > Site Collection Administration > Upgrade this Site Collection
• Check Upgrade Status
Farm Administrator
• Upgrade-SPSite –Idenitity <URL> -VersionUpgrade [-Unthrottled] [-QueueOnly]
The Upgrade queue
Site upgrades are placed in a queue
• First in, first out..
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>
Site Upgrade throttling
Web Application Setting
• $wa.SiteUpgradeThrottleSettings.AppPoolConcurrentUpgradeSessionLimit
• $wa.SiteUpgradeThrottleSettings.UsageStorageLimit
• $wa.SiteUpgradeThrottleSettings.SubwebCountLimit
Content Database Setting
• $db.ConcurrentSiteUpgradeSessionLimit
DEMO: SITE COLLECTION HEALTH CHECK AND UPGRADE
Upgrading My Site Host and My Sites
Always update the My Site Host first!
• My Sites cannot be upgraded before the My Site Host
• My Sites will automatically be upgraded when users hit
them
• Upgraded My Sites is required for new Social features
Other things worth to notice…
Upgrade logs now in ULS format!
Site Collection Maintenance Log
• New catalog in the Site Collection
Some bonus stuff, that even a dev can
appreciate…
Get-SPUpgradeActions
• Shows all upgrade actions in the farm
Get-SPPendingUpgradeActions
• Shows all pending upgrades for a given root
object
•Get-SPFarm | Get-SPPendingUpgradeActions -Recursive
THAT WASN’T TO HARD, RIGHT?
AND WE DIDN´T USE STSADM ONCE!
Summary
Plan, plan, plan…
Prepare for Claims Based AuthN, now!
Test, test, test…
Content Database Attach is the only upgrade method!
Let the Site Collection Administrators do the job
Better control of upgrade and transition period
questions?
WWW.WICTORWILEN.SE
@WICTOR
thank you.
SHAREPOINT AND PROJECT CONFERENCE ADRIATICS
ZAGREB, 11/28/2012