Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Temp licenses expriring

Status
Not open for further replies.

sudip00

MIS
Dec 23, 2002
49
US
Hi,
I have a win2k3 sever runningcitirx metaframe. The server keeps handing out licenses from "Temporary licenses for Win 2003....." instead of the 25 per user cale term server licenses that I installed. All the clients keep gertting a message stating their license will be expiring on mm/dd/yyyy. The date varies per user. The clients are xp and win 2k pro.
Any ideas?
thanks.
 
You have to install, and activate a windows 2003 terminal services server. Then add in your 25 cals

[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott
 
The citrix server is a 2003 server running terminal services. Should'nt that work?
 
The 2003TSE servers pull Microsoft 2003 TSE licenses from a 2003 License server. Even if you do configure your environment with a 2003 license server in a "per-user" mode...the licenses will not decriment due to Microsoft not completing that part of licensing. When you query the client using Microsoft's tool to troubleshoot licensing, it returns info about the client as if it has a temp license. However, it functions fine as long as the TSE/Citrix server knows about the license server. See the link below for good info.

 
No you must have a Windows2003 Terminal Servicese License Server as well.

[blue]Arguably the best cat skinner around ! [/blue]

Cheers
Scott
 
Ascotta,
I setup a Win2k3 License server. How can I specify to ctirix to check with server?
thanks.
 
Everything is in the link in my previous response. If you take the time to read, you might find the answer to your next question.

"Hard-Coding Preferred License Servers
Regardless of which of these four situations a Terminal Server is in, you always have the option of manually specifying a license server or servers that each Terminal Server should get licenses from. You can manually configure any Terminal Server to get licenses from any license server—there’s no need to stay within domain, subnet, location, or site boundaries.

You can configure a Terminal Server to use a specific license server via the Terminal Server’s registry. Be careful though, because this registry edit is not like most others. In this case, rather than specifying a new registry value and then entering data, you have to create a new registry key (or “folder”). To do this, browse to the following registry location:

HKLM\SYSTEM\ControlSet\Services\TermService\Parameters\

Add a new key called “LicenseServers.” Underneath the new LicenseServers key, create another key with the NetBIOS name of the license server that you want this Terminal Server to use. You don’t need to add any values or data under this new key."

 
Mitchero,
Thanks, i got it to look at the right server now. But the new license server still keeps handing out Temporary Win2k3 licenses to the clients instead of the 25 licenses that we purchased. All 25 are unused. Any idea?
 
We upgraded our Citrix farm to 2k3 and noticed that we had problems with clients getting licenses or getting temp licenses.
We had already specified the entry that mithcero mentioned above but we had to add a couple of more steps.
We added a seperate entry under the LicenseServer key with the fqdn and ip address of our license server.

Hope that helps.
 
Per user licensing in Win2k3 has not been completed by Microsoft. Until it is completed, you will always have 25 licenses available no matter how many users connect to your environment when you are in this mode...and it will appear as though temp licenses are being distributed. As stated in the article that I linked...here's the spoon-fed version of what you're looking for...

"Terminal Servers configured for User-Based CALs

Everything discussed in the previous section is applicable only when Terminal Servers are config-ured in “per device” licensing mode. When a user connects to a Terminal Server configured in “per user” licensing mode, a different process takes place.

When Terminal Services is installed on a Windows 2003 server, the server verifies that it can find (via the discovery process outlined previously) a license server.
There is no Step Two.

That’s right. All this TS CAL digital certificate, temp license, transfer mumbo-jumbo only applies when Terminal Servers are configured for “per device” licenses. With per user licenses, all you have to do is make sure that the Terminal Server can find a license server. (The license server doesn’t even have to be activated!) Other than periodically verifying that it exists, there’s no com-munication between a “per user” configured Terminal Server and a license server.

How did this come to be? When Windows 2003 was in beta testing, Microsoft was planning to offer a “per processor” licensing model. At the last minute (with Release Candidate 2), Microsoft changed its mind and decided to go with a “per user” option instead. This decision was a popular move on Microsoft’s part. The only problem was that it was so late in the game that Microsoft didn’t have time to build the “per user” technical license compliance infrastructure (although you can bet we’ll see it in future versions of Windows).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top