Licenses

[Steve1962]

We have three servers, all Windows 2000 server. 250 clients attach to all three servers. Since taking over this job, I've noticed the licensing mode is set to per server mode on all three servers. (250 concurrent connections)
Server A is DC, Server B is DC/DNS, Server C is member server. Is it better to have it set to 'Per Seat'? and would I need to change it on all three servers?
Will I need to do anything else after changing it to per seat, or will all clients (w2000) be able to connect without a problem?
When (if it get's changed to per seat) I add new CALS, do I just add them to the main DC, or will they need adding to all three servers?

Sorry for all the questions. Hope you can help

 

[Steve1962]

Any help appreciated

 

[AlexIT]

I have had networks installed both ways, no matter what you always get "Out of Licenses" errors recorded in the Event Viewer...leave your servers in the default per server mode. Now go to license management and tell the primary server you have 99,999 licenses for everything. This will reduce (but not eliminate) the number of "out of licenses" errors you have. If the BSA shows up you can show them the purchase orders or the MOLP certificate to prove that you have licenses for the number of users in your domain (you better have the same number of licenses anyway!)

I don't know why M$ keeps including the License Manager in their servers when it doesn't work...

Alex

 

[Davetoo]

The License service for servers is just to help you administer your licenses. It won't prevent any user from accessing the servers.

You can do what Alex said and just not use it as a reminder for you, or, with so many users, switch to per seat, make sure you have a CAL for each computer in your organization, setup that number of licenses and keep using the service as a reminder for you.

Also, you can just disable the Licensing Service on your servers, that will work as well.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[Seaspray0]

Once you switch to per seat, you can't switch back.

Per connection means you need a license for every connection to that server and each server needs licenses for the number of connections. This is good for lots of users, a small number of servers, and users working on shifts (you only need to license for the maximum number of connections you expect, not every client).

Per seat is good for a large ratio of servers to clients and where the number of connections is a high percent of the number of clients (i.e. single shift, almost everyone connects). You need one license for every client reguardless of the number of servers they connect to.

A client with a client license can connect to any server and the server connected doesn't require a connection licenses for it. A server with connection licenses can accept any client (no client license). Clients without client licenses are not supposed to connect to servers without connection licenses (no license on either end). Most companies will either be all per seat client licensed or have all the servers with connection licenses. It depends on which is cheaper.

If in doubt about any licensing, go by what microsoft say since their word is law concerning licensing or be willing to pay the penalty when audited by the men in black.

 

[jrIStech]

yeah,
when i installed my win2kserver i made sure i chose the per seat because it made my life much more easier

 

[Steve1962]

Thanks for the advice
To make it legal, I think I need to switch it to 'Per Seat'.
Would I need to do this on all three servers? And would I then have to tell it that I have 250 clients.
I presume this then means that each new machine I add to the domain requires only one license (CAL)?

Thanks.

 

[Davetoo]

If all 250 users are accessing each of the servers, then yes, convert all three servers to per seat (keeping in mind you can never convert back to per server), make sure you have 250 CAL's, and you're all legal. If a new computer is added to the network, it will only need one CAL in total, not one CAL per server it will access.

I usually have about 5-10% more licenses than computers, so I don't have to worry whenever a new system is added. I audit the licenses twice a year to make sure we stay legal.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.