Confusion on TSCALs, Domain or workgroup server

[rjs]

I've read the docs, white papers and forum threads and anything else I can get my hands on, but am still unsure about some setup and licensing stuff.

There will be 4 Metaframe XP servers in the farm using Windows 2000 server. There are NO other Windows 2000 or NT servers in this environment. It is all NetWare. I'm confused on two points, both regarding the Windows 2000 component:
1) TSCALs. I've read that these are not pooled. Does this mean if I have 100 users (machines) and 4 servers that I need 100 TSCALs for each server since any user could connect to any server? Or do I just need 100 total?
2) Since I have no other 2000 servers or a 2000 domain, can I put the Terminal licensing server component on one of the Metaframe servers, all of which would be workgroup servers? Or do I need a separate box to be the Windows 2000 domain controller and the TS licensing server?

 

[gbiello]

1) I does seem you need a PhD to understand MS TSCAl licensing. It is my understanding they weren't pooled, now they are. To make TSCal's more friendly, you need either W2Ksp2 with a hotfix I could send you if you post your email address, or W2Ksp3. There have been TS issues with sp3, so I would only apply it if you needed it.

2) You should be able to make any server you want the Licensing server.

Also. The TSCal's are stored in the LSERVER directory. I make it a point to back up this directory as soon as the licenses are activated. You will need to stop the TS Licensing service first. Should you run out of TSCals, you can call M$ and get more at no charge, as long as you have your original licensing paperwork. You can get the number from the TS Licensing application, by selecting "Register by phone".

hope this helps,
-gbiello

 

[chjinmind]

1. TSCALs
TSCALs are static licenses. Either the client have one or not. If the OS of the client is NOT 2k pro or XP, the client needs a TSCAL.
TSCALs are issued by a server in your environment that has the Terminal Services Licensing service installed (YOU determine wich server this should run on).
After you install this service you have to activate the server (phonecall or internet contact with MS clearinghouse) AND add some TSCALs. The amount depending on the number of physical clients you have. A TSCAL is stored in the registry on the client machine, once taken, never returned. (though it can be moved by exporting the registry branch on the client machine)

The Terminal Services licensing service only needs to be installed on ONE of your servers, the others will find it. (otherwise you can edit it "hard" in the registry)

The TSCALs are not to be confused with the citrix licenses wich are retuned as soon as the session ends. Citrix licenses the use and features of the ICA protocol, MS the right of executing software under thin client environment, roughly said.

2. As described in "1". Only install the component on one of the servers, the others will find it.

If you later migrate the servers to a domain, the domain controller automatically takes over the TS Licensing service, so be sure to export the license information before moving the server that holds the information before moving it into a domain.

Hope this helped a bit in the licensing swamp...

 

[buckybucky]

Here's the skinny,

In your environment you need 1 tscal for every device that will connect to the Citrix Servers not every user as each user could have more then one device, ie home and office.

If there is no domain controller you can install the license server on one of the Metaframe servers and it will work fine but you also need to make a registry change on all the other servers. Here it is ... HKEY Local Machine\system\currentcontrolset\services\termservice\perameters add a reg_sz value named DefaultLicenseServer with a value of <ServerName> where <servername> is the netbios or IP address of the license server. This needs to be done because the Terminal servers will only look for a Domain controller during the broadcast process and not other Member Servers. This will also assure that they will find a license and not give errors, even in a domain.

Hope that helps
Bucky