philadelphia area sharepoint user group january 30, 2013

Philadelphia Area SharePoint User Group

www.PhillySharePoint.org

January 30, 2013

Chris MannRJB Technical [email protected]


Philadelphia AreaSharePoint User Group



SharePoint 2013 Site Collection Upgrades

for Site Owners



• This is focused on issues Site Collection Owners should be concerned with

• I will be covering (VERY lightly), the database attach

• I won’t be covering upgrading• User profiles• BCS• Or any other service application.

Site Collection Upgrades for 2013

Disclaimer




• Visual Upgrade is gone

• Takes some workflow off of farm administrators for the upgrade of less complex sites

• Empowers Site Collection Owners to • Play a more active role in the upgrade process for

their sites• Conduct a health check on possible upgrade

issues• Execute the upgrade

Intro




• Administrative Controls

• Primary resource for this was Technet and a trial run

Intro




• Export all of your Farm WSPs using PowerShell

http://sharepintblog.com/2011/06/04/exporting-solutions-packages-wsp-with-powershell/

• Install all server side customizations (ie. WSPs) and deploy to both the 14 and 15 hive

• Compatibility mode is not available through the UI

• You can create new site collections in 2010 (14) Compatibility Mode

Technical Prerequisites




Technical Prerequisites




• Test-SPContentDatabase (similar experience as upgrading to 2010)

• Mount-SPContentDatabase (similar experience as upgrading to 2010)

• Added security policy in CA for my account• $w.MigrateUsers($true)• $w.ProvisionGlobally()

Technical PrerequisitesClaims-based authentication is an essential component to enable the advanced functionality of SharePoint 2013

By default, new Web Applications are set to use Claims-based authentication.




• Notification above the ribbon

• Start now or wait?

What do I see?




• Site Template did not work due to missing web analytics feature.

• The user experience is exactly the same as being in 2010 – not like the 2007 to 2010 visual upgrade

• Web parts worked

• Master page and other branding worked

• Some 3rd party components worked • Bamboo List Rollup – had issue with installing licensing manager, otherwise appeared

as though it would have• Chris O’Brien’s Feature Upgrade tool

My Experience




• Enables site collection administrators to see their site’s content in a new, separate copy of the site that is running on the SharePoint 2013

• Unlike Visual Upgrade in 2010, it is a complete and separate copy

• It is accessible by Search and Timer Jobs

• Default expiration is 30 days (configurable)

• Email notification to Site Collection owners when complete

Upgrade Evaluation Site Collection




• If you have an Enterprise version of SQL Server, the Create Upgrade Evaluation Site Collections job timer takes a snapshot of the database and reads the data from the snapshot to a destination database (with the source database being the default target). This doesn’t affect the read-only status of the source site throughout the whole process.

• For other versions of SQL Server that do not have snapshot capabilities, the Create Upgrade Evaluation Site Collections job timer backs up a site collection and restores it to a new URL. This makes the source site read-only for the whole duration of the process.




• Are web parts working?

• Are web parts in the correct location?

• Do pages customized in Designer look right?

• Service applications • Excel Web Access• Forms

• Workflows

• Large lists – throttling is turned on by default

• Branding /Styling

Things to watch out for




Upgrade ThrottlesLevel

Maximum number of site collections that can be upgraded at a time

Property that controls the throttle setting

Web applicationDefault is 5 per web application instance. Additional requests are queued.

SPWebApplication.SiteUpgradeThrottleSettings AppPoolConcurrentUpgradeSessionLimit

Content database Default is 10 per content database. Additional requests are queued.

SPContentDatabase.ConcurrentSiteUpgradeSessionLimit

Content of a site collection (size and number of subwebs)

Default is that a site that is more than 10 MB, or has more than 10 subwebs, cannot be upgraded in a self-service manner by the site collection administrator, but must be upgraded by the farm administrator.

SPWebApplication.SiteUpgradeThrottleSettings UsageStorageLimit




Upgrade In Progress




Thank you!

philadelphia area sharepoint user group january 30, 2013

Documents