What are the benefits of Windows Server 2022?

Get the most out of Windows Server with these 5 best practices 

March 1, 2022 2 min read

  • What are the benefits of Windows Server 2022?

    By Patrick WidjajaProduct Marketing Manager, Azure Marketing

We’ve invested in Windows Server for nearly 30 years, and we continue to find new ways to empower businesses who trust Windows Server as the operating system for their workloads. Over this time, we understand that business requirements have become more complex and demanding. Thus, we are energized when we hear how customers continue to Read more

5 new capabilities to automate Windows Server management with Azure Automanage 

November 2, 2021 2 min read

  • What are the benefits of Windows Server 2022?

    By Bernardo CaldasVice President of Program Management, Core OS and Edge Infrastructure

Customers of all sizes trust Windows Server to run their business and mission-critical workloads. With the launch of Windows Server 2022, we’ve added new capabilities that bring the best of Windows Server and Azure together. Whether you’re migrating to the cloud, modernizing applications, or managing a hybrid environment, you can take advantage of unique innovations Read more

Get a first look at Windows Server 2022—register for the free Windows Server Summit 

September 9, 2021 2 min read

  • What are the benefits of Windows Server 2022?

    By Liam SosinskyProduct Marketing Manager

You are invited to get a first look deep-dive at Windows Server 2022 by registering for the free, fourth annual Windows Server Summit, September 16, 2021, from 10:00 AM – 11:30 AM Pacific Time. Be among the initial set of customers to learn about investments we are making in Windows Server, Windows Server on Azure, Read more

Windows Server 2022 now generally available—delivers innovation in security, hybrid, and containers 

September 1, 2021 3 min read

  • What are the benefits of Windows Server 2022?

    By Bernardo CaldasVice President of Program Management, Core OS and Edge Infrastructure

Today, we are announcing the general availability of Windows Server 2022. It’s a big step forward for the operating system that is trusted by major corporations and small businesses alike to run their business and mission-critical workloads.  With Windows Server 2022, customers can continue to securely run their workloads, enable new hybrid cloud scenarios, and modernize their applications to meet evolving business Read more

Announcing public preview of Windows Admin Center in the Azure portal 

March 2, 2021 2 min read

  • By Microsoft Windows Server Team

This post was authored by Hari Pulapaka, Partner Group Program Manager, Windows Windows Admin Center, your favorite server management tool, is now available in preview in Azure. This new capability enables seamless and granular management of your Windows Server Azure IaaS virtual machines (VMs) from within the Azure portal. Here is a short video highlighting some Read more

One of the new features Windows Server 2022 brings is native support for hosting HTTP/3 services. In this post, we will discuss how to enable it and how it can benefit web services.

HTTP/3 is a major overhaul of HTTP with performance and security in mind. It uses QUIC as a transport (our HTTP server, http.sys, is using msquic) to gain the benefits of eliminated head of line blocking at the transport layer. This is a significant improvement over HTTP/2 which eliminated head of line blocking only at the HTTP layer with streams that allowed a single HTTP/2 connection to replace a set of HTTP/1.1 connections. HTTP/3 also benefits from many lessons learned in HTTP/2, such as simplifying the protocol by removing prioritization.

The HTTP/3 standard is nearly complete; its final publication as an RFC is only waiting on formal process at this point. It is already supported by major browsers which means web services are ready to benefit from deploying it.

One thing to note before proceeding: these instructions presume there were no changes made to the list of enabled TLS cipher suites on the Windows Server 2022 installation. If this is not the case, consult RFC9001 (“Using TLS to Secure QUIC”) and ensure there are some cipher suites in common between the server and its expected clients. HTTP/3 is built on QUIC which requires TLS 1.3. Turning off TLS 1.3 or disabling TLS 1.3 cipher suites will result in HTTP/3 deployment failures. See “TLS Cipher Suites in Windows Server 2022” to learn how to add cipher suites and which ones are enabled by default.

HTTP/3 support is opt-in on Windows Server 2022 via a registry key named “EnableHttp3” with value 1 at “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters”. Running this command from an elevated prompt will create the key:

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters" /v EnableHttp3 /t REG_DWORD /d 1 /f

Once this key is set, either restart the http.sys service or reboot Windows to apply the setting.

It is likely the web service will need to advertise it is available over HTTP/3 as well using “Alt-Svc” headers in HTTP/2 responses (though this can also be done using HTTP/2 ALTSVC frames). This allows clients who connect over HTTP/2 to learn the service’s HTTP/3 endpoint and use that going forward. This is done by sending an HTTP/3 ALPN (“Application-layer Protocol Negotiation”) identifier with HTTP/2 responses advertising a specific version of HTTP/3 to use for future requests. Sending the ALTSVC frame  can be done by http.sys. That can be enabled by setting the “EnableAltSvc” registry key with the command below. To apply the setting, restart http.sys or reboot Windows.

reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters" /v EnableAltSvc /t REG_DWORD /d 1 /f

If all goes well, the service will start serving content over HTTP/3. To ensure this is happening, use Edge to verify the protocol used to serve the web request. Right click on the page, select “Inspect”, then select the “Network” tab. If only “h2” is being used in the “Protocol” column instead of “h3”, try refreshing the page to ensure the ALPN is being honored (the first request will use HTTP/2 which will then advertise HTTP/3 support to Edge for future requests).