![Edge chromium server 2016 Edge chromium server 2016](/uploads/1/3/4/6/134662371/872681403.jpg)
Microsoft Edge based on Chromium, available and supported on Windows 7, 8 and 10 and most importantly in Windows Server 2008 R2, 2012/2012 R2, 2016 and 2019. This means that we now have a modern and secure browser that can be managed via Group Policy and is supported by Microsoft in a server operating system. I have a Windows domain running at Server 2016 functional level and I'm testing with Windows 10 Enterprise (1809) LTSC clients fully domain joined, fully updated. I've installed the latest 'Edge for Business' version 84.0.522.48. I'm trying to configure it with GPO and so far the only GPO that sticks is the start page URL. 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. On a server with a desktop, the procedure is the same as on a client OS. Anybody running the MS Edge Chromium on 2016 VDAs? Any benefits or drawbacks compared to Chrome Enterprise? We have a lot of old web apps that still only work in IE so having capability of Edge to fallback to IE might be helpful.
It is not possible to use smartcard in Microsoft Edge browser in Citrix session on windows 2016 terminal server. In all other popular browsers is smartcard working correctly (Chrome, Firefox, Internet Explorer). When connect to same server using RDP, than smartcard is working in Edge.
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.
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.”
“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.
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:
Edge For Servers
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:
If you have AD FS on Windows Server 2016 or later:
Microsoft Edge Chromium Server 2016
The command above will ensure that AD FS only covers the following use cases for WIA:
Edge Chromium Windows Server 2016
User Agents | Use cases |
---|---|
MSIE 6.0 | IE 6.0 |
MSIE 7.0; Windows NT | IE 7, IE in intranet zone. The 'Windows NT' fragment is sent by desktop operation system. |
MSIE 8.0 | IE 8.0 (no devices send this, so need to make more specific) |
MSIE 9.0 | IE 9.0 (no devices send this, so no need to make this more specific) |
MSIE 10.0; Windows NT 6 | IE 10.0 for Windows XP and newer versions of desktop operating system Windows Phone 8.0 devices (with preference set to mobile) are excluded because they send User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows Phone 8.0; Trident/6.0; IEMobile/10.0; ARM; Touch; NOKIA; Lumia 920) |
Windows NT 6.3; Trident/7.0 Windows NT 6.3; Win64; x64; Trident/7.0 Windows NT 6.3; WOW64; Trident/7.0 | Windows 8.1 desktop operating system, different platforms |
Windows NT 6.2; Trident/7.0 Windows NT 6.2; Win64; x64; Trident/7.0 Windows NT 6.2; WOW64; Trident/7.0 | Windows 8 desktop operating system, different platforms |
Windows NT 6.1; Trident/7.0 Windows NT 6.1; Win64; x64; Trident/7.0 Windows NT 6.1; WOW64; Trident/7.0 | Windows 7 desktop operating system, different platforms |
Edg/ and Edge/ | Microsoft Edge (Chromium) for Windows Server 2012 R2 or earlier |
=~Windowss*NT.Edg. | Microsoft Edge (Chromium) for Windows Server 2016 or later |
MSIPC | Microsoft Information Protection and Control Client |
Windows Rights Management Client | Windows Rights Management Client |