Re: Licensing Question -adding WK3 Server

While I don't want to dispute what Eugene says, a server does not consume a
CAL (Client Access License). A CAL is for a license for a device or a user
that is "accessing the server". It is not for a server that is "being
accessed". An SBS CAL is used to authenticate to the SBS domain (the SBS
server). A member server does not need to authenticate

How to configure licensing on an additional Windows server in an SBS network
http://support.microsoft.com/kb/327644

This question has been batted back and forth in this newsgroup for many
years. Over that time I have come to the conclusion, based on posts by Eric
Ligman - MS licensing guru and others, that servers do not consume SBS CALs.

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


<compsosinc@xxxxxxxxx> wrote in message
news:1171313994.761340.174250@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Feb 9, 12:19 pm, "Merv Porter [SBS-MVP]"
<mwport@xxxxxxxxxxxxxxxxxxx> wrote:
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]
============================

<compsos...@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.smallbiz20...

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- Hide quoted text -

- Show quoted text -


Merv- I received this reply in another newsgroup - it indicates that
the 2003 Server will consume a CAL and that contradicts what you
wrote. Can you clarify? here it is:

hi,

There are only device CALs for SBS2000.
To see the number of CALs registered/installed on the SBS2000,
launch the SBS Administration Console (in Start menu), then near the
right-corner of this window, click on "About". It'll bring up a
window
showing the licensed company and the number of CALs.


SBS2k supports 2 modes of CAL licensing; in your case you'll need to
use "per seat mode" licensing.


You'll need CALs for all devices joining the SBS2k domain, including
one for the (member) Windows server- so count all PCs plus Win
server.
However, you won't need separate CALs for Windows server. From
your info, it looks like you'll need 21 SBS CALs (15 + 5 + 1).


HTH,
Eugene Tan






.

Relevant Pages

  • Re: How to add a user with very limited rights
    ... The Windows Server 2003 External Connector license is an optional ... An EC license is not applicable to Web Edition or Windows Small Business ... For more information about External Connector License, ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW problem on one Client machine
    ... Welcome to SBS newsgroup. ... services licensing service on a Windows 2000 domain controller. ... terminal license successfully. ... messages in the event log saying that "A terminal license server cannot be ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Client Access Licenses
    ... You need 1 server license for each server OS and app (i.e. Windows Server 2003, ... The exception is for per-processor licensing on SQL which doesn't required CALs. ...
    (microsoft.public.windows.server.general)
  • Re: Anonymous connections.
    ... Windows Server 2003 Licensing Server can control ... you may use the New External Connector License option. ... Microsoft Partner Support ...
    (microsoft.public.windows.terminal_services)
Loading