Edge Chromium Server 2016

If you are looking for the Microsoft Edge browser on Server 2016, look no further, it isn’t available! This is due to Windows Server 2016 being in the Long-Term Servicing Branch and the quicker rate of change of the Edge browser can’t be supported.

Edge Chromium as a separate download ^. Since the first generation of Edge did not exist on the server, the Chromium version now fills this gap. To date, however, it has not been included with the installation media of Windows 10 or the server, so you have to download and install the browser yourself. Windows Server 2012 R2; Windows Server 2016 (LTSC) Windows Server 2019 (LTSC) Windows Server (SAC) Important. We will continue to support Microsoft Edge on Windows 7 and Windows Server 2008 R2 until January 15, 2022. These operating systems are out of support and Microsoft recommends you move to a supported operating system such as Windows 10.

The official response from Microsoft is:
“The Long-Term Servicing Branch (LTSB) versions of Windows, including Windows Server 2016, don’t include Microsoft Edge or many other Universal Windows Platform (UWP) apps. These apps and their services are frequently updated with new functionality, and can’t be supported on systems running the LTSB operating systems. For customers who require the LTSB for specialized devices, we recommend using Internet Explorer 11.”

Source: https://docs.microsoft.com/en-us/microsoft-edge/deploy/hardware-and-software-requirements

It’s a shame not to have a consistent user experience between Windows 10 and Server 2016 especially in environments that use Remote Desktop Services.

Microsoft Edge Chromium Windows Server 2016

By default, Windows Integrated Authentication (WIA) is enabled in Active Directory Federation Services (AD FS) in Windows Server 2012 R2 for authentication requests that occur within the organization's internal network (intranet) for any application that uses a browser for its authentication.

AD FS 2016 now has an improved default setting that enables the Edge browser to do WIA while not also (incorrectly) catching Windows Phone as well:

The above means you no longer have to configure individual user agent strings to support common Edge scenarios, even though they are updated quite often.

For other browsers, configure the AD FS property WiaSupportedUserAgents to add the required values based on the browsers you are using. You can use the procedures below.

View WIASupportedUserAgent settings

The WIASupportedUserAgents defines the user agents which support WIA. AD FS analyzes the user agent string when performing logins in a browser or browser control.

You can view the current settings using the following PowerShell example:

Change WIASupportedUserAgent settings

By default, a new AD FS installation has a set of user agent string matches created. However, these may be out of date based on changes to browsers and devices. Particularly, Windows devices have similar user agent strings with minor variations in the tokens. The following Windows PowerShell example provides the best guidance for the current set of devices that are on the market today that support seamless WIA:

If you have AD FS on Windows Server 2012 R2 or earlier:

Edge For Windows Server 2016

If you have AD FS on Windows Server 2016 or later:

The command above will ensure that AD FS only covers the following use cases for WIA:

Edge Chromium Windows Server 2016 Download

Additional links