Disable site collection upgrades after migrating from SharePoint 2010 to 2013
When migrating SharePoint from 2010 to 2013, it depend of the migration strategy you choose how the end result will appear for your end users. Two different approaches when migrating to SharePoint 2013 can be:
- Migrate the farm, content and solutions from 2010 to 2013
- Migrate the farm to 2013, but keep the content and solutions in 2010-mode
Selecting the last approach requires the least effort, and could be preferred for several reasons:
- Reduce the scope of the migration to only include the farm. Less risk and effort needed.
- Migrate content and solution in a later stage after the new 2013 farm has been stabilized.
- Keep solutions who will have an end-of-life in near future without extra effort to migrate it.
- Customer has no functional requirements to adopt 2013 functionality at the current time for all or parts of the solutions, and only requires a platform upgrade.
Since the site collection administrators can on their own effort start the upgrade of their site, I will cover how to get control of this process by disabling the site collection upgrades. As an farm administrator you can then later re-enable this feature, or perform the migration on behalf of the owners (maybe preferred)-
How will a upgraded site collection in 2010-mode appear?
When visiting a site collection after the platform has been migrated, pretty much nothing has changed (good!) for the end users, except a light pink (not nice!) bar at the top reminding us that this site should be upgraded.
On the site collection upgrade page, an option to "Try a demo upgrade" is available. By default this request is put into a queue, and processed once each night. A copy of the site collection is created, and the site owner will receive an e-mail with the URL. After a fixed time of 30 days, the test site will be deleted.
The reason why this is running by night, is by my best guess because the source site will throw an error while the creation of the eval site runs. So don't be too tempted to run this timer job manually if the site is in use!
The messages on the top of the screen will only be visible to the site collection administrators, so the regular users (visitors, members or owners) will not see this at all.
Disable the self-service evaluation
In the "SharePoint 2013 Management Shell" run the following Powershell script.
[code language="powershell" highlight="3"]
$siteUrl = "http://sp2013"; # Change this one!
$site = Get-SPSite $siteUrl;
$site.AllowSelfServiceUpgradeEvaluation = $false;
[/code]
The option to create a evaluation site is no longer available for the site collection. The next step would be to disable the possibility for the site owners at all to perform the upgrade them self.
Disable the self-service site collection upgrade
In the "SharePoint 2013 Management Shell" run the following Powershell script.
[code language="powershell" highlight="3"]
$siteUrl = "http://sp2013"; # Change this one!
$site = Get-SPSite $siteUrl;
$site.AllowSelfServiceUpgrade = $false;
[/code]
Now both the options are disabled, and the pink bar at the top of the site is also removed.
What if I want to disable this on all site collections?
If you want to go all-in, this Powershell script disables both the evaluation site and self-service upgrade for all site collections within a web application:
[code language="powershell" highlight="3"]
$webAppUrl = "http://sp2013"; # Change this one!
Get-SPSite -Limit All -CompatibilityLevel 14 -WebApplication $webAppUrl | % { $_.AllowSelfServiceUpgrade = $false; $_.AllowSelfServiceUpgradeEvaluation = $false; }
[/code]
Summary
In this article we have seen how a site collection appear to the end-users after the farm has been migrated from SharePoint 2010 to 2013, and the content databases attached back on. With a few lines of PowerShell the administrator can disable both the ability to evaluate a upgraded site as well as perform the self-service upgrade.