siemensnm
asked on
Terminal Server problem
Hi,
I'm having problems with a Windows Server 2008 Terminal Server. I have 25 (per device) CALs installed and Remote Desktop sessions are working from most of the machines.
However, there are 2 Windows XP machines that are unable to establish a RDP session with an error message about missing CALs. These are the errors produced in the Terminal Server's Event Log:
Event ID: 1028
The remote session could not be established from remote desktop client CLIENT_NAME because its license could not be renewed.
and
Event ID: 21
The Remote Desktop license server "SERVER_NAME" does not have any remaining permanent Remote Desktop Services client access licenses (RDS CALs) of the type "Windows Server 2008 or Windows Server 2008 R2 : Per Device CAL (TS, RDS or VDI)". As a result, the Remote Desktop license server cannot issue RDS CALs of the type "Windows Server 2008 or Windows Server 2008 R2 : Per Device CAL (TS, RDS or VDI)" to the Remote Desktop Session Host server "SERVER_NAME". To resolve this problem, verify that the Remote Desktop licensing mode configured on the RD Session Host server matches the type of RDS CALs installed on the Remote Desktop license server. If required, purchase and install additional RDS CALs as needed for this Remote Desktop license server.
I tried everything, including changing the name of the client and regenerating it's SID.
Another piece of information: I've imported the CAL's in two stages: first 5 licenses and then 20. I've noticed in the RD licensing manager that the first 5 are already allocated and new device licenses are issued from the "Temporary Per Device CALs". The entry with the 20 device CALs is empty. Shouldn't it have allocated licenses from it first?
Thanks.
I'm having problems with a Windows Server 2008 Terminal Server. I have 25 (per device) CALs installed and Remote Desktop sessions are working from most of the machines.
However, there are 2 Windows XP machines that are unable to establish a RDP session with an error message about missing CALs. These are the errors produced in the Terminal Server's Event Log:
Event ID: 1028
The remote session could not be established from remote desktop client CLIENT_NAME because its license could not be renewed.
and
Event ID: 21
The Remote Desktop license server "SERVER_NAME" does not have any remaining permanent Remote Desktop Services client access licenses (RDS CALs) of the type "Windows Server 2008 or Windows Server 2008 R2 : Per Device CAL (TS, RDS or VDI)". As a result, the Remote Desktop license server cannot issue RDS CALs of the type "Windows Server 2008 or Windows Server 2008 R2 : Per Device CAL (TS, RDS or VDI)" to the Remote Desktop Session Host server "SERVER_NAME". To resolve this problem, verify that the Remote Desktop licensing mode configured on the RD Session Host server matches the type of RDS CALs installed on the Remote Desktop license server. If required, purchase and install additional RDS CALs as needed for this Remote Desktop license server.
I tried everything, including changing the name of the client and regenerating it's SID.
Another piece of information: I've imported the CAL's in two stages: first 5 licenses and then 20. I've noticed in the RD licensing manager that the first 5 are already allocated and new device licenses are issued from the "Temporary Per Device CALs". The entry with the 20 device CALs is empty. Shouldn't it have allocated licenses from it first?
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks!!!
fix in Reece's Registry Fixes folder.
on a client that is running Windows Vista or a later version, later attempts to connect to a Terminal
Server may fail. Also, you receive the following error message:
An Error occurred in the Licensing Protocol
To resolve this problem, right-click the Remote Desktop Connection shortcut, and then click Run as
Administrator. By default, the remote desktop connection runs as a user with the lowest user
permissions. By default, a restricted user does not have permission to write registry entries to
HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail. Starting Remote
Desktop Connection with administrative credentials provides the permissions that are necessary to
write the needed registry keys.