'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Properly Move a SharePoint 2016 Farm to New Servers
Question details
The user needs to resolve an issue where a copied SharePoint 2016 farm retains old server references in configuration tools, preventing proper management.
- Product
- SharePoint Server 2016
- Device & OS
- not provided
- Scenario
- Migrating an existing on-premises SharePoint 2016 farm to new hardware or virtual servers.
- Observed behavior
- After copying the servers, sites and databases are visible, but Central Administration, SharePoint Management Shell, and the Products Configuration Wizard still reference the old server names.
Ensure you have full farm administrator privileges and have performed comprehensive SQL database backups before attempting any farm migration. Never rely on simply cloning or copying servers, as SharePoint configuration databases tightly bind to original server names.
Perform a Supported Database-Attach Migration
A SharePoint Server farm cannot be successfully moved by simply copying or cloning servers. The officially supported approach is building a new farm and attaching the existing databases.
Cloning SharePoint servers results in the Configuration Database retaining the old server names, which breaks Central Administration, PowerShell tools, and the Configuration Wizard. To correctly move a farm, you must provision a new SharePoint 2016 farm from scratch and migrate the content using the database-attach method.
Install SharePoint Server 2016 on your new servers and configure a brand-new farm topology using the SharePoint Products Configuration Wizard.
Back up the content databases and service application databases from the old SQL Server, then restore them to the new SQL Server instance that your new farm uses.
Create new web applications in the newly configured farm and use the Mount-SPContentDatabase PowerShell cmdlet to attach your restored content databases, effectively bringing your sites online with the correct server names.
Use PowerShell to Rename SharePoint Servers
If a server's hostname was changed after a clone, SharePoint must be explicitly informed of the new name via PowerShell to update the configuration database.
Need a Lightweight Office Solution? Try WPS Office
While managing heavy on-premises Microsoft SharePoint architectures, you may need a fast, reliable, and cost-effective office suite for your daily document needs. WPS Office is a highly compatible, free alternative to Microsoft Office that handles your essential productivity tasks seamlessly.
- 1. Download the software: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Run the installer: Open the downloaded setup file and follow the quick, straightforward installation wizard.
- 3. Enjoy seamless compatibility: Open your existing Microsoft Office documents in WPS Office and continue working without losing any formatting.
Frequently Asked Questions
Why does my cloned SharePoint server still show the old name?
SharePoint stores its topology and server names directly in its central SQL configuration database. Simply cloning a VM or copying a server's files does not update these database records, causing Central Administration and other tools to permanently reference the old names.
Can I migrate a SharePoint 2016 farm without rebuilding it?
No, it is not officially supported to simply copy or move a farm entirely as a clone. The Microsoft-recommended approach is building a new farm from scratch and migrating the content using the database-attach method.
Where can I get official support for on-premises SharePoint migrations?
Because on-premises migrations involve complex database and topology configurations, you should post your specific scenario in the Microsoft Q&A forums under the 'SharePoint Server' tag, where specialists can advise on supported migration and database-attachment procedures.
