id stringlengths 14 16 | text stringlengths 2 3.14k | source stringlengths 45 175 |
|---|---|---|
1af434f4ace8-1 | In-place with backward compatibility - You install an update in stages and use postponed upgrade (that is, do not run the upgrade process on the databases or site collections) with backward compatibility to reduce downtime.
Database attach: This approach is more complex than an in-place update, and it requires ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/prepare-to-deploy-software-updates |
1af434f4ace8-2 | Secure store service
Site collections
Logs
Apps
For more information about how to determine what you need to back up and the method to use, see Prepare to back up and restore farms in SharePoint Server . After you determine the farm elements that you will back up, refer to the articles listed in Bac... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/prepare-to-deploy-software-updates |
1af434f4ace8-3 | Determine whether related items need to be updated
Consider whether the following related items need to be updated when you update your farm:
Filter packs
Language packs
All these items are updated separately from an update of SharePoint 2013. Check to see if any updates to these items are available... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/prepare-to-deploy-software-updates |
1af434f4ace8-4 | Note
You must use the name Updates for this updates folder. If you use the SupdateLocation="path-list" property to specify a different location, Setup stops responding.
You can now use this location as an installation point, or you can create an image of this source that you can save to media or save as an ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/prepare-to-deploy-software-updates |
0c8d3603e5d2-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Administrators update SharePoint 2013 to deploy or update assemblies that provide functionality and to upgrade databases. A successful update follows a methodical approach that minimizes interruptions in service. Review information in t... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-1 | software update
A software update is any update, update rollup, service pack, feature pack, critical update, security update, or hotfix that is used to improve or to fix a software product that is released by Microsoft Corporation.
upgrade
Process by which you change an environment to use a newer vers... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-2 | Administrators can use the SharePoint Central Administration website or Microsoft PowerShell to monitor the status of an update.
Intended audience and scope
Information in this article is for all IT professionals who maintain SharePoint 2013. However, specific instructions to install a software update are i... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-3 | The second step in the patch phase is the binaries deployment step. In this step, the installer copies support dynamic link library (.dll) files to the appropriate directories on the server that is running SharePoint 2013. This step ensures that all the web applications are running the correct version of the binary fil... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-4 | Software update deployment cycle
The cycle that is used for upgrading SharePoint 2013 farms and servers also applies to deploying software updates, which are a subset of an upgrade phase. We recommend that you use the update cycle in the following illustration as a guide to deploy software updates.
Learn
Du... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-5 | Prepare
To prepare for the software update, document the environment and plan an update strategy to ensure that the update will go as planned in the expected downtime window.
Document the environment
You document the environment to determine what is unique in your farm. You can use several techniques to gather in... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-6 | The two final requirements for the update strategy are a communication plan and an update schedule.
It is important to communicate with site owners and users about what to expect during an upgrade. An administrator should inform users about downtime and the risk that the upgrade may take longer than expected or that ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-7 | Build a test farm
Build a test farm that represents the production environment. We recommend that you use a copy of the production data to determine potential problem areas and monitor overview system performance during the upgrade. The key indicator is the length of time it takes from the beginning to the end of the... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-8 | Monitor progress
The refined techniques that you use to monitor the software update in the test environment apply when you deploy the update in the production environment. Use the Upgrade and Migration page in Central Administration to monitor available status indicators. This feature enables live monitoring and pr... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-9 | Hyperlink to the Patch Deployment State page
Installed
Indicates that no action is required
Not applicable
Missing/Required
Displayed if a product is required on each server or if a patch for a specific .msi file is located on one server but not on the server for which this status is shown... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
0c8d3603e5d2-10 | User interface version mismatch
HTML and XHTML compliance
Other issues may include missing templates, user identifiers, and content issues such as large lists.
Data issues
Data issues result from the condition of the farm databases and can include all or some of the following:
Connectivity issues to d... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/software-updates-overview-for-sharepoint-server-2013 |
c9fa9e68998b-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
This article describes how to deploy custom features through solution packages to a SharePoint Server 2013 farm that has been upgraded from SharePoint Server 2010. It includes information and procedures for supported scenarios. It also ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-1 | Microsoft PowerShell cmdlets that you need to be familiar with
For the purposes of this article, you should be familiar with the following Microsoft PowerShell cmdlets:
Name
What does this do?
Example
Add-SPSolution
Adds the solution to the farm's solution store.
Add-SPSolution -Lit... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-2 | Figure: Add custom features in the upgrade process
You can use a solution package to add your customizations to the new farm. A solution package is a distribution package that delivers your custom SharePoint 2013 development work to the web servers or the application servers in your server farm. You can use solutio... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-3 | The Install-SPSolution PowerShell cmdlet also includes a compatibility-level parameter to deploy the solution package to locations in the root folder that are designated for either SharePoint 2010 mode or SharePoint 2013 mode site collections. These are the "14" and "15" root folders (hives), and when you deploy the ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-4 | Feature masking involves using a new and separate solution package for the same feature for upgraded sites and site collections (when a feature is scoped to a site or site collection). Feature masking allows upgraded site collections to automatically find and use the correct custom feature assemblies. This way, your us... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-5 | Scenario 3
Legacy solution for SharePoint 2010 compatibility mode, and build a new solution to implement new functionality for SharePoint 2013.
Note
For details about where solution package files are installed in the farm based on compatibility level, see the TechNet blog post, Planning Deployment of... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-6 | Add-SPSolution -LiteralPath c:\Solution.wsp
Deploy the solution package.
Deploy the solution package for SharePoint 2010 compatibility. You can do this by using the Install-SPSolution PowerShell cmdlet. Make sure to set the -CompatibilityLevel parameter to 14 . For example:
Install-SPSolution -Identity S... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-7 | In this scenario, the custom feature works correctly in SharePoint Server 2010. You want to build a solution package by adding this feature to a SharePoint 2013 farm, but you also want to make sure that you can incrementally add functionality for site collections in SharePoint 2013 mode that are using this solution pac... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-8 | else {/*New O15 implementation*/}}
}
By doing this, the same feature assembly serves both SharePoint 2010 and SharePoint 2013 versions of the feature. Feature masking isn't used in this scenario either because you're not only using the same feature assembly but also the same solution package. The same files for the ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-9 | Note
The CompatibilityLevel parameter in Install-SPSolution Microsoft PowerShell cmdlet also allows you the option to install a solution package to both the 14 and 15 root directories at the same time. You can do this by using the values of "14,15" or "All". For example: > Install-SPSolution -Identity Solution.... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-10 | Feature masking requirements
Requirement
Same or different
Solution Package - 2010 mode example
Solution Package - 2013 mode example
Solution package names
Different
POC14
POC15
Solution package IDs
Different
000000-0000-0000-0000-000000000000
11111111-1111-1111-1... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-11 | Add-SPSolution -LiteralPath c:\POC15.wsp
Deploy the solution package for SharePoint 2010 compatibility. You can do this through the Install-SPSolution PowerShell cmdlet. Make sure to set the -CompatibilityLevel parameter to 14 . For example:
Install-SPSolution -Identity POC14.wsp -CompatibilityLevel 14 -GAC ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-12 | Uninstall-SPSolution -Identity POC14.wsp -CompatibilityLevel 14
Important
Make sure to use the CompatibilityLevel parameter to " 14 " to retract the solution package for 2010 compatibility mode only. For example: Uninstall-SPSolution POC14.wsp -CompatibilityLevel 14
Remove the solution package from th... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
c9fa9e68998b-13 | Note
For more information about the branding considerations you need to make when you upgrade site collections in SharePoint 2013, see Branding issues that may occur when upgrading to SharePoint 2013 .
See also
Other Resources
Create a plan for current customizations during upgrade to SharePoint 2013
S... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/deploy-custom-features-to-upgraded-site-collections-in-sharepoint-server-2013 |
ec8a9e984f2e-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Content type syndication, or content type publishing, occurs when you publish a content type from a content type "hub" site collection to one or more "consuming" site collections. For more information, see Introduction to content types... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-1 | Two consuming site collections that are also based on the Document Center template
The content type hub publishes documents and document set content types to these site collections.
The following illustration shows this example environment before the start of the upgrade process.
SharePoint 2010 farm with con... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-2 | Back up the data and create a duplicate content type hub in the SharePoint 2010 environment
If you want to continue to use any of the consuming site collections in the 2010 environment but upgrade others, you must upgrade your environment so that you have a 2010 version of the content type hub and a 2013 version. The... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-3 | Create a web application to host a duplicate of the content type hub.
For information, see Create a web application (SharePoint Server 2010) .
Use the Restore-SPSite Microsoft PowerShell cmdlet to restore a copy of the original content type hub. Use the following syntax:
Restore-SPSite <URL> -path <path>... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-4 | New SharePoint 2013 farm
Use SQL Server Management Studio to restore the databases for the Managed Metadata service application and the two content databases for the original content type hub (ContentTypeHub1) and consuming sites, and the duplicate content hub.
Use PowerShell to create a Managed Metadata serv... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-5 | Note
When you upgrade the content database, the site collections remain in 2010 mode in the 2013 farm. Do not upgrade the site collections to 2013 mode yet. You upgrade the site collections later in this process.
Use the Set-SPMetadataServiceApplication Microsoft PowerShell cmdlet to configure the upgraded Ma... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-6 | Create additional Managed Metadata service applications and republish the content types
Now you are ready to create the Managed Metadata service applications that will serve content type hubs and consuming site collections running in 2010 mode in both the 2010 farm and the 2013 farm. After you create and configure th... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-7 | For more information, see Update a managed metadata service connection .
In Central Administration, create a Managed Metadata service application (Managed Metadata 3) and set the Content Type Hub property to the original content type hub in the 2010 environment (ContentTypeHub1 in the 2010 farm).
When you ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-8 | On the 2013 duplication content type hub that is in 2010 mode (ContentTypeHub3), republish all of the content types that were published before (Doc1 and DocSet1).
For more information, see Publish a content type from a content publishing hub .
Republish the content types in the 2010 environment:
On the... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-9 | This service application is the default storage location for Keywords.
This service application is the default storage location for column specific term sets.
This enables ContentTypeHub2 in the 2010 farm to consume terms from the term store in the Managed Metadata 1 service application.
On the 2013 farm,... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-10 | This service application is the default storage location for Keywords.
This service application is the default storage location for column specific term sets.
Consumes content types from the Content Type Gallery at <URL>.
Push-down Content Type Publishing updates from the Content Type Gallery to sub-sites a... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-11 | When you add a content type, you must make sure that the content type ID is the same on all three Content Type Hubs. To do this, follow this procedure:
On the 2013 farm, on the ContentTypeHub1, manually create the new content type and publish it.
Identify the content type ID for that content type.
Tip
You... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
ec8a9e984f2e-12 | Add the extracted property to the corresponding content type on both of the other content type hubs (ContentTypeHub2 and ContentTypeHub3).
Republish the updated content type from the other content type hubs (ContentTypeHub2 and ContentTypeHub3).
The following article on MSDN provides an example of how to use the ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/how-to-upgrade-an-environment-that-uses-content-type-syndication-sharepoint-serv |
0241c0e87d19-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
This article describes how to perform a search-first migration from Microsoft FAST Search Server 2010 for SharePoint to SharePoint Server 2013.
Introduction to search-first migration (SharePoint Server 2013)
Upgrading from FAST Sear... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/search-first-migration-from-fast-search-server-for-sharepoint-2010-to-sharepoint |
0241c0e87d19-1 | Running your system in mixed mode means that you do not upgrade the content of your farm or the site collection to SharePoint 2013. The FAST Search Server 2010 for SharePoint farm can continue to provide other FAST Search Server 2010 for SharePoint functionality for your organization. FAST Search Server 2010 for ShareP... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/search-first-migration-from-fast-search-server-for-sharepoint-2010-to-sharepoint |
0241c0e87d19-2 | On the SharePoint 2013 SQL Server, install:
Microsoft .NET Framework version 4.5
PowerShell Snapins for SQL Server
On the FAST Search Server 2010 for SharePoint farm, back up these databases:
FAST Search Administration database
FAST Content Search Service Application database
FAST Quer... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/search-first-migration-from-fast-search-server-for-sharepoint-2010-to-sharepoint |
0241c0e87d19-3 | Yes
Crawl rules
Yes
Crawl schedules
Yes
Scopes and scope filters In most cases, scopes and scope filters work after migration, but you cannot edit or change them. Scope filters usually contain Path: or Site: restrictions. SharePoint 2013 does not tokenize the URLs. When you... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/search-first-migration-from-fast-search-server-for-sharepoint-2010-to-sharepoint |
0241c0e87d19-4 | Rank profile
No
Note
A FAST Search Server 2010 for SharePoint rank profile can't be converted to a SharePoint 2013 ranking model.
Features with limitations
When you run SharePoint 2013 in mixed mode, certain features will function with limitations. You'll have to use manual workarounds for t... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/search-first-migration-from-fast-search-server-for-sharepoint-2010-to-sharepoint |
0241c0e87d19-5 | Site refiner
In SharePoint 2013, the managed property SPSiteURL is used to populate the site refiner. If there are problems with the site refiner after migration, verify that: The properties Basic:4 and ows_SPSiteURL are mapped to SPSiteURL . RespectPriority of SPSiteUrl is set to true . ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/search-first-migration-from-fast-search-server-for-sharepoint-2010-to-sharepoint |
e25334fb4ce3-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
My Sites are site collections owned by the user for the user to store their documents, connect with other users, follow and discover content, and so on. Upgrading My Sites differs from upgrading other site collections because My Sites c... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-1 | Mixed user interface modes. During an upgrade, a user's My Site may display both the SharePoint Server 2010 and SharePoint Server 2013 master pages. When this happens, the My Site is displaying mixed user interface modes which may cause confusion for users. The mixed user interface modes are affected by the combinatio... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-2 | Important
This list highlights some important things to consider when you perform an upgrade of My Sites. For a detailed discussion on upgrades, see Get started with upgrades to SharePoint 2013
Procedure to upgrade My Sites
The following list summarizes some of the upgrade activities for a My Site upgrade ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-3 | Upgrade the Managed Metadata service and User Profile service applications using the database attach method. For more information, see Upgrade service applications to SharePoint 2013 . Ensure the My Site Host URL field on the User Profile Service application is left blank because this field will be updated durin... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-4 | Verify that the My Site Host URL field on the User Profile Service application has the correct URL users should use to access the My Sites web application. For more information, see Configure My Site settings for the User Profile service application .
Upgrade the My Site Host from a SharePoint Server 2010 My Sit... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-5 | Alternative procedure for upgrading My Sites
You may have constraints that restrict you from upgrading your My Sites to SharePoint Server 2013 My Sites. For example, you are upgrading your entire server farm but you have customizations on your My Sites that you have not tested on SharePoint Server 2013. In this s... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-6 | Forced upgrade. If you use the forced upgrade path, users will not experience an automatic upgrade the first time they visit their My Site. Instead, their My Site will already be upgraded for them. A farm administrator can perform a forced upgrade of all My Sites in the farm by running the following command at the Sh... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-7 | Deferred site collection upgrade. The deferred site collection upgrade process uses the compatibility range settings to allow administrators to upgrade their databases and keep their site collections in SharePoint Server 2010 mode. When the compatibility range settings allow both 2010 user interface mode and 2013 user... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
e25334fb4ce3-8 | Note
The upgrade of the personal site collection is not an instant process. The My Site is added to an upgrade queue. When the upgrade starts, the My Site remains available to use during the upgrade process. Users can work on their documents throughout the upgrade process. The My Site Host and personal site collectio... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-my-sites-to-sharepoint-server-2013 |
bde59fedcb0b-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Even though site collection administrators can now upgrade their own sites to SharePoint 2013, server farm administrators can still control when and whether a site collection is upgraded by managing the upgrade queue. You can also view ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-1 | An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.
Note
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see Add-SPShellAdmin .
... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-2 | db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are running the PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.
Note
If you do not have permissions, cont... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-3 | Where:
<URL> is URL for the web application that you want to affect.
<Value> is the numeric value that you want to set for the delay (for example, 10 for 10 days).
<LinkURL> is a link where the user can find more information.
At the PowerShell command prompt, type the following command to change ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-4 | An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.
Note
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see Add-SPShellAdmin .
... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-5 | At the PowerShell command prompt, type the following commands to view the maximum, minimum, and default settings for a specific range:
[Microsoft.SharePoint.SPCompatibilityRange]::<RangeName>
Where:
RangeName is one of the following values: OldVersions , NewVersion , AllVersions .
This command returns ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-6 | Where:
<URL> is URL for the web application that you want to change.
RangeName is one of the following values: OldVersions , NewVersion , AllVersions .
At the PowerShell command prompt, type the following command to change the values for the CompatibilityRange manually:
$wa=Get-SPWebApplication <... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-7 | For more information, see Get-SPWebApplication .
Control the queue for upgrades of sites to SharePoint 2013
Every site that is set to upgrade is added to the queue, even if it is processed immediately. A site is removed from the queue after it is upgraded, or if it has encountered an error that must be address... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-8 | Verify that you have the following memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are running the PowerShell cmdlets.
An administrator can use the Add-SPSh... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-9 | Get-SPSiteUpgradeSessionInfo -Site <http://site>
Where:
<http://site> is URL for the site collection you want to add to the upgrade queue.
For more information, see Get-SPSiteUpgradeSessionInfo .
To add a site collection to the upgrade queue, at the PowerShell command prompt, type the following command... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-10 | To view the upgrade throttle settings for a web application by using PowerShell
Verify that you have the following memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-11 | For more information, see Get-SPWebApplication .
You can change the upgrade throttle settings for a web application. The following procedure provides steps to change the upgrade throttling settings for a web application.
To change the upgrade throttle settings for a web application by using PowerShell
Verify t... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-12 | For more information, see Set-SPWebApplication .
The following procedure provides steps to view upgrade throttling settings for a content database.
To view the throttle settings for a content database by using PowerShell
Verify that you have the following memberships:
securityadmin fixed server role o... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-13 | To change the throttle settings for a content database by using PowerShell
Verify that you have the following memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you a... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-14 | To request an upgrade evaluation site collection by using PowerShell
Verify that you have the following memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are run... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-15 | db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are running the PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.
Note
If you do not have permissions, cont... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-16 | Verify that you have the following memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are running the PowerShell cmdlets.
An administrator can use the Add-SPSh... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-17 | db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are running the PowerShell cmdlets.
An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.
Note
If you do not have permissions, cont... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-18 | <http://site> is the URL of the site collection.
This command returns the compatibility level and upgrade information (such as a pointer to the log file) for the specified site collection. If the compatibility level is "15," then it has been upgraded to 2013 mode. For more information, see Get-SPSite .
To v... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
bde59fedcb0b-19 | To view upgrade status for all site collections by using PowerShell
Verify that you have the following memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are runn... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/manage-site-collection-upgrades-to-sharepoint-2013 |
fe3635b3b015-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Use these steps in your test environment to identify any issues before you upgrade your production environment. And review your upgraded sites to fix any issues after you have upgraded a site collection.
When you perform tests before ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/review-site-collections-upgraded-to-sharepoint-2013 |
fe3635b3b015-1 | For farm administrators: The site collection upgrade log file and the upgrade error log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\15\LOGS. The logs are named in the following format: SiteUpgrade- YYYYMMDD-HHMMSS-SSS .log, where YYYYMMDD is the date and HHMMSS-SSS is the ti... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/review-site-collections-upgraded-to-sharepoint-2013 |
fe3635b3b015-2 | Are there any broken Web Parts pages and are the Web Parts displayed correctly (in the correct zone, location, and size)?
Either in Edit Mode for the page in the browser or in SharePoint Designer 2013, drag the Web Part into the correct zone or modify the Web Part properties to correct any sizing or positioning pro... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/review-site-collections-upgraded-to-sharepoint-2013 |
fe3635b3b015-3 | Are your Excel Web Access Web Parts working correctly? Did you create your connections again correctly? Are external data sources still working?
Verify all connections and external data sources.
Tip
If you have problems with a Web Part, append ?contents=1 to the end of the URL syntax (http:// site... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/review-site-collections-upgraded-to-sharepoint-2013 |
fe3635b3b015-4 | Are the appropriate cascading style sheet colors and styles used in the appropriate locations?
Verify or fix the links to the cascading style sheet file. Verify the link on the master page.
Theme choices are different in SharePoint 2013 - which theme do you want to use?
Your site's home page, or other p... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/review-site-collections-upgraded-to-sharepoint-2013 |
fe3635b3b015-5 | Are your customizations still in place?
Determine whether you have only one issue or a larger problem with the whole page. If you added a brand-new page to your original site (for example, if you replaced Default.aspx with a different file instead of changing the existing Default.aspx file), the new page has no ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/review-site-collections-upgraded-to-sharepoint-2013 |
fe3635b3b015-6 | If you want the new functionality and features, you must reset any customized pages to use the template. Resetting the page basically discards the customizations and attaches your page to the appropriate master page. Any customizations that you want can then be transferred to the master page instead of being stored in ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/review-site-collections-upgraded-to-sharepoint-2013 |
9b2c494331b5-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
After a server farm administrator has upgraded the databases, site collection administrators can upgrade individual site collections. When site collection administrators first browse to their sites after the database has been upgraded, ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-a-site-collection-to-sharepoint-2013 |
9b2c494331b5-1 | Watch the SharePoint 2013 Upgrade: Phase 5 video
Important
If you upgrade from SharePoint Server 2010 to SharePoint 2013, there are special considerations for My Sites. (My Sites are not available in SharePoint Foundation 2013.) Make sure that you upgrade the My Site Host site collection before you allow users ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-a-site-collection-to-sharepoint-2013 |
9b2c494331b5-2 | Verify that the user account that performs this procedure is a site collection administrator.
On the Site Settings page for the site collection, in the Site Collection Administration section, click Site collection upgrade .
On the Step up to SharePoint 2013 page, click Try a demo upgrade .
This option sta... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-a-site-collection-to-sharepoint-2013 |
9b2c494331b5-3 | Important
You cannot upgrade FAST Search Center sites to the 2013 experience. Existing FAST Search Center sites can continue to work in 2010 mode after upgrade. If you want the new functionality, you must create new enterprise Search Center sites in 2013 mode. > To enable users to preview Word or PowerPoint search r... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-a-site-collection-to-sharepoint-2013 |
9b2c494331b5-4 | Errors or warnings
When the upgrade started
Where you can find the upgrade log file
After the upgrade is complete, the Upgrade status page is displayed in the new user interface with the message, Upgrade Completed Successfully.
Click Let's see the new site to go to the home page.
Farm administ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/upgrade-a-site-collection-to-sharepoint-2013 |
e790a535552b-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
SharePoint 2013 includes a set of rules that you can run against a site collection to verify that it is working as expected. These rules are part of the site collection health checks. You can run the health checks from the Site Settings... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/run-site-collection-health-checks-in-sharepoint-2013 |
e790a535552b-1 | befe203b-a8c0-48c2-b5f0-27c10f9e1622
Customized Files
This rule checks for any files that were customized (or unghosted) in the site collection or subsites. When run in repair mode, it can reset the page to the default (reghost the file).
cd839b0d-9707-4950-8fac-f306cb920f6c
Missing Galleries ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/run-site-collection-health-checks-in-sharepoint-2013 |
e790a535552b-2 | Unsupported MUI References
This rule checks to make sure that the multi-user interface elements that are used by the site collection exist and are referenced correctly by the site collection.
6da06aab-c539-4e0d-b111-b1da4408859a
Before you begin
This is the first step in upgrading a site collect... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/run-site-collection-health-checks-in-sharepoint-2013 |
e790a535552b-3 | Verify that you have the following memberships:
securityadmin fixed server role on the SQL Server instance.
db_owner fixed database role on all databases that are to be updated.
Administrators group on the server on which you are running the PowerShell cmdlets.
Either a site collection administrator... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/run-site-collection-health-checks-in-sharepoint-2013 |
e790a535552b-4 | An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.
Note
If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about PowerShell permissions, see Add-SPShellAdmin .
... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/run-site-collection-health-checks-in-sharepoint-2013 |
91c662d99da6-0 | APPLIES TO: 2013 2016 2019 Subscription Edition SharePoint in Microsoft 365
Claims-based authentication is an essential component to enable the advanced functionality of SharePoint 2013. To move classic-mode web applications from SharePoint 2010 Products to SharePoint 2013, you can convert them to claims-based ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/migrate-from-classic-mode-to-claims-based-authentication-in-sharepoint-2013 |
91c662d99da6-1 | Administrators group on the server on which you are running PowerShell cmdlets.
You must read about_Execution_Policies ( https://go.microsoft.com/fwlink/p/?LinkId=193050 ).
Add memberships that are required beyond the minimums above.
An administrator can use the Add-SPShellAdmin cmdlet to grant permission... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/migrate-from-classic-mode-to-claims-based-authentication-in-sharepoint-2013 |
91c662d99da6-2 | From the PowerShell command prompt, type the following to perform user migration:
$wa.MigrateUsers($true)
After user migration completes, type the following from the PowerShell command prompt to perform provisioning:
$wa.ProvisionGlobally()
For more information, see New-SPClaimsPrincipal .
After you ... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/migrate-from-classic-mode-to-claims-based-authentication-in-sharepoint-2013 |
91c662d99da6-3 | Note
When you attach the SharePoint 2010 Products content databases to the SharePoint 2013 claims-based web application, the databases will be upgraded to the SharePoint 2013 database format but will not be claims-enabled.
Convert SharePoint 2010 Products classic-mode web applications to SharePoint 2013 claim... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/migrate-from-classic-mode-to-claims-based-authentication-in-sharepoint-2013 |
91c662d99da6-4 | Change to the directory where you saved the file.
At the PowerShell command prompt, type the following command:
$ap = New-SPAuthenticationProvider -UseWindowsIntegratedAuthentication -DisableKerberos
New-SPWebApplication -name "ClaimsWebApp" -Port 80 -ApplicationPool "ClaimsAuthAppPool" -ApplicationPoolAccoun... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/migrate-from-classic-mode-to-claims-based-authentication-in-sharepoint-2013 |
91c662d99da6-5 | If necessary, attach a third SharePoint 2010 Products content database to the new SharePoint 2013 claims-mode web application, and verify that the content database working correctly after you have attached it.
From the PowerShell command prompt, type the following:
Convert-SPWebApplication -Identity <yourWebA... | https://learn.microsoft.com/en-us/sharepoint/upgrade-and-update/migrate-from-classic-mode-to-claims-based-authentication-in-sharepoint-2013 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.