Hey Sean
How did the upgrade go? Any tips you could share with us? Also, did your upgrade just involve Console and Device services or auxiliary components as well? (SEG, MAG, Content)?
We are planning to upgrade from 2012 to 2016 servers as well on an on-prem setup with Device, AWCM, SEG, Content Gateway (relay) and MAG (relay) on one and Console, ACC, Content Gateway (endpoint) and MAG (endpoint) on the other. I understand there are two approaches to this:
1. Set up High Availability as Thomas recommends, set up the new 2016 server and disable the old one when the new is confirmed to be working as expected and
2. Stop services on the old server, set up the new 2016 server and then change the DNS to point to the new server
Anyone tried either and what are the pros and cons? Doing some research it appears that it is just a matter of installing the services on the new server which is simple but are there any specifics for the auxiliary services (MAG, SEG, Content)?
Thanks