**edit** we're on 2018 R2 already, so we don't need to upgrade our PureConnect version in our process. You'll need to look at release notes to see what version Server 2016 was officially supported in first
I'm working on this currently, as well. Our process is basically to provision new VMs and reinstall the applications, then schedule change windows to rename/re-ip to replace the existing servers. Windows servers naturally bloat, and this helps combat it a little.
You can look at tools like interaction migrator for backing up your CICs configuration, but you can use switchover to effectively just add a new backup server to an existing primary (and visa versa) to pull the configuration over.
With our physical servers (media servers) we would just take one out of service at a time and have it wiped and reinstalled with 2016R2 and reinstall the applications.
All of this said, if you aren't familiar with setting up an environment from scratch, I'd strongly consider talking to support at the least and possibly consider getting 3rd party assistance. The process isn't all that tricky but little things can cause problems that are really hard to pin down and depending on how your value your time, it could be worth it.
------------------------------
Aaron Lael
State of Utah
------------------------------
Original Message:
Sent: 02-13-2019 08:03
From: Romain Romain JOURDY
Subject: OS Upgrade 2008 to 2016 for CIC 2016R4
Dear all,
Could you tell me what are steps to upgrade CIC 2016R4 to 2018R4.
As seen in documentation, we need to upgrade Server OS from W2008R2 to W2016.
Could you explain how and when upgrade the OS in the migration process?
Many thanks in advance,
Romain
#ArchitectureandDesign
------------------------------
Romain JOURDY
Dimension Data France
------------------------------