Windows Server 2012 (non-R2) Hyper-V Failover Cluster
--four host node servers
--iSCSI cluster shared volumes (NetApp SAN)
--80 hosted VMs
Upgrade the failover cluster to Windows Server 2019.
We're aware of the need to evict one or more nodes to build a "new" cluster with WinSrv2019, then connect the storage and "swing" the VMs over (a procedure no longer needed when upgrading a WinSrv2012-R2 or later cluster).
--Can we perform the old-school "evict & build new" steps to upgrade straight to Windows Server 2019?
--Or, is it advised to first upgrade from 2012 to 2012-R2, then perform rolling upgrades to 2019?
--If we upgrade straight to 2019, are there any known issues or "gotchas" to watch out for due to skipping 2012-R2 and/or 2016?
--Are there any documentation or white papers for upgrading from 2012 (non-R2) failover clustering straight to 2016/2019? (Finding the docs just for 2012-2012R2 are difficult as it is.)
More info available upon request. Thanks in advance for assistance.