The configuration of Microsoft Edge can be done via AD group policies or Microsoft Endpoint Manager (InTune), in this article I’ll focus on how to configure Microsoft Edge via AD group policies. I’ll focus on how to install and configure Edge, there are some pitfalls there to be aware of. However this article will have some bits of new content, specifically around the Sleeping Tabs and Password Monitor features. The curious case of the pinned Microsoft Edge shortcut Microsoft Edge Group Policy Configuration This article will serve as a condensed version of my previous articles about Microsoft Edge which you can find here: In the coming Windows Server 2022, the Microsoft Edge browser is of course built-in. The stable release of Microsoft Edge was in my opinion huge and it still is because with Microsoft Edge we get a modern and secure browser which is supported in both Windows 10 (v1709 and later) and the Windows Server operating systems (2008 R2, 2012, 2012 R2, 20). At that time I had used the BETA edition of Microsoft Edge for quite some time and I was thrilled to see it enter the stable release channel. I am tired of roaming the internet searching for answers.During Citrix Summit back in January 2020, I posted my first article about the Microsoft Edge browser based on the Chromium Project. In my lab deployment there is no NLB anymore (as Connection Broker should take care of the load balancing) so when I connect (using Remote Desktop) to (resolves to the public IP of the RDS Gateway), I am presented with the 'Only members of the Remote Desktop Users group is allowed' message which makes no sense as I am using my domain admin account for testing.Īs I mentioned, at this point, I am ready to pay ayone that makes this thing works.

Here's the issue, my 200+ users in three countries are used to open remote desktop connection on their Windows desktops and connect to which resolved to an NLB cluster of two 2008 R2 servers. At this point, I am willing to pay anyone (out of my pocket) to get it done.

I have followed Molan's tutorial as well as many others and can't get it to work.

All we want is to provide the same RDC experience my users had with 2008 Terminal Server. I am struggling to understand this new RDS.

Windows 2008 r2 terminal server