Windows 2003 Terminal Server Licensing

[Enigma256]

Well I have a 2003 Server (Enterprise Edition) installed and promoted it to be a Domain Controller. The Computer name is r01msedc and netbios name is SSMSE. I have two machines, both of which are in the domain SSDMSE. One is BATTLE and the other is CASTLE. I am using Castle as the the License Server. So on the Castle machine, I log in as the Administrator and Log on to as SSDMSE, since I chose the option of Enterprise instead of your domain or workgroup.I activated the License Server and installed CAL's from Microsoft. and log off the machine. Than I log on to the Battle, and go into Licensing Manager, it does not find any license servers at all. So I go back into Castle ( Administrator , Castle ( Local Computer ), go into license Manager it does not find any license servers. If I log off and log back on to ssdmse domain in the castle machine it finds the license server. I hope I made sense. I have also added the DefaultLicenseServer key in the registry as well. Does anyone know a fix or ideas I would really apreciate it. Thanks

 

[davidwilson11]

I take it from what you say you are using per server licensing, have you tried the one time chang over to per seat licensing. As i read it from the book by Mark Minansi you install the CAL on one server it is only licensing for that particular server. To save money what you should is use per seat licensing. have you already tried? then you should be able to track them. hope that helps p.s how many systems are you licensing?

 

[davidwilson11]

sorry i made a mistake that was not the correct answer, i was away wandering with 2003 licensing and not terminal server licenses. let me know how you get on with it.

 

[GaZZaW]

Hello,

Are all your machines 2003 or just the DC ?
If just the DC then you must run the licensing server from the 2003 box.

Gary

 

[Enigma256]

I forgot to mention that I tried running the license server from the DC as well, I get the same problem. No other machines sees the terminal server licenses only the machine that has it.

 

[davidwilson11]

I am having the same problem,

I cant get my TS 2003 member server to issue the TS CALS. Not sure how on earth to fix this problem.

David

 

[WillShakespeare]

LOL! I'm having this too! If anyone comes up with a solution, let me know. The workaround I have is that I set the configuration to Per Device, and they can log in temporarily, until I get the problem sorted. The Per Device is the standard unlimited 120 day (oxymoron?) grace period for TS on my W2K3 server.

Will

 

[WillShakespeare]

Incidentally, what error messages are you people getting?

Will

 

[Enigma256]

OKay guys, I am still having the problem. I even tried reinstalling the OS and still no fix. I have found this link :

http://www.tricerat.com/ebook/

which is free of course and I followed the instructions to a tee and still the same problem. If you guys read the above link and it works for you please be kind enough to email me at ngeorge@techie.com and tell what you did to fix it. I would really appreciate it. I have tried everything I can think reduced the name of the domain, put the TS licensing on a dff server with in the same subnet, nothing. Thanks

 

[WillShakespeare]

I found this link in one of the other threads... but in following it, I am not sure what should be at the very end of the Registry Key!
It might help, if the guy who posted it will get back to me on this issue!

http://support.microsoft.com/?id=279561

Will

 

[Enigma256]

Will I just replied to you thread with the answer to what you are looking for. Thanks for the link, this is regedit is for machines running windows 2000 machines only will not work for Windows 2003 ( That is what I am guessing, since I have tried it and not worked )

 

[WillShakespeare]

As Enigma knows, I have made solid progress with the link I gave above! But the licensing manager still shows 0 User CALs issued, even though I can now access using Per User.

Will

 

[Enigma256]

Will Where do you change the access to Per User?

 

[WillShakespeare]

In Start - All Programs - Admin Tools - Terminal Server Configuration

hth,

Will