Can I Change 2003 TS Licensing to Per-Server?

[Kiehlster]

I recently set up a windows 2003 standard edition server but have noticed that every time anyone connects to it via RDC, the previous user gets kicked off. This is obviously because it's running on the single temporary license. We bought the W2k3 with a 5-client access license, but if I punch in the ONE serial number that came with W2k3 (which apparently is the w2k3 product key) it does not accept it. I don't have a list of 5 CAL licenses or I wouldn't be complaining.

I read on here that the server can be in per-user, per-device or per-server mode, but in Terminal Services Configuration I can only switch between per-device and per-user. I don't think I ever received a slip with 5 CAL codes or anything. I just have the 'getting started' manual, a microsoft subsidaries sheet, a cd case with product key and w2k3 cd, and a 5-client CAL agreement. I dont know how I'm suppose to pull 5 CAL codes of of the air, but the more I work on this, the more I hate microsoft licensing.

Can anyone either tell me (1) how to find my CAL license codes and/or (2) configure the server to use per-server terminal services licensing? This is kind of urgent because I am guessing the the temporary license is going to expire on me.

Steve Kiehl
Web Page Designer - Nanovox Productions
Fantasy Artist - Zeadi

 

[mlichstein]

Windows Server doesn't come with Terminal Server licenses. The 5 CALs are Windows licenses, which are separate from TS licenses.

You need to purchase either per-user or per-device TS CALs and set the TS license server to the appropriate mode.

 

[Kiehlster]

Then what on earth are Windows CALs??? I can't RDC into my server with more than one user? Why does it say "Number of Concurrent Connections: 5" in the Licensing" admin tool? What kind of connections are they talking about? Why can I and two other people RDC into our 2000 servers without spending an extra $800? Wow does this suck.

 

[Kiehlster]

Okay, nevermind. I figured out how to get it out of "application mode" as they call it. Looks like you have to pay for licenses when you set up terminal services in application mode. If you don't install terminal services, you can go into My Computer > Properties > Remote and enable remote access. Then it's in "Administration Mode". In that case you can have at least 2 people connected to the server at once. And that's all I really wanted. The server is set up as a web application server, so clients access it by the web. So we only needed the terminal services to administrate it (which in most cases is only one or two people at once. Using application mode I could only allow one person at a time and that person would get kicked whenever someone else tried to log in. Now it should say that there are too many people on if someone tries to log in when all the slots are filled. But now at least I don't need to deal with the pains of buying CAL licenses. I suspect that the server will allow up to 5 users connected at once using the Windows CALs, but I don't understand what those are, so I guess I'll find out later when too many people are on it.

 

[mlichstein]

Windows client access licensing:

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/caloverview.mspx

Windows Terminal Server licensing:

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2003.mspx