SharePoint On Premises migration – Basic question – answers / points / best practices / interview questions to know while migrating from MOSS / SharePoint 2010 to 2016

Hi All,

Greetings for the day 🙂 LIFE IS BEAUTIFUL 🙂

On every weekend we are starting sharing basic question and answers (may help to prepare interview , certifications, migration, help to understand basic concepts…) related to Microsoft cloud technologies (Azure, Azure AD, SharePoint, Microsoft 365, Teams, Power Platform and so on).

In last three weeks we shared interview questions about :

• Azure =>https://knowledge-junction.in/2021/05/15/azure-basic-questions-and-answers-help-to-prepare-interviews-and-respective-certifications/
• Azure AD => https://knowledge-junction.in/2021/05/02/azure-ad-basic-questions-and-answers-help-to-prepare-interviews-and-respective-certifications/
• SharePoint 2013 =>https://knowledge-junction.in/2021/05/08/sharepoint-2013-basic-questions-and-answers-help-to-prepare-interviews-respective-certifications-and-migration/

In this article I’ll share some questions related to migration from SharePoint 2010 to SharePoint 2016 on-premises environment (since currently working on SharePoint on-premises migration project).

Lets start the fun 🙂 :

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. Which are those 7 rules

Site collection health check rules

Rule name	Description	Rule ID
Conflicting Content Types	This rule checks for conflicts between existing content types and content types that are created when we upgrade the site to SharePoint 2013 A conflict occurs when both content types have the same name.	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	This rule checks for all default galleries and reports if any are missing from the site collection or subsites	ee967197-ccbe-4c00-88e4-e6fab81145e1
Missing Parent Content Types	This rule checks for missing parent content types If a missing parent content type is found, you can either delete the orphaned content type or associate the orphaned content type with a different parent content type	a9a6769f-7289-4b9f-ae7f-5db4b997d284
Missing Site Templates	This rule checks to make sure that the template the site is based on is available and reports if any elements are missing	5258ccf5-e7d6-4df7-b8ae-12fcc0513ebd
Unsupported Language Pack References	This rule checks to make sure that the language packs that are used by the site collection exist and are referenced correctly by the site collection	99c946f7-5751-417c-89d3-b9c8bb2d1f66
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

How we can run health check before upgrading the site collection to SP 2013? from UI

• We can run health check either through Site collection itself or through PowerShell
• Site collection health check from Site Collection itself
• – Navigate to Settings page => <Site Collection>/_layouts/15/settings.aspx
• – Note you must be “Site Collection Administrator” to perform this activity
• – On Settings page in second column under the row “Site Collection Administration“, click on the link “Site collection health checks” as shown in below fig

• – We will be redirected to – “Site Collection Health Checks” page – <Site Collection> / /_layouts/15/sitehealthcheck.aspx as shown in below fig

Which are the PowerShell commands to run the site collection pre-upgrade health checks by using PowerShell

• Test-SPSite
  • The Test-SPSite cmdlet runs one or all site collection health checks on the site collection and its contents.
  • This cmdlet reports the rules which were run and provides a summary of the results

Test-SPSite
    [-Identity] <SPSiteURL>
    [-AssignmentCollection <SPAssignmentCollection>]
    [-RuleId <Guid>]
    [-RunAlways]

• Example :

Test-SPSite https://<site name>/sites/knowledgejunction1

Test-SPSite https://<site name</sites/knowledgejunction1 -Rule "ee967197-ccbe-4c00-88e4-e6fab81145e1"

What permissions are required to run site collection health checks using PowerShell

1. Verify that you have the following memberships:
   • securityadmin fixed server role on the SQL Server instance
   • Administrators group on the server on which you are running the PowerShell cmdlets
   • db_owner fixed database role on all databases that are to be updated
   • Either a site collection administrator or be granted full read (for test mode) for the web application by policy

How we can verify upgrade status of specific site collection

$sitecollection = Get-SPSite <http://sitecollection>
# Sets a variable for the site collection
$sitecollection.CompatibilityLevel
# Returns the compatibility level for the site collection (either 14 or 15 for 2010 or 2013 mode)
$sitecollection.UpgradeInfo
# Returns the upgrade information for the site collection

What is upgrade evaluation site collection

• Site collection administrators can request a preview of their site collection. This preview site is called an upgrade evaluation site collection
• Farm administrators can request an upgrade evaluation site collection by using PowerShell
• An upgrade evaluation site collection enables us to see your site’s content in a new, separate copy of the site that is running on the SharePoint 2013
• When we request an evaluation site collection, the request is added to a Timer job – “Create Upgrade Evaluation Site Collections” which runs once a day
• We will receive an e-mail message when the upgrade evaluation site is available.
• This might take up to 24 hours.
• The message includes a link to the evaluation site.
• Upgrade evaluation site collections are set to automatically expire (after 30 days by default)
• If our evaluation site collection expires before you have finished evaluating the changes, we can request another upgrade evaluation site collection

How to request upgrade evaluation site collection from UI

• Verify that the user account that performs this procedure is a site collection administrator
• Navigate to Settings page => <Site Collection>/_layouts/15/settings.aspx
• Note you must be “Site Collection Administrator” to perform this activity
• On Settings page in second column under the row “Site Collection Administration“, click on the link “Site collection upgrade” as shown in below fig

• On the Step up to SharePoint 2013 page, click Try a demo upgrade.This option starts the process of generating an upgrade evaluation site collection
• In the Create Upgrade Evaluation Site Collection box, click Create Upgrade Evaluation Site Collection.A box opens and informs you that a demo site request was received.
• Click Close to close the box
• We will receive an e-mail message when the upgrade evaluation is available
• The e-mail message will contain a link to the site collection
• Review the site and confirm that our site collection will look and behave as expected in the new user interface

How 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 running the PowerShell cmdlets.
  • Either a site collection administrator or be granted full control (for repair mode) for the web application by policy
• Start the SharePoint Management Shell

Request-SPUpgradeEvaluationSiteCollection -identity URL to site

How to upgrade site collection by using PowerShell

To upgrade a single site collection in a database by using PowerShell

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

Upgrade-SPSite <http://site> -VersionUpgrade [-Unthrottled]

How to upgrade all site collections in database together in 2013 mode?

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

Get-SPSite -ContentDatabase <DBName> -Limit All | Upgrade-SPSite -VersionUpgrade -QueueOnly

• <DBName> is the name of the content database for which we want to upgrade all site collections
• QueueOnly parameter adds the site collections to the upgrade queue.
  • This allows the timer job to perform parallel upgrades when it is possible and can save time
  • The sites are upgraded in the order in which they are added to the queue
• This cmdlet upgrades all site collections in the specific content database to 2013 mode

Thanks for reading 🙂 f its worth at least reading once, kindly please like and share 🙂 SHARE ING IS CARING 🙂

Share In Teams:

Feel free if you have more questions / suggestions / feedback to add in comment section. If you have any topic which you want cover you are always welcome 🙂

Enjoy the beautiful life 🙂 Have a FUN 🙂 HAVE A SAFE LIFE 🙂 TAKE CARE 🙂

.