Another Licensing Question
Ed A.
if I have purchase a
WIN NT Server with 5 Clients
and a
WIN NT Server with 10 Clients
and a
WIN NT Server with 25 Clients
and I run the servers with the PER SEAT licensing modell with lets say a
max. of 40 WIN NT Workstations do I run into any licensing problems
accessing all three servers with each server opening up to max. 40
connections ??
Further if I want to add a WIN NT Terminal Server lets say with 5 Clients
and also the PER SEAT modell would I have to purchase more licences for the
TERM Server ??
TIA,
Ed
Tom Capote (MCSE)
server
and each seat, in your case 40 licenses for each server. If you have it set
up
Per Server, you need to only have the MAX number of connections that each
server
will encounter, ex.
Server 1 - Only 10 of your 40 people max will access it (only needs 10
licenses)
Server 2 - Only 25 of your 40 people will access it at one time (25
licenses)
etc...
Per Seat and Per Server
PER SERVER Client Licensing Mode
The server is licensed for a maximum number of clients that will connect to
the server at one time. Any client on the network can connect to the server.
The number of concurrent users must be entered in the 'concurrent
connections' box. This licensing mode is useful if only a subset of a group
of computers can access the server at a time. The Per Server License mode
can be upgraded once, at no charge, to the Per Seat License mode.
PER SEAT Client Licensing Mode
A license is required for each server and for each client (seat) on the
network. To add a client, a client license must be purchased. To add a
server, a server license must be purchased. The client computer may access
any number of servers.
How to: Determine if server uses Per Seat or Per Server licensing mode.
Solution:
Open License Manager, and select the domain to view the licensing
information. Click the 'Products View' tab.
1) Open License Manager.
2) Select the 'License' menu and select 'Select Domain'.
3) Select the desired domain from the 'Select Domain' list box, and click
'OK'.
4) Click 'Products View'.
5) Examine the information in the 'Per Seat Purchased' and 'Per Server
Purchased' columns to determine the licensing mode of the selected domain.
--
Tom Capote
-------------------------------------------
Microsoft Certified Systems Engineer (MCSE)
Compaq Accredited Systems Engineer (ASE)
Microsoft Backoffice MVP - Windows NT
A+ Certified Technician
Ed A. <e...@sunnycars.de> wrote in message
news:#zYrszK5#GA....@cppssbbsa02.microsoft.com...
Ed A.
I have read your standard reply many times in this forum, therefore I titled
this msg as *Another* Licensing Question :-)
Ok, here is what I do not understand:
Your example explained the Per Server Licensing Modell:
Server 1 with 5 Clients > max connections 5 at a time ( concurrent users )
even with 100 Workstations
Server 2 with 10 Clients > max connections 10 at a time even with 100
Workstations
Server 3 with 25 Clients > max connections 25 at a time even with 100 Wks
and so on
Therefore if I add a new server
Server 4 with 5 Clients > max concurrent users is 5 even with a 100
Workstations in the net
I guess I have understood the Per Server Licensing Modell.... right ?!
Ok... I will continue with the PER SEAT Licensing Modell:
Server 1 > max connections 40 at a time even with 100 WIN NT Wks
Server 2 > max connections 40 at a time even with 100 WIN NT Wks
Server 3 > max connections 40 at a time even with 100 WIN NT Wks
since I have purchased 3 WIN NT Packages ( one including 5, the other 10 and
the other package 25 clients access licenses ) >>>> I have 3 Server Licenses
and 40 Client Licenses, right ?!
Ok now I want to add a new server ... since the packages are always (?)
comming with min of 5 Client Access Licenses I would get following result:
Server 1 > max 45 concurrent users
Server 2 > max 45 concurrent users
Server 3 > max 45 concurrent users
Server 4 > max 45 concurrent users
Right ?!
If I have a new workstation ( lets say Nr. 46 ) I would only have to
purchase a client access license ... right ?
Now .... you wrote following in your msg:
"well, if you have it set up as Per Seat, you MUST have a license for each
server and each seat, in your case 40 licenses for each server."
Therefore buying a new server I would have to purchase one server license
*and* the number of client licenses I use on the network ( e.g. 40 if the
other servers are PER SEAT and I have 40 Seats ( client access licenses) )
.....
***BUT*** now it is getting confusing ... further you wrote:
"PER SEAT Client Licensing Mode
...
To add a client, a client license must be purchased. To add a server, a
server license must be purchased. The client computer may access any number
of servers."
This differs to your first statement....
Are you confused by now ??!?! :-)
TIA,
Ed
Tom Capote (MCSE)
Per server may be a cheaper way to go;
If you have 100 computers on 1 NT Server, 50 people
work 8am to 5pm and the other 50 work 6pm to 2am.
In the Per Server model, you really only need 50 client licenses,
because only 50 users max will work on the NT server at any given
time, thus you only need 50 CAL's (Client Access Licenses)
In a Per Seat model, you would need 100 licenses, period.
Even if no more than 50 people access it at any given time, 100
people can potentially access it, you physically have 100 seats connected
on your network that have access to your NT Server.
One would ask, why go to per seat? Well, let's say you have
100 computers on your network, they all work 9am to 5pm,
all people access the server, maybe all at the same time, maybe not.
You want to be in compliance with MS licensing terms, so to be safe,
you go the per seat model because it's easy to track, easy to buy and easy
to show the software police when you get audited!
Hope this helps?
--
Tom Capote
-------------------------------------------
Microsoft Certified Systems Engineer (MCSE)
Compaq Accredited Systems Engineer (ASE)
Microsoft Backoffice MVP - Windows NT
A+ Certified Technician
Ed A. <e...@sunnycars.de> wrote in message
news:#CbsVWX5#GA....@cppssbbsa02.microsoft.com...
Ed A.
Well, I am confused, too :-)
I will not further bug you .... tomorrow I will call MS and talk to them in
hope that they can help me out.
Thanks for your input anyway.
Ed