RE: Which licensing server I am using?
Your 2003 TS is still in it's grace period (which lasts 120 days on
2003). A 2003 TS cannot use a W2K TS Licensing Server, so it's not
using that one, and the 2003 LS which you installed isn't activated
yet.
Check the EventLog on the 2003 TS, it might contain informational
messages stating that it is in it's grace period. But I'm not 100%
sure that there will be any, it's possible that these warnings only
appear in the EventLog when you only have 14 days left of the grace
period.
Anyway, assuming you want to fix your licensing situation, activate
the 2003 LS and install 2003 TS CALs on it.
I assume that you know that *all* clients who connect to this
server need a purchased 2003 TS CAL (as well as a normal 2003
server CAL)?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?SmFuZQ==?= <Jane@discussions.microsoft.com> wrote on 05
nov 2007 in microsoft.public.windows.terminal_services:
> Thanks for your great help.
>
> Is there a way to tell I am using temporary CALs to connect to
> the new windows 2003 TS since I have one windows 2000 licensing
> server activated?
>> If I were you i wouldn't make the DC licese server for the
>> termianl server. I would rather use the Terminal Server itself
>> to be its own license server, but if you have any special
>> reason go for it.
> Thanks. I am going to use the TS as my licensing server. Any
> reason?
>
> Thank you.
>
> "andrew" wrote:
>
>> Ok, I hope you are talking about Terminal Server CAL's. As far
>> as I know once you have installed Windows 2003 Terminal Server
>> it provides 90 day limited CAL's. I believe this is why you
>> were able to log in.
>>
>> As, for license server you can find out by going to
>> Administrative Tool and then click on Terminal Server
>> Licensing. You will be able to see here whether it is using any
>> license server.
>>
>> If I were you i wouldn't make the DC licese server for the
>> termianl server. I would rather use the Terminal Server itself
>> to be its own license server, but if you have any special
>> reason go for it.
>>
>> Also when you setup licese server it is suggested that you make
>> changes to the register so that the change is parmenent. But
>> there are 2 other methods one is by going to Termials server
>> Licensing and then right clik to connect the license server and
>> another is going to Termina Server configuration then Server
>> setting. From there you will see "License Server Discovery
>> Mode" click that to open and then put the IP address of the
>> License Server. This is doing the same as changing the registy.
>>
>> See the lick below for more information:
>>
>> http://www.microsoft.com/windowsserver2003/techinfo/overview/qui
>> ckstart.mspx
>>
>> http://technet2.microsoft.com/windowsserver/en/library/b6c02871-
>> 7bef-4e26-9aab-48730511c1261033.mspx?mfr=true "Jane" wrote:
>>
>> Thanks
>>
>> > Hi all,
>> >
>> > I still have terminal licensing server installed on the
>> > windows 2000 DC. Recently, I installed one new windows 2003
>> > terminal server. Also, I install the terminal licensing
>> > server on one windows 2003 domain controller but I did not
>> > activate it yet. When I connect to the new Windows 2003
>> > terminal server, I have no
>> > problem and I did not get the terpporary licensing warning.
>> > Is this normal? Can you tell me which licensing server I am
>> > using to to connect to the new windows 2003 terminal server
>> > since the new 2003 clicening server is not activated?
>> >
>> > Thank you.