Re: CAL Confusion

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Richard Steele (RichardSteele_at_discussions.microsoft.com)
Date: 12/10/04 

Date: Fri, 10 Dec 2004 13:23:02 -0800

So, just to be clear. We should get the CALs for users and not worry about it
as long as we have only 15 users. There is nothing we need to do in SBS to
deactivate users to free up CALs. In effect it will allow up to 15
concurrent users, though there are 30 users set up in SBS (as the historical
data is kept.).

"Javier Gomez [SBS MVP]" wrote:

> > We have SBS 4.5 with 15 client licenses. We are upgrading to SBS 2003 soon
> > and need to purchase upgrade CALs and are trying to determine which type
> > to
> > use.
>
> Welcome to the club :-)
>
> > I believe the way our current licenses work is that they allow for up to
> > 15
> > concurrent users. Perhaps I'm wrong, but I have setup many more users than
> > 15.
>
> Licensing has never been by concurrent usage, not in this version or any
> other version. You can create as many users as you want, but in SBS2k (and I
> believe in 4.x too) you were basically licensed PER SEAT (which is now Per
> Device).
>
> > However I have read that the SBS 2003 User Cals allow for 15 "named"
> > users,
> > meaning the CAL is somehow tied to specific users.
>
> If you buy Device CALs then its the devices that count. If you buy 15 User
> CALs then only 15 persons can access the server at all (not concurrently).
> In either case you can create as many AD accounts as you like (i.e. an user
> can have more than one account)... but the CAL belongs to a person. Remember
> this is a *legal* requirement, not a technical one... the server doesn't
> really care how you assign them. Bottomline is that if you comply legally...
> you wouldn't have to worry about SBS blocking the logon.
>
> > I don't think I want the Device Cals as we have several staff members who
> > work at home and I want to give them remote access to our server.
>
> Fair enough.
>
> > Also, we have part time workers coming in and out of our business all of
> > the
> > time. How do we deal with this?
>
> If you have a cal for them... then there is no problem. You can legally
> reassign a cal in a permanent or semi-permanent basis according to the EULA.
>
> --
> Javier [SBS MVP]
> www.msmvps.com/javier
> << SBS ROCKS!!! >>
>
>
>

Relevant Pages

  • Re: Licensing limitation
    ... Javier [SBS MVP] ... > then you could just go by Device CALs instead. ... >>> SBS licensing does not use a concurrent connection model - never has. ...
    (microsoft.public.windows.server.sbs)
  • Re: Confused about 75 user/device/account (?) limit
    ... Things have become a lot clearer now and the likeliness of purchasing SBS has increased like a zillion times. ... If I have understood you correctly, the following would be true: suppose we would purchase 10 Device CALs and 0 User CALs, it would mean that OWA cannot be used from outside the building, right? ...
    (microsoft.public.windows.server.sbs)
  • Re: what to do with local and remote users for a SBS Network?
    ... Device CALs would be more ... And the first 5 CALs that come with SBS can be assigned as either User, ... as Device CALs and then buy User CALs for the rest of your people. ... >>> decided to use his laptop, he could RWW into his desktop. ...
    (microsoft.public.windows.server.sbs)
  • Re: silly questions about CALs
    ... If you have 15 Device CALs any number of people may use the system from your ... If you have a mix of Device and User CALs any number of users may access SBS ... the resources through computers in our company; ...
    (microsoft.public.windows.server.sbs)
  • Re: How many Cals do I need?
    ... etc.) then USER CALs are the appropriate license type for K2. ... server from a single computer, such as on a shop floor. ... Mac accesses and authenticates to the services on SBS from his office ... or 4 DEVICE CALs. ...
    (microsoft.public.exchange.setup)