1. Test and mount the content database to a different web application. This is often the case if you have multiple web applications in the source farm, each with a root site collection.
2. Rename the site collection in the source farm so that the URL doesn't conflict, and both can coexist in the new SharePoint farm.
3. Delete one of the site collections from the source farm before attempting a database attach upgrade to the new SharePoint farm.  This can often be accomplished using Remove-SPSite. However, what do you do if the site to be deleted is also orphaned in the source farm and Remove-SPSite fails?

Deleting Orphaned Site Collections

For more information on resolving other Test-SPContentDatabase findings please see:

The Test

• Individual Users are in the format: i:0#.w|<Domain\UserName>
• Groups are in the format c:0+.w|<GROUP SID>

Resolution

For more information on resolving other Test-SPContentDatabase findings please see:

Resources

1. SQL Mirroring is deprecated and not recommended.
2. When Workflow Manager is a component of SharePoint Server 2016 or SharePoint Server 2013, it will be supported according to the end of support dates of the respective SharePoint Server version.
3. Extended support for Workflow Manager ends on 7/14/2026 when used with a SharePoint 2016 farm. However, extended support for Windows Server 2012R2, the maximum Windows version for Workflow Manager CU3, ends on 10/10/2013

Resources

What is a Server Side Dependency?

Identifying Server Side Dependencies

SharePoint Health Analyzer

Test-SPContentDatabase

1. Missing Setup Files - Resource files
2. Missing Assembly - Missing event receivers
3. Missing Features - Feature definitions
4. Missing Web Parts - .webpart files
5. Database Authentication Mode (Classic or Claims)

Removing Missing Server Side Dependency References

Features

Setup File

Web Part

With this information you have two options for remove this webpart from the page

1. Navigate directly to the web part maintenance page by appending ?contents=1 to the URL. In this case you would navigate to: https://sharepoint.contoso.com/sites/lab5-4/SitePages/Home.aspx?contents=1
2. Remove the webpart using PowerShell

Event Receiver

For more information on resolving other Test-SPContentDatabase findings please see:

Understanding the Usage Reports

Accessing the Office365 Usage and Activity reports using Windows PowerShell

Step 1: Register an App in AzureAD to access the Usage Reports

Step 2: Use Get-Office365Report.ps1 to access the Graph API and download your report

Resources

SharePoint Online Management Shell

1. Download sharepointonlinemanagementshell_6112-1200_x64_en-us.msi
2. Run the installer
3. Once installed you can load this module into your scripts using:

Office Dev PnP PowerShell Module

SharePoint Online Client Side Object Model (CSOM)

1. Download the NuGet Commandline:
2. From the directory where you saved nuget.exe:

Azure Azure AD Management Shell

1. Download AdministrationConfig-V1.1.166.0-GA.msi
2. Run the installer file
3. Import the module in your script by running:

Security and Compliance Center

SQL Version Support

SQL High Availability Feature Support

Resources

1. Ensure SharePoint web application pools are running under a service account (any production SharePoint farm should already be configured this way)
2. Configure SharePoint for Kerberos authentication
3. Create SPNs and configure Kerberos Constrained Delegation (KCD)
4. Publish SharePoint through Azure AD App Proxy
5. Configure AAMs in SharePoint for the external URL
6. Assign users to the Azure AD App Proxy

1. A SharePoint 2016 farm using host header site collections
2. Office Online Server
3. Using the same URL internally and externally for SharePoint

Host Named Site Collections

Get-SPSite | FT URL, HostHeaderIsSiteName -AutoSize

Get-SPSite | ?{$_.url -like "https://sharepoint.xxxxxxxxxxxxxxx.co*"} | Get-SPSiteURL | FT -AutoSize

Office Online Server (OOS)

<form target="WebApplicationFrame" action="https://officeonline.xxxxxxxxxxxxxxx.co/wv/wordviewerframe.aspx?ui=en%2DUS&rs=en%2DUS&WOPISrc=https%3A%2F%2Fsharepoint%2Exxxxxxxxxxxxxxx%2Eco%2Fsites%2FTeamSite1%2F%5Fvti%5Fbin%2Fwopi%2Eashx%2Ffiles%2Fb40646494c8c48d9a31d4156918f2a07&wdEnableRoaming=1" id="canvas_form" method="post">

1. OOS can be configured with both an internal and external URL
2. SharePoint can only be bound to one URL for OOS. I cannot set a different OOS URL for default and extranet zones.
3. SharePoint users do not authenticate to OOS using Windows integrated authentication. Instead an authorization token is included in the request to the OOS server. This means that we do not need to configure Kerberos Constrained Delegation (KCD) when publishing OOS

Note: Since passthrough authentication is being used, it is important to lock down host domains for which Office Online Server will allow file operations.This will prevent a SharePoint farm, or other servers, from unauthorized domains from binding to this farm.

Publish a Friendly URL for SharePoint

Next Steps

Additional Resources

Supportability for SharePoint

Uses for redirect

1. Redirecting the user from http to https to enforce SSL communication. When a SharePoint farm is load balanced this is typically done using the load balancer but it some cases can be done on the SharePoint server or another server running IIS by using the IIS URL Rewrite module
2. Redirecting a user who has a stale URL, typically when the name is changed during a farm migration or upgrade. This can also be done using a load balancer or any IIS server by implementing the URL Rewrite module.

Step by Step Instructions for HTTP to HTTPS redirect

#1 Download the URL Rewrite tool by following the instructions here

#2 Ensure that the IIS site you are using is configured for the proper port 80 binding. In this case we are listening for all traffic on port 80. But you could restrict this based on host header as needed

#3 Create a new URL rewrite rule

#4 Configure Rule Settings Exactly as follows

#5 Apply the rule

#6 From the top node disable and enable the rule (alternatively perform IISReset)

Note: web.config file modifications

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

<rewrite>
	<rules>
		<rule name="Redirect to http" enabled="true" patternSyntax="Wildcard" stopProcessing="true">
			<match url="*" negate="false" />
			<conditions logicalGrouping="MatchAny">
				<add input="{HTTPS}" pattern="off" />
			</conditions>
			<action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Found" />
		</rule>
	</rules>
</rewrite>

Additional Resources