Hi all,
we are running SEPM 14 RU1 in a Windows 2008 R2 server, with a remote database in a SQL Server 2016. Our plan is to 'refresh' the OS of the SEPM server to Windows Server 2012 or 2016, installing the same SEPM version on it. Since they are virtual machines, I think my wintel colleagues will create a new instance of Windows Server 2016 with a different hostname and different IP for the new SEPM to be installed on it, and when the migration is completed, the old one will be decommissioned.
I found this article: https://www.symantec.com/connect/articles/how-move-sepm-one-server-another-server , the point 3.2 looks suitable for our case, but it deals with embedded database, not a remote database. How to proceed in our case? Is there any specific actions or measures having into account the remote database?. I do not know if using the recovery file, I still need to provide some database information during the installation process.
Cheers!