8/21/2019 Migrating SharePoint 2013
1/15
CA C ALLAHAN
HTTP://ABOUT.ME/CACALLAHAN
Migrating SharePoint2010 to 2013
8/21/2019 Migrating SharePoint 2013
2/15
Prerequisites
Experience administering SharePoint
Previous experience with migration helpful
Understanding of :
Windows Server
SQL Server
Basic PowerShell (particularly the SharePoint relatedcmdlets)
Willingness to learn about migrating SharePointand ability to sit through a presentation
Sense of humor*
8/21/2019 Migrating SharePoint 2013
3/15
Agenda
Migration Path
Services that can be migrated
Services that cant be migrated
Preparing for Migration
House cleaning
Documentation
Customizations Eight steps to Migration
8/21/2019 Migrating SharePoint 2013
4/15
Migration Path
Only SharePoint 2010 can be upgraded to SharePoint 2013
There is no in-place upgrade for SharePoint 2013
There is only database attach upgrad ing
There is no pre-upgrade check for 2010, only Test-SPCo ntentDatase before attaching
Site collections ca n have an upgrade hea lth chec k run before upgrade
Upgraded content da tabases generate an upgrade status report to make sure upgrade was successful
Site co llections are upgrad ed individually, and start out, by default in 2010 mode
A tempo rary evaluation upgrade (cop y) ca n be c reated for a site collection to see if there will be any problems upgrading before doing so pe rmanently
Services that can be upgraded
Search
User Profile Service
Metad ata Service
Secure Store
Business Connec tivity
PerformancePoint
Services that cannot be upgraded
State
Usage and Health
Web Analytics (not a service anymore, part of Search)
Foundation Search (also no longer available in 2013)
8/21/2019 Migrating SharePoint 2013
5/15
Preparing for Migration
House cleaning
Visual upgrades
Orphaned sites
Large lists with too many columns
Extraneous do cument versions
Site collections that need to be moved to their own content databases
Decommission PowerPoint broadcast sites and Fast search center
Remove unused web pa rts, features, solutions, sites, etc.
Documentation
Customizations
Some might migrate, many wont
Create at test environment to check your customizations as part of your prep
Authentica tion- convert classic web app lica tions to claims (or plan for it on the 2013 server)
Site templates may need to be rebuilt (unsupported zones, controls in non-standa rd places can ca use issues)
Convert C lassic to C laims web applications
For User Profile- export synchronization key
8/21/2019 Migrating SharePoint 2013
6/15
Documentation
Some simple tools to gather information about your SharePoint implementationbefore migration.
Stsadm o enumallwebsincludefeatures includewebpartsincludeeventreceiversincludec ustomlistview >c:\ enumallfarm.txt
PowerShell Script (spec ifically for SharePoint Foundation, but will work for Server too):http://technet.microsoft.com/en-us/library/ff645390(v=office.14).aspx
More thorough powershell script that generates numerous XML files:http://technet.microsoft.com/en-us/library/ff645391.aspx
Simple tool that generates hmtl file: http://spsfarmreport.codeplex.com/
To do file comparison between 2010 servers 14 hive, and the 2013 server, somesimple tools
WinMerge FreeFileSync (portable too)
WinDiff
SPDocKit (notfree, but a great documentation tool)
8/21/2019 Migrating SharePoint 2013
7/15
Converting Classic to
Claims Although 2013 can support classic mode a uthentication, claims based authentication is the default
Migration web application databases
You can migrate content databases from web applications that were using classic mode authentication to 2013 (notrecommended)
You can migrate content databases from web applications that were classic mode, then upgrade them on the 2013server (extra work)
You can upgrade the authentication mode on the web applications from classic to claims on the 2010 prior to migrating
(suggested approac h)
To do so:
$webapp name =read-host Enter Web Applica tion URL
$wa =Get-SPWebApp lication $webappname
$wa.UseC laimsAuthentica tion =$True
$wa.Update()
$account =read-host Enter PS Policy Account
$acc ount =(New-SPC laimsPrincipa l Identity $acc ount IndentityType 1).ToEncoded String()
$zp =$wa.ZonePolicies(Default)
$p =$zp.Add($ac co unt,PSPolicy)
$fc =$wa.Po licyRoles.GetSPecialRole(FullControl)
$p.PolicyRoleBindings.Add($fc)
$wa.Update()
$wa.MigrateUsers($True)
$wa.ProvisionGloba lly()
8/21/2019 Migrating SharePoint 2013
8/15
Migrating the User
Synchronization Encryptedkey The User Profile Service uses an encrypted key to
synchronize with Active Directory. To migrate thesync capabilities of UPS, you must export the key so
you can import it on the 2013 server. At elevated command prompt, at path: C:\ Program
Files\ Microsoft Office Servers\ 14.0\ SynchronizationService\ Bin
Run MIISKMU.exe
Its full name: Microsoft Identity Integration Server EncryptionKey Management utility
Selec t Export Key
Enter Farm Administrator acct and password
Spec ify filename and location
The file will be saved as a BIN, back it up. Be sure itsavailable to use on 2013 server during migration.
8/21/2019 Migrating SharePoint 2013
9/15
Eight steps to migration
1. Install SharePoint 2013 (dont forget languagepacks)
2. Copy customizations over to the new server3. Run configuration and configure farm settings
4. Move databases to new SQL Server
5. Migrate Service Applications (that can migrate)
6. Create Web Applications7. Test and Attach Databases
8. Upgrade site collections
8/21/2019 Migrating SharePoint 2013
10/15
Migrate Service
Applications Service Applications can vary in terms of
requirements and parameters
You can only migrate service applications using
PowerShell
Generally, migrating a service application from 2010to 2013 is very much like creating a new serviceapplication, except, if they need databases, theyrefer to the databases being migrated and possiblyoriginal passphrases (as in the case of Secure Store)
Create service application pool
Create service application, referring to databases toupgrade
Create proxy
8/21/2019 Migrating SharePoint 2013
11/15
Create Web Applications
You first need to create a web application to attach thecontent databases from the 2010 server
Make sure all settings and URLs are the same
You can use PowerShell or Central Administration
You can remove the database that gets createdautomatically
The migration itself should be done in PowerShell
To create a claims based web application (example):
$auth = New-SPAuthenticationProviderNew-SPWebApplication Name Portal ApplicationPool PortalApplicationPoolAccount contoso\ sp_portalapppool URLhttp://sp1 AuthenticationProvider$auth
Pro tip: Do not use convert-spwebapplication
8/21/2019 Migrating SharePoint 2013
12/15
Test and Attach
Databases SharePoint 2010 does not have a preupgrade
checker, however it does have a cmdlet to testindividual content databases before upgrading
them. Test-SPContentDatabase Name -
WebApplication
If there are errors they are often concerning server sidedependencies or the database is using c lassic modeand the new web application uses claims
Attaching the content database to the webapplication will upgrade it.
Mount-SPContentDatabase Name DatabaseServer WebApplication
Review database and upgrade status in GUI
8/21/2019 Migrating SharePoint 2013
13/15
Upgrade the Site
Collections Once the content databases are succ essfully attached to the new
SharePoint 2013 web applications the site collections they contain are no tupgraded automatically
They are still running as SharePoint 2010 site collections and can be upgradedindividually
As a site collection administrator
As a farm administrator
They can, of course, do mass upgrades
The easy way to upgrade a site collection or two:
Use the Banner at the top of the site collection page
Use the link in the Site Collec tion Settings page
Use PowerShell
Before upgrading
Run the Site Collection Health Check
Can C reate temporary Evaluation site collection
Select to create a temporary evaluation site collection (site name appended w ith eval)
Usually lasts 30 days (can be changed)
DO NO T do work on temporary site- it is not permanent!
8/21/2019 Migrating SharePoint 2013
14/15
Summary
Migration Path
Services that can be migrated
Services that cant be migrated
Preparing for Migration
House cleaning
Documentation
Customizations Eight steps to Migration
8/21/2019 Migrating SharePoint 2013
15/15
CA CALLAHAN
TWITTER: @CAC ALLAHAN
FACEBOOK GROUP: FACEBOOK.COM/GROUPS/CALLAHANSPF
HTTP://ABOUT.ME/CAC ALLAHAN
Migrating SharePoint2010 to 2013