Skip to main content
  • EN

Microsoft dropped a surprise on us today by releasing Windows Server 2022 to no fanfare at all. It’s been released today 18th August 2021, it will have mainstream support until the 13th October 2026 and will be considered end of life on the 14th October 2031 (how are we talking about the 2030’s already?!). This is evidenced in Microsoft’s updated Windows Server Release Information document.

If you’re looking to grab an evaluation copy of Windows Server 2022 you can do so here. Alternatively if you have a suitable agreement with Microsoft you can also download a copy from VLSC or MSDN.

Interested to learn what’s new in Windows Server 2022? You can check out Microsoft’s post on the subject here. IMPORTANT: Microsoft are making TPM 2.0 support mandatory, if you’re looking to install onto existing hardware, be sure you meet the hardware requirements.

 

Supported Platforms

 

Realistically it’s going to be premature to start migrating your entire environment to Windows Server 2022, but in the interest of helping you work out where your support status is, consider the following.

 

VMware ESXi:

 

VMware have “Tech Preview” status for Windows Server 2022 at present, meaning that as Microsoft have only just made Windows Server 2022 “Generally Available” (GA), there may be some blocking issues that need resolving by Microsoft or VMware may be required to release a patch to support this operating system (OS). You can track the status of VMware’s support for this OS via this link.

Note: The following information is subject to change. At present it appears VMware are targeting support for ESXi 6.7U2 and above as the minimum requirement to run Windows Server 2022.

 

Microsoft Hyper-V:

 

Microsoft haven’t yet updated their documentation to reflect the minimum requirements, at present their Microsoft Docs article only lists virtual machines supported for Windows Server 2019 and below as well as Windows 10 and below. It is a reasonable assumption you will be able to virtualise Windows Server 2022 on Hyper-V 2022 however we won’t know about backwards compatibility until Microsoft update the article.

Bare Metal/Physical Installation:

 

At present none of the major hardware manufacturers I’ve checked have released any lists detailing which platforms will support Windows Server 2022, I’ll aim to update this blog post as information becomes available. If you want to see if your system will run Windows Server 2022 with or without vendor support, see my link to the hardware requirements above.

 

Veeam:

 

Veeam generally aim to release support for new operating systems within 90 days of release, normally within their next patch after the OS has been released (depending on the time difference between them). Veeam currently offer no support for Windows Server 2022 but as per their KB article KB4126, they will no longer blanket refuse to install on these systems. Veeam Backup & Replication v11a is scheduled to be the first release that will support Windows Server 2022, this is scheduled for Q3 of 2021 as per the notes on KB4180. Veeam Agent for Microsoft Windows 5.0.1 is expected to be released alongside Veeam Backup & Replication v11a and will also add support for Windows Server 2022.

Update 23/08/2021: Anton Gostev has provided an more precise indication of Veeam Backup & Replication v11a availability. Within the latest newsletter sent on the 23rd August 2021 Anton Gostev highlighted the integration of Veeam Backup for Google Cloud Platform v2 requires Veeam B&R v11a to be installed and would be available next month, later in the newsletter Anton Gostev reconfirmed one of the main improvements of the v11a release is support for Windows Server 2022.

Update 24/08/2021: Microsoft have confirmed Windows Server 2022 will only support SQL Server 2017 upwards. Veeam v11a will include support for Windows Server 2022, but at present I don’t have information to confirm if this is just processing Windows Server 2022 as a VM/Agent or including support for Veeam components such as the main VBR server itself. This could add a complication as Veeam installs with SQL Server 2016 express by default, but this version of SQL Server isn’t supported on Windows Server 2022 (see the SQL Server section for more information).

Conclusion:

 

It’s great to see Microsoft still releasing full longer term support systems instead of forcing everyone onto a semi-annual channel. I’ll update this blog post as new information becomes available and as compatibility with any key applications becomes available.

 

Update 21/08/2021:

SharePoint: Microsoft’s GitHub pull requests shows that SharePoint Server 2019 supports Windows Server 2022, but they’re saving this being merged into the live documentation until the 1st September 2021.

SQL Server:

Update 24/08/2021: I reached out to various teams at Microsoft Docs to request updates to the documentation, seeking clarification regarding Windows Server 2022 support. The Microsoft SQL Server team responded today to inform me that they will only be supporting the SQL Server editions still in active support. These are SQL Server 2017, 2019 and the soon to be released SQL Server 2022.

 

Dell: Dell haven’t released a list of supported hardware for Windows Server 2022 yet. However their 15th generation servers are starting to show driver support, indicating these will be supported running Windows Server 2022. At present this shouldn’t be interpreted as full support. Dell have changed the default offerings for their servers in January 2021 to include TPM 2.0 which is a mandatory requirement for Windows Server 2022. As a result of the Dell 15th generation PowerEdge servers being released after this date, these servers should support Windows Server 2022 unless the TPM 2.0 device has been deliberately removed from the configuration. Should the 14th generation servers be supported too, they may require the addition of a TPM 2.0 module if this wasn’t included with the server, though at present Dell are showing no drivers for Windows Server 2022 on 14th generation.

 

I think it is fair to say that Veeam Backup & Replication v11a (due in September of this year) will provide full Windows Server 2022 support:

-Backup as a VM (all hypervisors)

-Be on a backup proxy (Hyper-V)

-Installed upon (B&R on WS2022)

-Veeam Components installed on WS2022

That’s the MO here when it comes to platform support. That being said, it is not final till it is generally available. This was mentioned in the R&D Forum Digest this week (WS2022 support) by El G himself. I hope this helps @MicoolPaul  and @Chris.Childerhose 

Thanks for the further clarification @Rick Vanover 😁

I think it is fair to say that Veeam Backup & Replication v11a (due in September of this year) will provide full Windows Server 2022 support:

-Backup as a VM (all hypervisors)

-Be on a backup proxy (Hyper-V)

-Installed upon (B&R on WS2022)

-Veeam Components installed on WS2022

That’s the MO here when it comes to platform support. That being said, it is not final till it is generally available. This was mentioned in the R&D Forum Digest this week (WS2022 support) by El G himself. I hope this helps @MicoolPaul  and @Chris.Childerhose 

Perfect, thanks for confirming that’s the intended plan :relaxed:

There are rumors that the free Hyper-V service will be removed in Windows Server 2022.

Sad, this was a simple testing environment for virtual systems in several windows server versions.

Yup saw that in the R&D Forums Gosteagram this morning. Do I hear KVM :)

I was surprised to this news of Hyper-V Server not continuing as a free hypervisor. 

This was, in my professional opinion, the best free hypervisor option in the market.  A game changer for ROBO/Edge, retail locations, small businesses and more. 

There are rumors that the free Hyper-V service will be removed in Windows Server 2022.

Sad, this was a simple testing environment for virtual systems in several windows server versions.

Guess I will be keeping Win2019 in the lab then to use Hyper-V for testing and VMCE/A study.  :stuck_out_tongue_winking_eye:

I’ve heard these rumours too. Apparently Hyper-V role will continue in Windows Server 2022 but Hyper-V is going to be giving way to Azure Stack!

 

Seems only fitting from the company that will make Exhange/SharePoint/Skype for Business 2022 all subscription only for their on-premises offerings…

 

Ready or not, here comes cloud! 😉

Well it’s microsoft.com not microsoft.org

Well it’s microsoft.com not microsoft.org

I thought .com was for Veeam.COMmunity?

TBF I say the same about Veeam Community Edition limits… We’re Veeam.com not Veeam.org

When @Gostev had not mention it in his digest, I would have missed that Microsoft does not offer a free Hyper-V with 2022 any more.

When @Gostev had not mention it in his digest, I would have missed that Microsoft does not offer a free Hyper-V with 2022 any more.

When @Gostev had not mention it in his digest, I would have missed that Microsoft does not offer a free Hyper-V with 2022 any more.

I can tell you this, vNote42 having worked with Anton for almost 11 years….  * * * NOTHING * * *  gets by Gostev. Ever.

When @Gostev had not mention it in his digest, I would have missed that Microsoft does not offer a free Hyper-V with 2022 any more.

I can tell you this, vNote42 having worked with Anton for almost 11 years….  * * * NOTHING * * *  gets by Gostev. Ever.

:joy:

Wikigostev

When @Gostev had not mention it in his digest, I would have missed that Microsoft does not offer a free Hyper-V with 2022 any more.

I can tell you this, vNote42 having worked with Anton for almost 11 years….  * * * NOTHING * * *  gets by Gostev. Ever.

Definitely seems that way. :joy:

When @Gostev had not mention it in his digest, I would have missed that Microsoft does not offer a free Hyper-V with 2022 any more.

I can tell you this, vNote42 having worked with Anton for almost 11 years….  * * * NOTHING * * *  gets by Gostev. Ever.


🤣🤣🤣 that can be exhausting….

See Anton Gostev’s comment to Windows Server 2022 and ReFS Repositories:

“ While it goes without saying that you should not update your ReFS backup repositories to Windows Server 2022 before we deliver its official support with version 11a, there are always people who feel adventurous or just like to experiment. If you're one of those, please do stick to clean Windows Server 2022 installs for now, as there's the confirmed regression in the ReFS format upgrade code path which may leave your backup repository in the BSOD boot loop.”

Keep also in mind, when upgrading ReFS, next synthetic full will not be fast-cloned but “legacy” fulls. Learned this not long ago. We re-installed Repo-Server with 2019 (2016 before). First synthetic full needs many times more time then before. Timing of the different jobs also led to the fact that it was worse.

See Anton Gostev’s comment to Windows Server 2022 and ReFS Repositories:

“ While it goes without saying that you should not update your ReFS backup repositories to Windows Server 2022 before we deliver its official support with version 11a, there are always people who feel adventurous or just like to experiment. If you're one of those, please do stick to clean Windows Server 2022 installs for now, as there's the confirmed regression in the ReFS format upgrade code path which may leave your backup repository in the BSOD boot loop.”


The hotfix for this issue is now available:

KB5005619. 

Source:

https://forums.veeam.com/post430029.html#p430029

 

Fine, thanks for the update @Mildur 

Just wanted to post this here but again you’re faster @Mildur. At least this time I’ve noticed it :sweat_smile:

Just wanted to post this here but again you’re faster @Mildur. At least this time I’ve noticed it :sweat_smile:

Haha 🙂 my morning routine. Check the forums.

Since the official image is out, I will be testing this via MDT/WDS soon and may end up performing an in-place upgrade soon.

Has anyone already upgraded? 

We don‘t do in place upgrades in our company.

But we are testing the new edition with our applications.

Comment


Terms & Conditions