funtrio.blogg.se

1. #Server 2016 remote desktop services point to license software#
2. #Server 2016 remote desktop services point to license license#
3. #Server 2016 remote desktop services point to license windows#

#Server 2016 remote desktop services point to license license#

However, when the Remote Desktop Session Host role is installed, it needs a license server because the server is actually running as a RDS host, thus RDP is supposed to be used by actual clients instead of remote administrators if a valid license server can't be found, or if it doesn't have enough licenses, the server will accept RDP connections for a while (the "grace period") and then stop allowing them.īut again, for this to be the case, the Remote Desktop Session Host role must be installed if it's not installed, there is no way or reason for the server to require RDS licenses.

#Server 2016 remote desktop services point to license windows#

You can always log in via RDP to a Windows Server 2016 machine in order to manage it there is a hard limit of two concurrent connections and no grace period.

The fact that neither the role nor the license configuration appears to be present on either machine (including the working one!) is baffling.Ĭan this be configured somehwere else? What am I missing? My understanding is that for a user to connect via RDP, you either have to be running in the "grace period" or have RDP licenses available. I also ran gpresult and there is nothing in the report at all about RDP licensing. In gpedit, all settings related to RDP licensing are "not configured" on BOTH machines. However, the Remote Desktop system service is running on both machines. The machine where RDP works has been runnning for 3+ years so I'm pretty sure it's not working due to "grace period". The funny thing is, on both servers, neither the Remote Desktop Services nor the Remote Desktop Licensing roles or features appear to be configured or installed. In Server Manager, open the Tools menu, expand Terminal Services (or Remote Desktop Services), and click RD Licensing Diagnoser. "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. On the other one, when I try to log in with my username via RDP, I get the following error: On one of them I can log in with my username via RDP.

#Server 2016 remote desktop services point to license software#

You can also set this through registey : HKEY_LOCAL_MACHINE –> SOFTWARE –> Policies –> Microsoft –> Windows NT –> Terminal Services LicenseServers = license server name

Under Computer Config -> Windows Components/Remote Desktop Services/Remote Desktop Session Host/Licensing Set the Remote Desktop licensing mode Enabled Use the specified Remote Desktop license servers Enabled The solution is set the mode through GPO : Remote Desktop licensing mode is not configured. Some time you get errors about terminal server licensing mode and no more connection can be made to the terminalĪn event id 4634 can occur and event ID 50, in the license diagnostig you can get : The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode,īut license server da-server-host does not have any installed licenses.