Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
License 1
- Thread starter seanie69
- Start date
-
1
- #2
NickFerrar
MIS
If you mean 'per seat' or 'per server' it's basically a choice between licensing each PC (per seat) so that once licensed they can connect to any Windows Server on your network or licensing the servers individually for a certain number of concurrent users (per server) which means users on your network can connect to that server up to the number of licences you purchased (if you licence it for 50 users and user 51 tries to connect they'll get denied access).
It's generally better to go 'per seat' if you have 2 or more servers that most people need to connect to. That way you only need to buy a licence to cover each person.
If you only have a single server or a couple of servers that only a few people need to connect to then 'per server' might be cheaper as not everyone in your company may need a licence.
As an example say you had 2 servers A and B and 100 employees who each needed to access A and B regularly. You would go for per seat as then you would need to buy 100 licences (1 for each person), if you went for per server you would need to buy 200 licences (100 for each server) in order to support all 100 people connecting to either server at any time.
If in the same scenario though 20 people max need to connect to server A and 30 people max need to connect to server B at any one time then per server would be cheaper as you would only need to buy 50 licences (20 for A and 30 for B).
Trouble is if you go per server then add another server in the future it could end up being cheaper to go per seat after all so I think most companies generally go per seat unless they're sure they won't be adding additional servers.
It's generally better to go 'per seat' if you have 2 or more servers that most people need to connect to. That way you only need to buy a licence to cover each person.
If you only have a single server or a couple of servers that only a few people need to connect to then 'per server' might be cheaper as not everyone in your company may need a licence.
As an example say you had 2 servers A and B and 100 employees who each needed to access A and B regularly. You would go for per seat as then you would need to buy 100 licences (1 for each person), if you went for per server you would need to buy 200 licences (100 for each server) in order to support all 100 people connecting to either server at any time.
If in the same scenario though 20 people max need to connect to server A and 30 people max need to connect to server B at any one time then per server would be cheaper as you would only need to buy 50 licences (20 for A and 30 for B).
Trouble is if you go per server then add another server in the future it could end up being cheaper to go per seat after all so I think most companies generally go per seat unless they're sure they won't be adding additional servers.
- Thread starter
- #3
ok im getting a better understanding
i have server 2003 installed and its in per server mode at the moment, from what i understand it come with 5 cals and only five people can use this server for there files before the sixth person gets access denied.
My question is my other server is 2000 so the cals are not able to be used between the two machines.
When i click on add licneses to per server mode it says service not running ???
i have server 2003 installed and its in per server mode at the moment, from what i understand it come with 5 cals and only five people can use this server for there files before the sixth person gets access denied.
My question is my other server is 2000 so the cals are not able to be used between the two machines.
When i click on add licneses to per server mode it says service not running ???
- Status
Similar threads
