Windows Cal's on terminal server

[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

 

[Charles]

1: is your server is activate?
2: Are you ruuning in Administrative mode or Application
Mode?
3: Do you have the TS License service install?

If you are in Application mode, your server must be
activated before 90 days. You must have the TS License
service installed and running.

Windows 2000 or XP already have a TS CAL so you can
connect to the TS without having to purchase new TS CAL.


Charles

 

[Bob Qin [MSFT]]

Hi Lars,

From the information you provided, it seems that license/license server
have not been installed correctly.

With Microsoft Windows 2000 Terminal Services licensing, if a client device
is running the most recent version of the Windows desktop operating system,
it does not have to have a TS CAL to satisfy the licensing requirement,
they will use the built-in license.

After you install Terminal Services License Server, please activate it and
check if problem is resolved.

For more information, please refer to:

306622 HOW TO: Activate a License Server by Using Terminal Services
Licensing
http://support.microsoft.com/?id=306622

306578 HOW TO: Deactivate or Reactivate a License Server Using Terminal
http://support.microsoft.com/?id=306578

290712 Windows 2000 Terminal Services Licensing Frequently Asked Questions
http://support.microsoft.com/?id=290712

810728 White Paper: Microsoft Windows 2000 Terminal Services Licensing
http://support.microsoft.com/?id=810728

Have a nice day.

Regards,
Bob Qin
Product Support Services
Microsoft Corporation

Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Lars Hermansen]

Hi Bob -

I'm sorry i posted my question twice, but somehow the first post never left
my outbox, and i tried again.

The terminal services license server is running and activated, and the
terminal services licensing tells me that i have issued 12 "existing windows
2000 license" clients with no errors.

I think my problem is something about the windows server license and not the
terminal server license. The windows server license calculates the wrong
amount in use in the status. When 7 clients login i get the warning that its
nearly out of licenses and user number 8 cannot login to the terminal
services. The overview still tells me that i have purchased 13 windows
server licenses and i have reached 7 or 8.

Vera Noest made a reply to my other post saying that per seat licensing will
resolve the problem. I'll try that and return here with status later

Thanks for you help
Lars

 

[Guest]

The License Logging Service is absolutely useless and no program (that I'm aware of) is dependent on it. Go to the service, stop & disable it. That will take one possibility out of the equation.

The most likely problem is unreachable TSLS (Terminal Services License Service). So long as:

a. You're Running Windows 2000 Server Terminal Services (Application Mode)
b. Have an Activated TSLS on a DC or the TS (if it is not part of an AD Domain).
c. Client OS are Windows 2000 or XP Pro
d. TS can contact the TSLS

It should work. If A,B,C & D are correct and you still have this problem then something else is a miss.

Patrick Rouse
Microsoft MVP - Terminal Server
http://www.patrickrouse.com/ts.htm