Seeking feedback regarding a Windows Server in-place upgrade. My MICC server is currently running on a Windows Server 2012R2 OS and with SQL 2014.
Has anyone in this forum attempted an in-place upgrade from Windows Server 2012R2 to 2016 Std? If so, were there any issues with any of the MICC applications? The 2016 OS is listed as supported, just wondering how the application handles an in-place upgrade as opposed to being installed on it.
I've been able to test this with limitations (an isolated vm - no connection to MCD or other components). The Mitel services do start, however I am not able to fully test. In this test, I experience messages regarding the MICC RedistPacker (errors). However, not sure if this is due to the vm being isolated.
Upon successful OS upgrade, my next step would be to upgrade SQL to 2016. Which I have yet to test.
