Re: licensing

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Geoff (geoffcurrie_at_hotmail.com)
Date: 05/28/04 

Date: Fri, 28 May 2004 16:41:54 +0800

Thanks for your reply

I find licensing for sbs the most confusing aspect of sbs. I have always
thought of sbs2000 as concurrent from a tech perspective as the only
licensing management tool are "help about" to see the number of quote
"licenses" and using net session to see how many "devices" are connected and
licenses are applied to the server and not to any client pc. It really is
smoke and mirrors and a device seems to give its license back each time its
user logs off. This leads to the question of how do you legally define what
device holds a license at anyone time?

>From what you have mentioned I agree per user seems to be the way to go for
my 2003 scenario. Just so I understand can you tell me if this scenario is
correct,

Buy sbs2003 and 50 licenses ( well 45 + the 5cals that ship wth the
product)as per user and load them on the server

5 staff leave and are replaced by 5 new staff, the new staff are able to
logon and consume a per user license no admin effort beyond creating the new
accounts and removing the old ones

User 1 goes on leave for 4 months and as a good admin I don't give user1's
username and password to the temp but create an account called temp.
    1 the temp will the temp be able to logon
    2 I'm violating my license agreement as there are 51 users and 50 per
user licenses

2 users job share and work part time. The both use the same office and pc
but never at the same time. It seems to make sense to buy a per device
license for the pc they use as they just use that one pc and never use
outlook web access or any other server features requiring authentication
away from that pc . If one of them log on to another machine I assume it
will be successful and they will consume a per user license as you mention
that there is no mapping of user to a specific license and potentially stop
user number 50 from logging on.

Your response is appreciated as searching through MS FAQ's and product doco
hasn't really clarified the scenarios above

Cheers

Geoff

"Javier Gomez [SBS MVP]" <javier_gomez@remove.this.engineer.com> wrote in
message news:ewmC5uFREHA.2032@TK2MSFTNGP11.phx.gbl...
> First of all-> Legally SBS2k is *not* licensed per concurrent connections,
> it is Per Device. In SBS2k3 you have the option of Per Device or Per User.
>
> Every user or device need a distict CAL. If you have 60 users accessing
the
> server (via OWA, RWW, file/print, Outlook or whatever) using 75 devices->
> You need either 60 User CALs, 75 Device CALs or a combination of both. The
> user or the device must have a CAL to access an SBS resource... it doesn't
> matter if the connections are conccurent or not.
>
> Your case looks like a perfect candidate for User CALs (since employees
use
> more than one device to access the server, i.e. from home).
>
> > Also we have quite a bit of staff turnover, leave, redeployment so using
> the
> > per user would be high on the admin effort
>
> There is no "admin effort"... the user/device CAL are LEGAL concepts. The
> server doesn't know about this... in other words-> There is no place on
the
> SBS2k3 box where you say X licenses belongs to Y user. The way I see it is
> if you have an equal or larger number of USER CALS than actual users (not
AD
> accounts)... the you are ok.
>
> --
> Javier [SBS MVP]
>
> << SBS ROCKS !!! >>
>
> "Geoff" <geoffcurrie@hotmail.com> wrote in message
> news:OKWajQFREHA.1624@TK2MSFTNGP09.phx.gbl...
> > Currently I have a sbs 2000 server with 45 client licenses. As the
growth
> of
> > the company has doubled expection we shall soon exceed 50 users. I'm
> > upgrading to sbs2003 and with the new license model it seems I will need
a
> > lot more licenses. Currently we have approx 60 users but no more than
> 40ish
> > are logged on at any one time. With concurrent licensing (SBS2000) the
> only
> > issue we have is reaching 50 concurrent users. I could use per device
> > licenses (for sbs2003) but it seems Outlook web access will not
> authenticate
> > users who don't have a user license. Is this correct?? To add further to
> the
> > issue some staff have a pc at home and a pc at work.
> > Also we have quite a bit of staff turnover, leave, redeployment so using
> the
> > per user would be high on the admin effort. Can anyone tell me from
> > experience how effective /practical it is changing user account
licensing
> > on the per user model.
> >
> > Thanks
> >
> >
>
>

Relevant Pages

  • Re: Assigning CALs in SBS2003?
    ... it also helps if you realise that no MS license tracking system/mechanism ... Fortunately SBS' ability to ... That's the simple way - keep all CALs the same type, ... economical to purchase User CALs for these folks. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS R2 CALs
    ... When you upgrade to R2 on a SBS SP1 with 70 User CALs you do NOT have to repurchase the additional user CALs ONLY the basic R2 upgrade for either Standard or Premium whichever is the case. ... >> The license management panel only shows 5 licenses. ...
    (microsoft.public.windows.server.sbs)
  • Re: Assigning CALs in SBS2003?
    ... Because they are carrying the license, the connection is compliant and only the single User CAL is considered to be in use. ... Any persons, whether they hold a "user" CAL, or not, may use this device to connect to the SBS and the connection is compliant because the device holds the license. ... Generally speaking, if you have more 'Devices' than 'Persons', you'll purchase User CALs; that's the most economical for you and the flexibility allows this. ...
    (microsoft.public.windows.server.sbs)
  • Re: Assigning CALs in SBS2003?
    ... A person carries a "user" license around with him/her. ... connect to the SBS and the connection is compliant because the device ... That's the simple way - keep all CALs the same type, ... to purchase User CALs for these folks. ...
    (microsoft.public.windows.server.sbs)
  • Windows 2003 SBS Licensing Problems
    ... I've been having a tough time with the licensing on my Windows 2003 SBS. ... additional 10 User CALS from our vendor. ... the server and we have to restore them from our backup file! ... license" warning would seriously slow everyone down while logging into the ...
    (microsoft.public.windows.server.sbs)