Licensing 2k and 2k3

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We had device cals for 2000 in an NT Domain. We up graded the Terminal servers to 2003 and with the XP licensing transition we added the User cals to the server. NONE of the licenses are being logged correctly. It appears that I have to remove the 2000 Tscals. The problem is that license tool doesn’t allow you to do this. What should I do

Thanks

Joe
 
Both your TS and your LS run 2003, correct?
I don't think that you will have to remove the W2K TS CALs. The
problem is that your W2K TS CALs can't be used, since they are not
valid to connect to a 2003 TS, and your 2003 TS CALs can't be used
because they are Per User CALs and your TS (yes, TS, not LS!) is
probably in the default Per Device licensing mode. That means that
your TS never "sees" the 2003 User CALs on your LS.

The solution is simple: You can change this from Administrative
Tools - Terminal Services Configuration - Server Settings

You might want to read this article as well, it explains why you
have to manage User CALs manually:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

=?Utf-8?B?Sm9lLlNhcmNvbmVAdW5pdGVkd2F0ZXIuY29t?=
 
What I did is, I backup the License DB. This put the sever back to a clean license install. I re actived the License 2k3 per user. I changed the server mode from Device to User on all the servers. I still getting a temp license. The only I have in LS is Built in, Temp and User 2k3 licenses. Why aren't I getting a count on the User License? Only the Temp I get a count

Thanks

Joe

----- Vera Noest [MVP] wrote: ----

Both your TS and your LS run 2003, correct
I don't think that you will have to remove the W2K TS CALs. The
problem is that your W2K TS CALs can't be used, since they are not
valid to connect to a 2003 TS, and your 2003 TS CALs can't be used
because they are Per User CALs and your TS (yes, TS, not LS!) is
probably in the default Per Device licensing mode. That means that
your TS never "sees" the 2003 User CALs on your LS

The solution is simple: You can change this from Administrative
Tools - Terminal Services Configuration - Server Setting

You might want to read this article as well, it explains why you
have to manage User CALs manually

822134 - The Function of Terminal Server CALs in Windows Server
200
http://support.microsoft.com/?kbid=82213

--
Vera Noes
MCSE, CCEA, Microsoft MVP - Terminal Serve
http://hem.fyristorg.com/vera/I
--- please respond in newsgroup --

=?Utf-8?B?Sm9lLlNhcmNvbmVAdW5pdGVkd2F0ZXIuY29t?
 
Did you read KB article 822134? It explains why the User Licenses
are not counted down in License Manager.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

=?Utf-8?B?Sm9lLnNhcmNvbmVAdW5pdGVkd2F0ZXIuY29t?=
 
Several possibilities come to mind:

* you can control which users have permission to access the TS and
make sure that you have as many licenses as permitted users
* you can check the security tab of EventLog to check who logged on
the TS, provided you have auditing of security events enabled
* you can create a logfile by putting a line in the login script that
users run when accessing your TS:
echo %username% %clientname% %date% %time% >> logon.log
 
Back
Top