W98 client cannot get permanent TS CAL

[PBurcin]

We are running a XPa MetaFrame farm on W2K (SP2)servers in an NT 4.0 domain. Most of our users have W98 systems. One client in particular is having a very difficult time in getting a permanent TS CAL. The PC was issued a temporary license; it has now expired. The server that was issuing licenses at the time this PC originally got its temp license is no longer the licensing server. The licensing server for this subnet has at least 130 CALs available. It was issuing CALs yesterday just fine. We have deleted the license key from the client system registry, renamed the client system, and updated the Citrix client software. The TS Licensing service was also stopped and restarted. None of the attempts to get a permanent TS CAL have been successful. The licensing server event log shows event 1004 - terminal server cannot issue a client license. Has anyone found a successful way to fix this problem? Why would the licensing server claim that it does not have any client licenses to issue? Any input is appreciated. Thanks.

 

[xs4citrix]

Since your are running SP2 for win2k on your servers; was the famous ts licensing hotfix (can't rememeber the q number) installed, on the one running the TS license service?

http://www.printingsupport.com

Free citrixprinting support

 

[PBurcin]

Yes, the TS licensing hotfix has been installed. BTW the Q is 287687.
Any ideas?

 

[xs4citrix]

Did the win98 client get his temporary TS license, before the hotfix was applied to the TS license server?

http://www.printingsupport.com

Free citrixprinting support

 

[PBurcin]

The hotfix was installed when the server was built several months ago. A couple of things happened last night that seemed to have fixed the problem, at least for this particular client. #1 - all servers in the farm performed their automated reboot. #2 - the roaming profile contents were deleted for this particular client. This morning, first attempt to login was successful. No errors in the event log for the licensing server.

 

[BeerGood]

Sounds like the reboot fixed things, but FYI just in case I'd check:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters
Name: DefaultLicenseServer
Data type: REG_SZ

on the terminal server and make sure that the data value is not pointing to the old (no longer around) licensing server (IP or name). If you don't have this, then the Terminal Server should auto-discover the licensing server. If it's set, then it will not be able to locate your new licensing server.

Also, the licensing server needs to be in the same workgroup/domain, or the above registry setting enabled.

Cheers

 

[PBurcin]

Thanks for the input BeerGood. However, again when the servers were built, the registry key you are referring to was updated to point the DefaultLicenseServer --> to the only licensing server in the domain/on the subnet in question. See Q239107 for the information I used to set this up.

Even with this setup, the client in question could not get a new CAL from the licesing server until 1.) the server reboot, and 2.) deletion of the roaming profile contents.

Thanks for your comments.