Forum Discussion
Hyper-V Server 2022
Free 'Microsoft Hyper-V Server' product update
Since its introduction over a decade ago in Windows Server 2008, Hyper-V technology has been, and continues to be, the foundation of Microsoft’s hypervisor platform. Hyper-V is a strategic technology for Microsoft. Microsoft continues to invest heavily in Hyper-V for a variety of scenarios such as virtualization, security, containers, gaming, and more. Hyper-V is used in Azure, Azure Local, Windows Server, Windows Client, and Xbox among others.
Starting with Microsoft Hyper-V Server 2019, the free ‘Microsoft Hyper-V Server’ product has been deprecated and is the final version of that product. Hyper-V Server 2019 is a free product available for download from the Microsoft Evaluation Center: https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2019
Microsoft Hyper-V Server 2019 will continue to be supported under its lifecycle policy until January 2029, see this link for additional information: https://docs.microsoft.com/en-us/lifecycle/products/hyperv-server-2019.
While Microsoft has made a business decision to no longer offer the free 'Microsoft Hyper-V Server' product, this has no impact to the many other products which include the Hyper-V feature and capabilities. This change has no impact to any customers who use Windows Server or Azure Local.
For customers looking to do test or evaluation of the Hyper-V feature, Azure Local includes a 60-day free trial and can be downloaded here: https://learn.microsoft.com/en-us/azure/azure-local/ . Windows Server offers a free 180-day evaluation which can be downloaded from the Evaluation Center here: https://www.microsoft.com/en-us/evalcenter
Microsoft remains committed to meeting customers where they are and delivering innovation for on-premises virtualization and bringing unique hybrid capabilities like no other can combined with the power of Azure Arc. We are announcing that Microsoft Hyper-V Server 2019 was the last version of the free download product and that customers begin transitioning to one of the several other products which include Hyper-V or consider Azure.
Thank you,
Elden Christensen
Principal Group PM Manager
Windows Server Development Team
When you speak of "reassigning" a license, is anything required to be "physically" done? Or do we just effectively say "right, this Server 2022 license is now assigned to these VMs rather than these", and then run them for 90 days, at which point we could fail back. In other words, how does formally assign a license?
The hyperV replication not need any licence migration...
You can't start the two mahines at the same time with same copy of OS (aka licence in US, that not exist in France).
It's the same ID, the same system.
A replication is basicaly a save/backup, as a clone.
You can have 10 systems on the first machine, 10 replications on the second, and moving "for all time" 5 machines on the second hypervisor, with not end delay, because you want split performances, and accept a degraded mode when issue comming on 1 hypervisor for exemple.
Just respect "it's the same machine, so I can't run 2 on the same time with the same licence".
Any people in Microsoft blames you if you start for a short time the two mahine, after any crash (in the case where you have launch the replication for continu work after bug of the main system), to migrate some data for any reasons.
But "short moment" is not 10 years...
It's like 1 or 2 weeks maybe, where the initial machine is not use as service (or 2nd)... 1 day in fact in real situation where we xan imagine this scenario.
Or for time to re-migrate at starting point.
- Hi Chris,
We only ever use replications in the case of a primary server hardware failure. If the general terms for the product license apply, then we should be fine. Having said that, I think looking into SA would be a good move.
Thanks. Hi SpenceFoxtrot,
I'm not sure the Microsoft product terms allow you to do what you're describing, but at the end of the day that's between you and any Microsoft auditors.
The only thing I'd suggest you might consider is that Disaster Recovery Rights under Software Assurance exist for a reason.
Kind regards,
Chris
