sammydlc
asked on
The remote session was disconnected because there are no Terminal Server license servers available to provide a license
I have the following setup.
1 Windows 2003 Terminal Licensing Server issuing licenses.
3 Windows 2003 Terminal Servers running application mode.
Recently one of my users started receiving this error message when trying to connect to any of the TS.
"The remote session was disconnected because there are no Terminal Server license servers available to provide a license"
I have over 300 users and none have the same error except this one. I deleted the MsLicensing Reguistry entry on the client's computer to try to refresh the temporary license but no luck. If I go to the licensing server I see this computer listed under the Temporary License but there is no way to deleteing direclty on the Licensing Server.
Any help is really appreciated
1 Windows 2003 Terminal Licensing Server issuing licenses.
3 Windows 2003 Terminal Servers running application mode.
Recently one of my users started receiving this error message when trying to connect to any of the TS.
"The remote session was disconnected because there are no Terminal Server license servers available to provide a license"
I have over 300 users and none have the same error except this one. I deleted the MsLicensing Reguistry entry on the client's computer to try to refresh the temporary license but no luck. If I go to the licensing server I see this computer listed under the Temporary License but there is no way to deleteing direclty on the Licensing Server.
Any help is really appreciated
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I logged into my Terminal Server and opended the Licensing Server MMC, (Start-Programs-Administra
I noticed that when it opened, it dscaned for LS but did not find any. I then clicked on ACTION - CONNECT and supplied the correct LS. It connected without any problems.
I closed the MMC and reopened and had the same issue where the LS was not identified.
I then edited the registry to specify my TS where my LS was.
On the TS went to REGEDIT-
HKEY_LOCAL_MACHINE\SYSTEM\
Here I created a new KEY and named it as my LS.
HKEY_LOCAL_MACHINE\SYSTEM\
Closed regedit and opened it.
WALLA, THE TS now could See the LS.
Then I went to the client and Deleted the MSLicensing registry key
Retried and the client was able to connect.
Thanks for all your help.