Your best bet for all licensing questions is to talk to a reseller, since
there may be nuances to your particular situation that change the "stock"
answer to this question. But as a rule, it goes like this:
Per server: only allows X concurrent connections to one server at a time,
needs to be purchased for each individual server. So if you have ServerA
configured as per-server with 50 CALs, you can have up to 50 concurrent
connections to that server. If jsmith accesses the server from two separate
devices simultaneously, she's taking up 2 CALs and you have 48 left.
Per server is good in small environments with only a few servers, because it
does the job of license enforcement for you - once you reach the maximum
concurrent licensed connections on a server, nobody else will be able to
connect to that server. However, you'll need to maintain separate CALs for
each server that clients need to connect to. So if jsmith needs to access a
file on SERVERA and SERVERB, she'll be taking up 2 CALs even though she's
only working from one device - one CAL on ServerA, one CAL on ServerB.
If you move to per-device/user licensing, jsmith would only need one CAL to
access resources on both SERVERA and SERVERB.
--
Laura E. Hunter
Microsoft MVP - Windows Server Networking
Author: _Active Directory Consultant's Field Guide_
(http://tinyurl.com/7f8ll)
All information provided "AS-IS", no warranties expressed or implied.
Replies to newsgroup only.
"Gary Land" <gllxxx@2bellsouth.net> wrote in message
news:OpyMuKlrFHA.3836@TK2MSFTNGP12.phx.gbl...