Re: User vs device CALs

AFAIK, you don't *have* to move to more servers after implementing the
Transition Pack. You'd need to upgrade to SBS 2003 R2, then buy the R2
Transition Pack and any additional CALs (the Pack sets you back to 5 for
each major component). Kind of expensive but may be the best you can do.

I would think putting the Lab users onto their own SBS server would be less
expensive (even a cheap desktop may do for the hardware).

--
Merv Porter [SBS-MVP]
============================

"Adrian Marsh (NNTP)" <adrian.marsh@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:45C4E44C.60209@xxxxxxxxxxxxxxxxxxxxxxxxxx
Hi merv,

Yeah.. I've already started down that route, of not adding lab PCs to
the domain to conserve licenses. This will make it annoying for the
end-users, but the best I can do right now..

One question maybe you can answer: With the transition pack, do you
actually need new hardware? (as part of the pack itself?) I know it
breaks out the Exchange and DC parts of SBS out to full servers.. My
server stats show CPU usage rarely breaks 30%, and if I could make it
last to 80-90 users then I could properly plan the transition. But if it
requires new h/w as part of the pack immediately, then that obviously
changes the upfront requirements.

I do actually want to move away from SBS, as I need a more resilient
system, but I'd like some breathing space with other projects.


Merv Porter [SBS-MVP] wrote:
Hi Adrian,

The limit is 75 CALs, whether you reach that total with Device CALs, User
CALs or a combination of the two types. This is an absolute limit and
not
"concurrent use" as it was in SBS 4.5 and SBS 2000.

I'm wondering if the "lab" has an absolute need to be part of the current
SBS network. Maybe you can split it off into its own SBS network (with
its
own SBS server, of course)? With the proper setup, the two networks
could
"share" a single Internet connection.

I think you're only other option is to buy and deploy the Transistion
Pack
and break away from SBS as a single server environment.



.

Relevant Pages

  • 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: problem connecting to server from XP
    ... If you just purchased the "software pack" I would ask why it didn't include ... SBS SP1 timeframe of updates. ... want to start with disks that were Windows Small Business Server 2003 w/SP1 ... I installed firewall by using the wizard "connect to internet" ...
    (microsoft.public.windows.server.sbs)
  • 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)
  • Re: Licence reset in SBS 2003
    ... I understand that the CALs often disappear on SBS ... Microsoft CSS Online Newsgroup Support ... >> We are maintenaing few SBS 2003 server and sometime we lose all our ...
    (microsoft.public.windows.server.sbs)