Per User TS CAL Weirdness.....

[James Crane]

Hello,

I'm hoping someone can help me with this Windows 2003 Server TS CAL
issue..... I have the following setup :

Windows 2000 SBS Server acting as a Domain Controller.
Windows Server 2003 acting as a member server in the SBS domain.
Terminal Services Licensing is installed and activated on the Windows
Server 2003 Terminal Server. I have 4 Windows Server 2003 Per User
CALs installed on terminal server and the terminal server is
configured for Per User mode. When I connect my four users to the
server they connect without any issues. However, when I look in the
Terminal Services Licensing snap-in it shows 4 Total licenses with 4
Available and 0 Issued. Any idea why the terminal server is not
issuing these per user licenses? I checked the event logs and they
are completely clean. Does it only start issuing the per user
licenses once the grace period for the server has expired???

Any help is greatly appreciated.....

Thanks in advance !!

 

[Joe Zalewski]

James:

The TS CALs need to be installed on the Primary Domain Controller.
2003 TS CALs are backwards compatible. Hope this helps!

If you need additional Licenses try
http://www.thinclientpricing.com/microsoft.asp?MicrosoftCat=License

 

[Vera Noest [MVP]]

What you see is, unfortunately, expected behaviour.
Per User TS CALs were build-in to the OS in a very late stage.
The 2003 TS Licensing server cannot handle them correctly, so
currently Per User CALs are unmanaged.
This means that when a TS server is set to accept User CALs it
will look to the license server to make sure that one is available
but it will not be decremented from the database.
It is your responsibility to have a valid User CAL for every user
that uses the terminal server.

Hope this clarifies the situation.

 

[James Crane]

Joe,

A terminal server running Windows Server 2003 does not communicate
with a terminal server licensing server running Windows 2000. My
domain controller is running Windows 2000 SBS..... I believe my
Terminal Server Licensing is running on the correct box (the Windows
2003 member server).......