Re: Licensing Question -adding WK3 Server

Servers do not consume CALs because they are not considered "clients". With
SBS 2000, the Windows 2003 CALs are covered by the SBS 2000 CALs up to the
number of SBS 2000 CALs you have installed. You would only need a Windows
2003 server license for the additional server. KB 327644 is your guide for
this.

To determine the number of SBS 2000 installed CALs:

SBS Administrator Console | Server Status | About

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

<compsosinc@xxxxxxxxx> wrote in message
news:1171031534.062096.119640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
We are going to be adding a Windows 2003 R2 Server as a member server
to an existing SBS2000 domain. The 2003 Server will run an application
that approx 15 XP workstations will access. Those same workstations,
plus 5 others, will access the SBS 2000 Server as they always have.

1. How do we check how many CALs we currently have installed on for
the SBS2000 Server?

We have been reviewing posts and articles concerning whether or not we
need the following:

1. A CAL for the Windows 2003 Server to be added to the domain.
2. CALs for the workstations to access the Windows 2003 Server, while
still accessing the SBS2000 server.

Here is a thread from 2005 that indicates that we do not need any more
CALs for anything.

http://groups.google.com/group/microsoft.public.backoffice.smallbiz2000/browse_thread/thread/86cfb16e4f0846fa/bb61eb3ce253b4b1?lnk=st&q=CALs+windows+2003+server+sbs+2000+domain&rnum=6#bb61eb3ce253b4b1

Also, here is an excerpt from Microsoft KB Article 327644, dated
October 2006

The license agreement for the SBS 2000 client access license pack
says,
"This CAL also authorizes you to access and use the services and
functionality of a Microsoft Windows 2000 Server that is in the same
domain
as the Server Software." Although it is not specifically stated, you
are
also allowed to access any computers that are running Windows Server
2003 in
the same domain as the SBS computer. The reference to Windows Server
2003
was not included in the license agreement because Windows Server 2003
was
not a released product at the time. There are no plans to update the
text of
the license agreement."

Can anyone clarify what we need to do for proper licensing of this
setup?

Thanks



.

Relevant Pages

  • Re: Questions about SBS
    ... There is a misunderstanding of the SBS licensing that you appear to have ... CALs are allocated to an individual User or Device. ... You'll need to buy a Separate Server, Windows ...
    (microsoft.public.windows.server.sbs)
  • RE: Service Pack 1 on SBS 2003 Premium
    ... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
    (microsoft.public.windows.server.sbs)
  • RE: Service Pack 1 on SBS 2003 Premium
    ... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
    (microsoft.public.windows.server.sbs)
  • Re: The list of servers for this workgroup is not currently availi
    ... Select Windows Small Business Server 2003 and then click Change/Remove. ... You may prompt to inset SBS installation CD. ... Our only problem w/ connecting to the branch office is mapping ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Standard - Update to SP 1 fails
    ... order to prepare SBS server to deploy Windows XP SP2 to client computers ... that are running Windows XP Professional. ... The SBS SP1 launcher need copy ... please install it and then ...
    (microsoft.public.windows.server.sbs)
Loading