Re: Licensing Question

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

From: Jagtar Singh (JagtarSingh_at_discussions.microsoft.com)
Date: 11/25/04


Date: Thu, 25 Nov 2004 10:53:02 -0800

Hi Chad,

     There's not much that I can do with the Win98 clients...yet. The
budget is $10K, and while that sounds like a lot, the server HW is taking out
$5.8K, the router/firewall/VPN appliance is taking out $0.4K, SBS2003 Premium
is taking out $0.3K, extra 10 CALs is taking out (have to quote this still),
AVG software will consume $1.1K, and the backup hardware will take out
another $1.1K.

     Add it all up and that's $8.7K (no CALs yet) and I've not been paid
either. This company wants to be fully licensed and protected, and the
desktop upgrade is budgetted for next month. 10 PCs to upgrade to WinXP and
Office2K3 = another $10K easily.

     I would have done the PCs first and the server after, but their current
server is dying.

     This client of mine (who will remain anonymous) has been running
un-licensed software for a long time (they didn't know) and they're trusting
me to get them out of this mess. It's tough and expensive, though, and they
don't want to get into trouble. I'm doing my best to help them out.

- Jagtar

"Chad A. Gross [SBS MVP]" wrote:

> Hi Jagtar -
>
> In the scenario you have described, the owner would only be using a single
> User CAL. As for the gritty details of SBS Licensing:
>
> SBS does NOT use concurrent licensing. Once a user or device consumes an
> SBS CAL, they retain that CAL until such time that they no longer have a
> future need to authenticate with the SBS. (e.g. a user leaves the company,
> or a device is removed from service). At that time, the CAL can be
> reassigned to another User / Device.
>
> The recommended solution is to not mix User CALs and Device CALs. So the
> simple answer for licensing is that you'll need either a User CAL for each
> of your users (mind you, you only need CALs for your actual users - not user
> accounts or Exchange mailboxes), or a Device CAL for each unique device that
> will be authenticating with your SBS. If you're going to be doing any sort
> of remote access either via OWA, OMA, RWW or VPN, then you're probably going
> to be much better off going with the User CAL model, as this allows each
> user to have multiple simultaneous connections while only using their
> individual CAL.
>
> As for the connection limit, SBS doesn't have the technology to track its
> licensing scheme. As a result, it uses a concurrent connection tracking
> limit. Eventually, SBS will block log-ons. However, it is important to
> note that SBS has some built-in 'wiggle-room' - so if you have 10 User CALs,
> and all 10 Users are connected to the server, and the owner connects again
> from another device, he's not going to be blocked. Eventually. If the
> numbers keep increasing, eventually connections will be blocked. (I'm not
> sure where this limit is . . . )
>
> And last but certainly not least, Win98??? You really need to kill off
> all of your Win98 boxes. They're not secure, and they don't allow to take
> advantage of all of the features of SBS2k3. You should *really* be planning
> to replace these as soon as possible . . .
>
> --
>
> Chad A. Gross - SBS MVP
> SBS ROCKS!
>
> www.msmvps.com/cgross
> www.gosbs.org
>
>
> Jagtar Singh wrote:
> > Hi Everyone,
> >
> > I'm installing SBS2003 and the owner of the company wants to VPN
> > into the office. We'll be using a LinkSys RV082 router/firewall/VPN
> > appliance for the VPN-ing. The owner of the company has a two PCs at
> > work (one for surfing and one for work; both are Win98 clients) and a
> > laptop at home (WinXP; which will be used for VPN). He will only
> > have one user account.
> >
> > Assume that all three machines are logged on / authenticated to
> > the SBS2003 server. If I go with user CALs, will he use up 1 CAL
> > (since he's only using one account), 2 CALs (since the devices he's
> > using are connected in two different ways; VPN and office) or 3 CALs
> > (since he's on three machines)?
> >
> > This point is very crucial for my understanding, since the
> > company is small and wants to be as compliant as possible for the
> > lowest cost (I can appreciate that). I don't want to buy extra CALs,
> > but I also don't want to buy too few.
> >
> > BTW, if I buy too few, will the server not allow connections at
> > all, or will it flag warnings for awhile until we get the required
> > licenses?
> >
> > Thanks in advance,
> >
> > - Jagtar
>
>
>



Relevant Pages

  • Re: SBS 2003 IIS BASED SERVICES FAIL INTERMITTENTLY
    ... If I read your post correctly, you have a switch where the SBS ... Run DHCP server on your SBS, and set all client machine nics to dynamic. ... Once you have your nics configured, run the Connect to the Internet wizard, ... QUESTION1 - what is REFUSING CONNECTIONS? ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 with Server 2008 Terminal Services
    ... Customers running SBS 2003 R2 can use their CALs to access additional servers running Windows Server 2003, Exchange Server 2003 and SQL Server 2005 Workgroup Edition on the SBS 2003 R2 network. ... See the licensing questions section for additional information on SBS 2003 R2 CALs. ... Remote Web Workplace rather than VPN. ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... so that means that I do not need any CALS for the ... Chris> Using up the SBS CALS is something that I want to avoid as it will ... Justin> Are you trying to say that if a user logs onto the terminal server ... The reason I want to make it a member server is because some users will need ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Server Licensing issues on a SBS 2003 Domain
    ... so that means that I do not need any CALS for the ... Chris> Using up the SBS CALS is something that I want to avoid as it will ... Justin> Are you trying to say that if a user logs onto the terminal server ... The reason I want to make it a member server is because some users will need ...
    (microsoft.public.backoffice.smallbiz)
  • Re: SBS2003 - Transition Pack
    ... If you were under your current purchased CALs, ... If it still says it's SBS, ... Once the transition is complete, ... Server 2003 Standard Edition and Exchange Server 2003 Standard. ...
    (microsoft.public.windows.server.sbs)