Support Server 2012 R2 Hyper-V in VMM 2019
I know System requirements for System Center Virtual Machine Manager (https://docs.microsoft.com/en-us/system-center/vmm/system-requirements?view=sc-vmm-2019) does not list Server 2012 R2 Hyper-V as being a supported Hyper-V host in a VMM 2019 environment. And there's a difference between "not officially supported" and "officially not supported". VMM 2019 simply does not allow you to install its agent on a Server 2012 R2 Hyper-V server:
The verslon of the Windows operating system on the computer xxxxx is not supported for a host.
Upgrade the operating system to Windows Server 2016 or a later supported version, and then try the operation again.
So if you're planning to upgrade from a Hyper-V 2012 R2 environment to Server 2019: you can't do it using VMM. We're adapting our plans using an intermediate 2016-environment, but that's not easy.
Funny thing: ESXi 5.1, which is even older than Hyper-V 2012 R2 IS supported... So please, Microsoft: support your own stuff if you want your customers to remain loyal and make it possible to migrate from a Server 2012 R2 Hyper-V environment to a Server 2019 Hyper-V environment using VMM.
Support for Windows Server 2012 R2 hosts added in VMM 2019 UR2.
Michael L commented
With CU2 Hyper-V on Server 2012R2 are supportet!
any idea on when VMM 2019 will support 2012 R2 hosts?
Michael L commented
what do you think about when can we expect to include the 2012R2 Hyper-V hosts in the 2019 VMM? Even if you can't give an exact time, feedback would be very important.
When can we expect the support for Windows Server 2012R2? We are want to migrate now our servers from Windows Server 2012R2 to Server 2019 using SCVMM.
Hi All, We are planning to extend support to Windows Server 2012R2 for management as hosts in VMM 2019. Would like to understand if this support needs to e extended for WS 2012R2 library server, SOFS, PXE and Update servers. Please fill in this very focused survey for us to understand the requirement.
I suspect the reason it is isn't supported is because Hyper-V 2019 needs Network Controller, which doesn't work on 2012R2, whereas VMWare is more like a guest, so it doesn't participate in the Logical/Virtual network the same way.
We have 66 2012 R2 Hyper-V Hosts and we startup to replace these servers to a Hyper-V 2019. We are in problems in how can we do this task without support of 2012 R2 and 2019 in the same version of SCVMM (2016 - actualy installed don't support hyper-v 2019, and vmm 2019 don't support 2012 R2). It is so sad...
Response from Microsoft via Unified Support ticket pasted below...
I understand your requirement and I would like to state that operating system Windows 2012 R2 is out of mainstream support, Hence there are no plans in bringing back support for it in SCVMM 2019.
I would however reach out to the product group in order to check if there are any plans to support windows 2019 in SCVMM 2016.
Please add 2012 R2 support and include SOFS (Windows Server 2012 R2)
Any updates on this, or SCVMM 2016 support of hyper v hosts running Server 2019?
Please add support for this ASAP, This is still a supported OS by MS.
Please implement support.you would think as 2012 R2 is still a supported OS till Oct'2023 that newer versions of SCVMM would support it as a Hyper-V host.We are now in the same boat of an intermediate 2016 environment or deploying a separate environment all together so as to migrate through attrition.