upgrading to sharepoint 2013

Presented by:

Upgrade to SharePoint 2013

About Me

Veenus Maximiuk, MCITP, MCTS, MCPD, vTS

SharePoint Managing Architect

© 2013, Information Control Corporation2

spvee.wordpress.com

@SharePointVee

Linkedin.com/in/vmaximiuk

[email protected]

Agenda


Service Application & Content Upgrade

Demos

Claims Migration

Things to Know Before Upgrade

Q & AUpgrade Improvements


Things to Know Before Upgrade

Supported Upgrade


SharePoint 2007

(MOSS)

SharePoint Server 2010

SharePoint Server 2013

Windows SharePoint Services 3.0

SharePoint Foundation

2010

SharePoint Foundation

2013

Upgrade RequirementsServer Requirements• SharePoint Server

– Windows Server 2008 R2 SP1, or

– Windows Sever 2012 Datacenter or Standard

– NO Previous Versions of SharePoint

• Database Server

– SQL Server 2008 R2 SP1 (x64), or

– SQL Server 2012 (x64)

Client Requirements

• Office 2010 or Office 2013

– For full offline and integrated experience

– Office 2007 – limited integration

• Browser

– Internet Explorer 8, 9, and 10

– Chrome

– Firefox

– Safari


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)


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 rule


Claims Migration


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 advice



Service Application & Content Upgrade


Upgrading Managed Metadata ServiceStep-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 Service

Managed Metadata ServiceUpgrade Results



Managed Metadata ServiceTerm Store Upgrade Results


Upgrading User Profile ServiceStep-by-Step1. 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)

User Profile Service – Service ApplicationUpgrade Results


User Profile Service – Managed Profile ServiceUpgrade Results


Upgrade Managed Metadata Service Application

Demo


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.)

– Certificates© 2013, Information Control Corporation20

Content Upgrade Overview1. 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 -ShowFailed


Upgrade Content Databases

Demo


Upgrade Improvements


Upgrade Improvements

• Deferred Site Collection Upgrade

• Site Collection Health Checks

• Upgrade Evaluation Site Collections

• System Event Notifications

• Logging Changes

• Site Collection Upgrade Throttling


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 sites


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>]



Site Collection Health Checks

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 upgraded


Request for Site Evaluation



Creates Upgrade Evaluation Site Collections Timer Job

Site Collection Evaluation Site


Using Self-Service Site Collection Upgrades

Demo


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 Collection


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>© 2013, Information Control Corporation34

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 -Recursive© 2013, Information Control Corporation35

Thanks to Our Sponsors


Questions?


upgrading to sharepoint 2013

Technology