italyllka.blogg.se

Take a close look at the events in the Event Viewer on the RDS host. Reset 120 Days RDS Grace Period (L$RTMTIMEBOMB)

This could be caused by network connectivity problems, the Remote Desktop Licensing service is stopped on the license server, or RD Licensing isn't available. If the RDS License server is not available, the License Diagnoser will display an error: License server rdslic_hostname is not available. In this case, the MSLicensing reg key will be automatically re-created, and the computer will receive a new RDP license.Īs you can see, LicenseServer is specified in the configuration, and the PerUser licensing type is used.Ĭheck that the following ports are not blocked by firewalls when accessing from RDSH host to RDS LicenseingServer: TCP 135, UDP 137, UDP 138, TCP 139, TCP 445, TCP 49152–65535 (RPC range). Close the registry editor and run the mstsc.exe (Remote Desktop Connection) as as administrator.Remove the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.Start the Registry Editor ( regedit.exe).In this case, you need to reset this expired license in the registry on the client device.ĭo the following on the client computer (Windows 10 in this example): Most likely, in this case the client computer is trying to connect to your RDSH server with an expired temporary RDP license (if your RDS license server was unavailable when the client first connected, the client was issued a temporary RDP license for 180 days). When connected, your users will always receive a temporary local Per Device license. If your RDSH server is deployed in a workgroup (not in an AD domain), then you cannot use Per User RDS licenses on it.