L
Lars Hermansen
Hi
I have a costumer with a w2k-server (sp4) running terminal server, and 12
clients running w2k-pro/xp-pro. The server is installed with 13 Windows
server CAL's in per server mode. The client both logon to the domain, using
shares and printers, and are running terminal server sessions.
The problem is that they quite often cannot connect to the terminal server.
In the app. log there is an event 201 from LicenseSevice - No License was
available for user X using product termservice 5.0. In the Licensing program
it says Windows server : Per server purchased - 13 Per server reached - 8.
Restarting the License logging service solves the problem for a while.
The Danish sales support has told us that we only need one CAL pr. PC even
though the user uses both shares and terminal server.
Would it perhaps help to change the server license to pr.seat?
Thank you for Your help
Lars
I have a costumer with a w2k-server (sp4) running terminal server, and 12
clients running w2k-pro/xp-pro. The server is installed with 13 Windows
server CAL's in per server mode. The client both logon to the domain, using
shares and printers, and are running terminal server sessions.
The problem is that they quite often cannot connect to the terminal server.
In the app. log there is an event 201 from LicenseSevice - No License was
available for user X using product termservice 5.0. In the Licensing program
it says Windows server : Per server purchased - 13 Per server reached - 8.
Restarting the License logging service solves the problem for a while.
The Danish sales support has told us that we only need one CAL pr. PC even
though the user uses both shares and terminal server.
Would it perhaps help to change the server license to pr.seat?
Thank you for Your help
Lars