New On Prem Server Upgrade WinServer 2008 R2 to WinServer 2016

[Sean_Kane]

Hi Everyone,
I am currently investigating the first physical server migration that I have ever done with AW. We are presently running AW 9.3.0.10 (Console and Device server) on an On-Premise Windows Server 2008 R2 server. SQL DB on SQL 2016. I need to get rid of Server 2008 and plan on going with a 2016 server.
My thought at this time: upgrade current (2008) On Prem Server to WorkSpaceOne 9.6. AFter that is complete, setup brand new Server 2016 Windows On Prem server, follow the WorkspaceOne UEM Installation Guide and setup a new copy of WorkspaceOne on the 2016 Server.
What I can't figure out is, do I point the DB server to the existing DB during the initial installation on the new Windows On Prem server? Or, do I install it to a ' dummy DB'  and then just redirect it to the existing production DB after the installation is complete?

Thanks in advance,
Sean

[Stansfield]

Also the guide does not say it but be sure to get rid of your old database once you migrate.  The old database can interact with the devices (especially sending emails) even if it is not connected to the server anymore.  It would still be wise to just deactivate all jobs and the database for a bit before you get rid of it though.

[Erdi1]

Hello and sorry for bringing up this old thread.

We have on-premise environment 20.5.0.52. Our Console and Device Services run on one Windows Server. We also have one Endpoint and one Relay server with the VMWare Tunnel Proxy.

We want to upgrade the console to 2203 but our servers are all Windows Server 2012. The setup needs at least Windows Server 2012 R2.

Has anyone performed an in-place-upgrade from 2012 to 2012 R2? Is it safe or does is destroy the WS1 installation?

Thanks and regards,

Erdi