Move SharePoint 2016 on prem environment to Windows 2019 and SQL 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-3302573%22%20slang%3D%22en-US%22%3EMove%20SharePoint%202016%20on%20prem%20environment%20to%20Windows%202019%20and%20SQL%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3302573%22%20slang%3D%22en-US%22%3E%3CP%3EQuestion%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20steps%20should%20be%20taken%20to%20move%20our%20current%20environment%3A%20SharePoint%202016%20On-Premise%20on%20Windows%202012%20R2%20with%20SQL%20Server%202012%20on%20Windows%20Server%202012%20R2%20to%20SharePoint%202016%20On%20Premise%20Windows%20Server%202019%20and%20SQL%20Server%202019%20on%20Windows%20Server%202019.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrent%20Environment%3A%3C%2FP%3E%3CP%3ESQL%20Server%202014%20on%20a%20Windows%202012%20server%20(VM)%3C%2FP%3E%3CP%3ESharePoint%202016%20on%20a%20Windows%202012%20server%20(VM)%3C%2FP%3E%3CUL%3E%3CLI%3E1%20App%20Server%3C%2FLI%3E%3CLI%3E1%20Web%20front%20end%20with%20distributed%20cache%20server%3C%2FLI%3E%3CLI%3E1%20search%20server%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlanned%20environment%3A%3C%2FP%3E%3CP%3ESQL%20to%20SQL%20Server%202019%20on%20a%20Windows%202019%20server%26nbsp%3B(VM)%3C%2FP%3E%3CP%3ESharePoint%202016%20to%20a%20Windows%202019%20server.%26nbsp%3B(VM)%3C%2FP%3E%3CUL%3E%3CLI%3E1%20App%20Server%3C%2FLI%3E%3CLI%3E1%20Web%20front%20end%20with%20distributed%20cache%20server%3C%2FLI%3E%3CLI%3E1%20search%20server%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESQL%20Server%20has%20been%20created%20with%20SQL%202019%20installed%20and%20configured.%3C%2FP%3E%3CP%3ESharePoint%202016%20has%20been%20installed%20on%20the%20new%20Windows%202019%20(VM)%20servers%20with%20their%20respective%20roles.%3C%2FP%3E%3CUL%3E%3CLI%3E1%20App%20Server%3C%2FLI%3E%3CLI%3E1%20Web%20front%20end%20with%20distributed%20cache%20server%3C%2FLI%3E%3CLI%3E1%20search%20server%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI%20have%20created%20the%20first%20Web%20Application%20and%20Site%20Collection.%3C%2FP%3E%3CP%3EI%20cannot%20access%20the%20site%20with%20the%20install%20account.%20I%20get%20a%20%E2%80%9CCan%E2%80%99t%20reach%20this%20page%E2%80%99%20message.%3C%2FP%3E%3CP%3EI%20have%20created%20the%20following%20service%20Applications%20(same%20on%20current%20environment)%3A%3C%2FP%3E%3CUL%3E%3CLI%3EApplication%20Discovery%20and%20Load%20Balancer%20Service%20Application%3C%2FLI%3E%3CLI%3EManaged%20Metadata%20Service%20Application%3C%2FLI%3E%3CLI%3ESearch%20Administration%20Web%20Service%20for%20Search%20Service%20Application%3C%2FLI%3E%3CLI%3ESearch%20Service%20Application%3C%2FLI%3E%3CLI%3ESecure%20Store%20Service%3C%2FLI%3E%3CLI%3EState%20Service%20Application%3C%2FLI%3E%3CLI%3EUser%20Profile%20Service%20Application%3C%2FLI%3E%3CLI%3EWSS_UsageApplication%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20not%20sure%20what%20steps%20I%20should%20take%20next.%3C%2FP%3E%3CP%3EShould%20I%20wipe%20everything%20out%20and%20start%20over%20with%20just%20the%20basic%20install%20(no%20configuration)%20of%20the%20three%20servers.%20Add%20them%20to%20the%20existing%20farm%2C%20then%20migrate%20the%20databases%20to%20the%20new%20platform%20before%20reconnecting%20the%20SP%20environment%20to%20the%20upgraded%20database%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20need%20to%20have%20both%20the%20new%20environment%20and%20old%20environment%20online%20at%20the%20same%20time%20due%20to%20ongoing%20project%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20looking%20for%20suggestion%20on%20how%20to%20proceed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3302573%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3347134%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20SharePoint%202016%20on%20prem%20environment%20to%20Windows%202019%20and%20SQL%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3347134%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1380982%22%20target%3D%22_blank%22%3E%40Jupiter82%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3EHave%20you%20named%20the%20site%20url%20in%20the%20new%20(win2019)%20environment%20same%20as%20the%20existing%20one%20(win2012r2)%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20are%20trying%20to%20reach%20the%20SharePoint%20site%20locally%20in%20the%20server%20you%20need%201st%20to%20add%20an%20entry%20into%20the%20hostfile%2C%202nd%26nbsp%3B%26nbsp%3BDisable%20Loopback%20Check%20via%20PowerShell%20and%203rd%20%3CEM%3E(optional)%20%3C%2FEM%3Econfigure%20the%20SSL%20certificate%20in%20IIS%20if%20your%20site%20is%20running%20in%20HTTPS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20should%20help%20you%20accessing%20the%20site%20in%20the%20new%20platform%20(win2019).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConcerning%20the%20migration%20approach%2C%20what%20you%20are%20trying%20to%20do%20is%20technically%20possible%20because%20you%20are%20still%20using%20the%20same%20SharePoint%20version%2C%20only%20upgrading%20to%20a%20new%20OS%2C%20%3CU%3E%3CSTRONG%3EHOWEVER%3C%2FSTRONG%3E%3C%2FU%3E%26nbsp%3BI%20don't%20recommend%20the%20approach%20because%20it's%20too%20risky%2C%20in%20my%20opinion%2C%20and%20if%20something%20goes%20wrong%20you%20will%20generate%20an%20outage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20better%20approach%20is%20to%20build%20a%20parallel%20SP%20platform%20%3CEM%3E(as%20you%20are%20doing%20right%20now)%3C%2FEM%3E.%3C%2FP%3E%3CP%3EApply%20all%20the%20settings%20and%20customization%20and%20migrate%20finally%20the%20Content%20Databases%20from%20an%20instance%20to%20another.%3C%2FP%3E%3CP%3EIF%20you%20need%20to%20access%20both%20platform%20at%20the%20same%20time%2C%20you%20need%20to%20create%20the%20web%20applications%20and%20urls%20same%20as%20the%20existing%20%3CSTRONG%3EAND%3C%2FSTRONG%3E%20%3CEM%3E%3CU%3Etemporary%3C%2FU%3E%3C%2FEM%3E%20extend%20on%20the%20new%20platform%20the%20web%20applications%20with%20a%20unique%20name.%3C%2FP%3E%3CP%3EThis%20will%20allow%20you%20to%20keep%20browsing%20both%20sites%20at%20the%20same%20time%20(eg.%20xyz.contoso.com%20-%20win2012r2%20%2F%20xyz-2019.contoso.com%20-%20win2019).%20Once%20you%20have%20validated%20that%20everything%20works%20fine%2C%20before%20the%20final%20cut%20over%2C%20you%20can%20simply%20delete%20the%20extension%20and%20keep%20the%20original%20url%20as%20default%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3348126%22%20slang%3D%22en-US%22%3ERe%3A%20Move%20SharePoint%202016%20on%20prem%20environment%20to%20Windows%202019%20and%20SQL%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3348126%22%20slang%3D%22en-US%22%3Eyeah%20as%20above%2C%20pretty%20straight%20forward%20operation.%3CBR%20%2F%3E1.%20Configure%20new%20farm%20exactly%20the%20same%20as%20the%20existing%3CBR%20%2F%3E-%20Install%20SharePoint%3CBR%20%2F%3E-%20Configure%20Services%20using%20same%20service%20accounts%20setup%3CBR%20%2F%3E-%20Configure%20Web%20Applications%20the%20same%20(Service%20Accounts%2C%20DNS%2C%20Hostnames%20e.t.c)%3CBR%20%2F%3E-%20Install%20any%20solutions%3CBR%20%2F%3E-%20set%20old%20farm%20to%20read-only%2C%20backup%20and%20restore%20all%20(content%20and%20service%2C%20not%20all%20required%20google%20which%20ones%20are)%20databases%20to%20new%20sql%20(overwriting%20existing%20is%20they%20existing%20in%20testing%2Fsetup)%3CBR%20%2F%3E-%20Change%20DNS%20entries%20to%20point%20to%20new%20server%3CBR%20%2F%3E-%20Decomissions%20old%20servers%3C%2FLINGO-BODY%3E
Occasional Visitor

Question:

 

What steps should be taken to move our current environment: SharePoint 2016 On-Premise on Windows 2012 R2 with SQL Server 2012 on Windows Server 2012 R2 to SharePoint 2016 On Premise Windows Server 2019 and SQL Server 2019 on Windows Server 2019.

 

Current Environment:

SQL Server 2014 on a Windows 2012 server (VM)

SharePoint 2016 on a Windows 2012 server (VM)

  • 1 App Server
  • 1 Web front end with distributed cache server
  • 1 search server

 

Planned environment:

SQL to SQL Server 2019 on a Windows 2019 server (VM)

SharePoint 2016 to a Windows 2019 server. (VM)

  • 1 App Server
  • 1 Web front end with distributed cache server
  • 1 search server

 

SQL Server has been created with SQL 2019 installed and configured.

SharePoint 2016 has been installed on the new Windows 2019 (VM) servers with their respective roles.

  • 1 App Server
  • 1 Web front end with distributed cache server
  • 1 search server

I have created the first Web Application and Site Collection.

I cannot access the site with the install account. I get a “Can’t reach this page’ message.

I have created the following service Applications (same on current environment):

  • Application Discovery and Load Balancer Service Application
  • Managed Metadata Service Application
  • Search Administration Web Service for Search Service Application
  • Search Service Application
  • Secure Store Service
  • State Service Application
  • User Profile Service Application
  • WSS_UsageApplication

 

I am not sure what steps I should take next.

Should I wipe everything out and start over with just the basic install (no configuration) of the three servers. Add them to the existing farm, then migrate the databases to the new platform before reconnecting the SP environment to the upgraded database?

 

We need to have both the new environment and old environment online at the same time due to ongoing project work.

 

I am looking for suggestion on how to proceed.

 

Thank you.

2 Replies

Hi @Jupiter82 ,

Have you named the site url in the new (win2019) environment same as the existing one (win2012r2) ?

 

If you are trying to reach the SharePoint site locally in the server you need 1st to add an entry into the hostfile, 2nd  Disable Loopback Check via PowerShell and 3rd (optional) configure the SSL certificate in IIS if your site is running in HTTPS.

 

This should help you accessing the site in the new platform (win2019).

 

Concerning the migration approach, what you are trying to do is technically possible because you are still using the same SharePoint version, only upgrading to a new OS, HOWEVER I don't recommend the approach because it's too risky, in my opinion, and if something goes wrong you will generate an outage.

 

A better approach is to build a parallel SP platform (as you are doing right now).

Apply all the settings and customization and migrate finally the Content Databases from an instance to another.

IF you need to access both platform at the same time, you need to create the web applications and urls same as the existing AND temporary extend on the new platform the web applications with a unique name.

This will allow you to keep browsing both sites at the same time (eg. xyz.contoso.com - win2012r2 / xyz-2019.contoso.com - win2019). Once you have validated that everything works fine, before the final cut over, you can simply delete the extension and keep the original url as default   

 

 

 

 

yeah as above, pretty straight forward operation.
1. Configure new farm exactly the same as the existing
- Install SharePoint
- Configure Services using same service accounts setup
- Configure Web Applications the same (Service Accounts, DNS, Hostnames e.t.c)
- Install any solutions
- set old farm to read-only, backup and restore all (content and service, not all required google which ones are) databases to new sql (overwriting existing is they existing in testing/setup)
- Change DNS entries to point to new server
- Decomissions old servers