Case 1: The client installed 2008 RDS CALS on Windows 2008 server in a Windows 2003 domain network. When connecting to the 2008 RDS servers the client receives the following error: "The remote session was disconnected because there were no Remote Desktop License Servers available to provide a license."

Resolution: Windows 2003 AD and the Default Domain Policy had registry security settings applied. Also, the Windows 2008 R2 servers have a group called, "TermService" which is not a group in 2003 AD.

After running "subinacl" to apply permissions to the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\" key for the SID "S-1-5-80-446051430-1559341753-4161941529-1950928533-810483104", the RDS host server could then read/write the appropriate license information to the registry.

Case 2: Please follow this post to Specify a license server for 2008 R2 RD Session Host server

Case 3: This issue occurred on a Windows 2008 R2 server in a Windows 2003 AD.

Resolution: download the "subinacl.exe" from Microsoft but do NOT use the subinacl.exe version from the W2k3 Resource Kit (shows version 4.x, if I remember correctly); this version is flakey.

Run this command:

subinacl /keyreg "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM" /grant=S-1-5-80-446051430-1559341753-4161941529-1950928533-810483104=F

Case 4: That could be the permission issue which was not set correctly on the registry key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM and it was unable to change the "Licensing Core\Licensing Mode" key. The key was set to 5, which does nto appear to be valid. Valid entries are 2 (for per device) or 4 (for per user). I used the subinacl command subinacl /keyreg "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM" /grant=S-1-5-80-446051430-1559341753-4161941529-1950928533-810483104=F, re-installed the RDS Licensing and specified the same options as before. After the re-install with the correct permissions on the Reg Key the licensing mode was set correctly and its working perfectly now.

Case 5: One of our clients receives the same error. They don't have Remote Desktop for their Windows Server 2012. But they want to access the server remotely. The resulotion is running administrative mode, for example mstsc /admin. Then they can login the server remotely.

Contact a consultant

Related Topics

Bob Lin Photography services

Real Estate Photography services