The terminal server cannot issue a client license!! Why not?
I bought 5 TSCAL, but someone I need to access our system keeps getting this message. I have tried from home and it works fine...Please can someone help...
Hi guys
I have a similar problem. Pleeeese help
I have 2 servers, 1st is the DC which has the term serv licenseing program in DC mode and
2nd server is the TS. Both have win2k
All clients were connecting (dumb terms, WinXP, Win98) before BUT NONE were showing up in the TS Licensing program on the DC (on the "Existing Windows 2000 License", or on the "Windows 2000 server - TS CAL Token(per-device)". The branch for Temporary License is not present)
I have license's installed and so all are available.
Now suddenly 1 dumb terminl cannot connect and since none are showing up in the TS Licence program, I believe the other dumb, 98's will start to slowly drop off.
Error on the TS - Source: TermService Evt ID: 1004 and Desc:The terminal server cannot issue a client license"
Error on the DC - Source: TermServLicensing Evt ID: 22 and Desc:The Terminal Services Licensing Server <servername> has no license pack registered for the product 'Windows 2000 Terminal Services Client Access License'. Use Terminal Services Licensing administrative tool to register the license pack
I uninstalled the ts license and reinstalled
On the TS in the registry, I added DefaultLicenseServer in Parameters AND THE subkey LicenseServers - <Servername>
BUT NOTHING WORKS. All or any help would be greatly appreciated
Thank you guys
I'd deactivate your license server then reactivate it and reinstall your CALs. It sounds like your problem is that your license server is unaware of the CALs it has installed.
I have a similar problem also. We're running w2ks sp4 and terminal services. However, i cannot activate the licence server.
Upon running the licensing wizard, I am either greeted with
"Access Denied" or
"The terminal server licensing wizard was unable to access the registry, please make sure you have admin priviledges on the system, and retry the operation. If the problem persistsm make sure the licensing service is installed and running"
I am logged in as administrator, the service is running & i have no idea why the wizard is behaving like this. Any light anyone can shed on this for me is greatly appreciated. The 90 day temp licences are beginning to expire, and it's affecting people's ability to work.
I've got almost the exact problem that Opachu has. Except that the only Terminal Services client access that I have used to date these last 2-1/2 years is for the Domain Admin &/or the server's local Administrator (which is also a Domain Admin) to access from a PC on the LAN or remotely via our IPSec VPN WAN for administrative functions. Now we'd like to make use of the 20 licenses that we bought with the original W2K server (which is our DC) + the 5 licenses that came bundled with it + the 5 that came bundled with our 2nd W2K server (30 total).
Our original licenses were installed on the DC as 'Per-Server' licensing and we'd like to change this to 'Per-seat' licensing, and move the Terminal Server from the DC to the 2nd ('smaller') server to dedicate it to Terminal Services and the shared apps (Office, etc.). Microsoft (live and via Web FAQ) said I just need to uninstall and reinstall the original licenses, adding the 'new' ones in the process.
Only problem is that when I load the wizard, I receive the same errors that Opachu does (see above in his post).
I am logged in as local Admin on the box and a Domain Admin, so I should have the permissions and authority to be able to do ANYTHING on the server.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.