Rdesktop Licensing

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I don't understand how to configure the correct licensing mechanism W2K 
Terminal-Server and PXES-ThinClient.

First of all I'll try to explain my current configuration.
At the server side I'm using a W2K Terminal Server with 8 TSCAL's installed.
At the client side there are 8 different desktop machines and 1 Notebook with 
Win95 installed. (The notebook was purchased with Windows 2000 prof.  
installed.)
Theres is a second notbook currently running Windows 2000 professional.
There are some additional other machines, using dhcp but not using 
terminal-services!

Because the are 9 Win95 Clients running, but only 8 TSCAL's and 1 unused 
Windows 2000 prof. Licence the notebook gets a temporary license I have do 
delete hkey_local_machine/software/microsoft/ms-licensing every 90 days to 
get the notbook running. (another method is to change the machines name.)

There are no problems with the second notebook, because Windows 2000 
professional is running with its build in license, and not using one of the 8 
TSCAL's.

Now I want replace the Win95 Clients and the Win95 Notebook with 9 PXES 
Clients, with equal hardware.
I have tested my 'new' clients (Compac Deskpro EN, with onboard Intel LAN, ATI 
graphics, 300MHz PII) which were running fine.
But for all Clients a temporary license is issued. And because of dhcp the 9 
Compac's get 12 different temporary licenses now !
So after 90 day's I will get into big trouble.

Is ist possible to reconfigure the W2K Server to get my configuration running 
without trouble? Perhaps using the per Client license model?

Any hint's are very very welcome :)

Henning 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBFySlu1M3lPi4uIERAsB+AKCTMVHavyzeFb7oIYhxKymittdd7QCfSNt4
xDuKIyMtIi/IhI57W7TQgdU=
=IIP3
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com