The problem exists when attempting to connect RDP from personal home PCs (not managed by company GPOs and MS update schedules) over VPN.
The problem remains and is exactly the same.
It doesn't matter if the RDP connection is initiated from a windows 7, windows 10 or Windows Server 2012 R2.
We only have a few windows 10 machines but no issues found on those so far.
The problem is on random machines, all windows 7.
All clients are set per GPO to use the Remote Setting of the "more secure" option:.
So please don't ask me to check this on the about remote desktop connection window.
Network level authentication IS supported on all machines as per the About Remote Desktop Connection.
Just to be clear: no errors pop-up whatsoever in Group Policy, System, Application and Administrative Event Logs on the Terminal Servers and connection broker servers.Īny guidance on how i can troubleshoot this please? It states: "There's a problem with Remote Desktop Licensing - There is a problem with your license for Remote Desktop and the session will end in 60 minutes. If we logon with our test users (5 of them) we all get this error. Servers and re-added them with per device licensing mode. Next we changed the deployment properties 'RD Licensing' mode: we removed both lic For this change we rebuild the RD licensing database and re-added the per-device licenses. We changed the licensing mode from per user to, per device (an initial mistake). No errors or warning pop-up regarding licensing (though RD Licensing Diagnoser is no longer available in WS2016 apparently). Licensing is configured on both licensing servers - licenses per device are added on both and is integrated with AD. 2 servers with connection broker, gateway, web server and licensing role (ha mode) installed and 4 session hosts - all on WS2016Standard. I'm building a new RDS farm on Windows Server 2016.