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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2003 As a Terminal Server 1

Status
Not open for further replies.

snootalope

IS-IT--Management
Jun 28, 2001
1,706
US
Hello

We recently upgraded to windows 2003 server from 2000 server for our terminal services. Currently, our 2003 machine is acting as the term serve license server. It's passing out device CAL's to 3 2000 server machine's running citrix.

Here's the problem: Clients who were origanily given TEMPORARY device cals are now unable to logon because they can't pick up a permanent CAL. What's weird is, It's only about 18 WYSE terminals that are doing this. Right now i've got 200 permanent device CALs and about 70 of them are taken up. I need those TEMP licenses to be killed and new ones given, but i'm getting this error on the 2003 machine when one of those 18 people try to sign on:

Unable to reflash our terminals. The terminals we're having trouble with are less than a year or so old and they have the latest firmware. The only firmware available for download from Wyse is atleast two versions older.

I did flash the configuration and reflash it to other terminals though. Still didn't work.

Rebooted our terminal server last night as well. Still getting the same error:

Event Type: Warning
Event Source: TermServLicensing
Event Category: None
Event ID: 21
Date: 6/2/2004
Time: 7:31:07 AM
User: N/A
Computer: Server1
Description:
The Terminal Server Licensing server Server1 has no permanent licenses for product 'Windows Server 2003 - Terminal Server Per Device CAL Token'. Use Terminal Server Licensing administrative tool to register more licenses.

I've reactivated my Term Serve. Installed new Client Packs from the MS clearing house, and I've also restarted the Term Serv License service and waited the ten minutes for them to switch pools, as well as reboot that server...

any ideas?
 
Hi,

I got error 1004, and one of term couldn't connect,last week, I just reset that capio and it works. Do you check eventid.net for eventid 21?
 
I know that if you convert your 'per device' CALS to 'per user' you probably won't have any more problems.

I'm guessing your problem has to do with the way the 'per device' mechanism deals with the WYSE workstations--it may have trouble properly allocating for that type of device. I know that's obvious.

ShackDaddy
 
The Terminal Server Licensing server Server1 has no permanent licenses for product 'Windows Server 2003 - Terminal Server Per Device CAL Token'"

That error is usually pretty self explanatory. You say you purchased and installed new CALs? What kind of CALs are installed on the server?

Please list all license groups that are listed in the license manager currently.
 
Hi guys.. First of all, if you read into windows 2003 USER CALs, you'll see it says..."User CALs cannot be issued to Windows 2000 terminal servers or to clients that access Windows 2000 terminal servers.." So this is definitly not a Device vs. User confussion..

Here is what is listed in my Terminal Server Licensing currently:

Existing Windows 2000 Server-Terminal Services CAL Token (per device) - Unlimited

Temp Licenses for Windows 2000 Server - Terminal Services CAL Token (per device)

Windows server 2003 - Terminal Server Per Device CAL Token - 10 total 10 Available

Windows Server 2003 - Terminal Server Per Device CAL Token - 75 Total 74 Available

What i've done since I posted this is deactivated the server, deleted the license file, and then reactivated and resinstalled the licenses. I'm still getting the same error though..

snoots
 
I have win 2003 server with using to connect with win2k pro worstation and up pops message saying that "cannot logon to session" i have ticked the "user" setting in T/S config,
Does any one have any idea why I get this message from Win2k Pro client when connecting to my T/S 2003 server.
 
Hello
I found an article in the ms knowledge base: you should re-install the licenses! I have had the same problem by one of my customer and this was the solution (I also move the license server from the dc to the ts).
As workaround, you could also change the licensing mode to user cal: no check will be made regarding license usage ...
Regards - Vincent
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top