Guest Rating:  Votes: 0 rating(s) Score: 0/0 |
Hello,
I have a question about Terminal Server and Licensing on Windows 2003 server.
We have both installed on the same machine, after we checked if this was possible or not
When we start Terminal Server Licensing at this moment, there is no default license server available, but manually we can connect to our license server.
When we do that, we see that it is activated, as it’s meant to be.
We also did buy a 5 user CAL and installed this on the license server.
But, when we connect thought Terminal Services from a client, it seems that the license server does not issue this connection from the installed 5 user CAL but from de default 120-day license.
Our fear is now that after the 120-day license is expired, our terminal server stops working.
Can you explain what is wrong or do you you maybe have a solution for this?
Thanks in advance.
|
|
|
Rating: Votes: 0 rating(s) Score: 0/0 |
Terminal Services always hands out a temp license before it hands out the permanent license. To make sure that the license server is being properly used, specify it in the Terminal Servers registry: http://support.microsoft.com/default.aspx?kbid=279561
Jeff
|
|
|
Guest Rating: Votes: 0 rating(s) Score: 0/0 |
Hello,
I've tried to set this in the Windows registry, and now de server was default discovered in Licensing. However, it still issues no license from the CAL we have installed, when we connect via Terminal Services from a client.
On the client we get an error that our temporary license will expire in 5 days.
Then I tried to uninstall and reinstall Terminal Server Licensing, but when I want to install the user CAL now, I get an error that this CAL already has been activated.
Does anyone know how I can install and activate a user CAL for a second time or how I can deactivate a TS user CAL that has already been installed / activated in the past?
Thanks in advance for your answers.
|
|
|
Rating: Votes: 0 rating(s) Score: 0/0 |
Are you in per user or per device? If you are doing per user, a license will never be taken out of the pool. If you want to reimport your licenses, you'll have to go through the MS clearinghouse and have them reissue your licenses. You can delete the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store\LICENSE00x to force the client to get a new license.
Jeff
|
|
|
Guest Rating: Votes: 0 rating(s) Score: 0/0 |
I have contacted the Microsoft Clearinghouse en got a new license code.
I installed it and it seems to be installed en activated correctly.
I also added the registry key, so that Terminal Services Licensing discovers the license server default and it works.
By the way, we are doing per user.
Is I understand well, when you are in per user mode, you never see anyhting changing in the number of 5 lincenses, when a client connects to the terminal server. Is this right?
I also tested if TS was still working after setting the date of the server and the client to for example the year 2006, and it still works then.
I also installed the Windows 2003 Server Resource Kit and when I use the TSCTST command from a client now, i get the message that the client has no license. Is this right? Has this anything to do with the fact that it is per user?
Can I really assume that everyting works correctly now?
Thanks in advance for your reactions.
|
|
|
Rating: Votes: 0 rating(s) Score: 0/0 |
quote ORIGINAL: Guest
By the way, we are doing per user.
Is I understand well, when you are in per user mode, you never see anyhting changing in the number of 5 lincenses, when a client connects to the terminal server. Is this right?
This is correct, Microsoft have not yet implemented a way to enforce Per User TS licenses. With your 5 CALs you could support 500 users...
|
|
|
Guest Rating: Votes: 0 rating(s) Score: 0/0 |
Thanks everybodey for your reactions.
I think everything is working fine right now. [:D]
Greetings, Paul
|
|
|
Rating: Votes: 0 rating(s) Score: 0/0 |
Jeff -
Does this registry key change work for 64bit as well?
Thanks,
|
|
|