Re: sbs CAL's

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



I just KNEW someone was going to say that! In that case, the server is NOT a
device, since the EULA does not include "server" anywhere in the description
of a CLIENT Access License, and according to Microsoft, in an SBS 2003
domain, there is "no such thing" as a server-to-server license.. The user
would require a CAL, though, to be legal.

Gregg Hill

"kj" <kj@xxxxxxxxxxx> wrote in message
news:u9yL34j5FHA.3588@xxxxxxxxxxxxxxxxxxxxxxx
> Of course when a user logs on to a member server using a domain account
> then they become an authenticating user and server becomes a device and
> really muddies all the waters. ( just don't do it!)
>
> --
> /kj
> "Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
> news:ONKGz4h5FHA.3588@xxxxxxxxxxxxxxxxxxxxxxx
>> Ronnie,
>>
>> No, that is incorrect. Per the three different people I spoke to at MS,
>> there is no such thing as a server-to-server license. The key here is
>> that the SBS CALs are CLIENT Access Licenses. Other servers on the
>> network are NOT clients in Microsoft's eyes. I have been told by three
>> people at Microsoft that you can buy a base SBS 2003 with its five
>> licenses and add an UNLIMITED number of other servers, NONE of which
>> consumes an SBS CLIENT Access License.
>>
>> Per the EULA, a "device" is described as "...a single personal computer,
>> workstation, terminal, handheld computer, pager, telephone, personal
>> digital assistant, or other electronic device ("Device")..." Again, there
>> is no such thing as a server-to-server access license in an SBS 2003
>> domain. Other servers are not considered to be a "device" and do not
>> require a license, other than the server license used to install the
>> server software itself (Windows NT4 Server, 2000 Server, or Server 2003).
>> The additional servers can be member servers, and if they are 2000 or
>> 2003, they can be domain controllers.
>>
>> From the FAQ you posted:
>> Q. I want to have additional Windows-based servers in my Windows Small
>> Business Server 2003 domain. Do I need CALs for those servers?
>>
>> A. Your Windows Small Business Server 2003 CALs cover you for any
>> additional Windows-based servers in the domain. You do not need to buy
>> additional CALs for them.
>>
>> Per that statement and the multiple clarifications I have gotten for
>> Microsoft, you are covered for "any additional Windows-based servers" in
>> the domain. "Any" and all additional servers. "You do not need to buy
>> additional CALs for them." You can have 75 CALs, with 75 users and
>> devices, and have 200 other servers, all covered because they reside in
>> the SBS 2003 domain. "You do not need to buy additional CALs for them."
>>
>> No CAL required per additional server. Final answer!
>>
>> Gregg Hill
>>
>>
>>
>> "RG strath.ac.uk>" <ronnie.gibson<ATSIGN> wrote in message
>> news:eRbj90d5FHA.2396@xxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> "Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
>>> news:e6iYgqa5FHA.1416@xxxxxxxxxxxxxxxxxxxxxxx
>>>> According to Microsoft, there is no such thing as a server-to-server
>>>> license, and SBS 2003 CALs cover ALL additional servers, even if you
>>>> have 100's of them. The additional servers do NOT consume an SBS CAL.
>>>
>>> Gregg,
>>> I'd imagine those licenses would be termed as 'Device CALs' rather than
>>> server-to-server licenses.
>>>
>>> The confusion on this topic always seems to centre over the ambiguous
>>> statement that additional server on the SBS network don't require any
>>> CALs.
>>> The conclusion usually reached is that while users don't require
>>> additional
>>> CALs to access the additional Windows Server (as they would in a non-SBS
>>> environment), the server itself does consume one CAL.
>>>
>>> So one CAL per additional server but no user CALs required for users to
>>> access those servers.
>>>
>>> Hope that helps,
>>> Ronnie
>>>
>>
>>
>
>


.



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: 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)
  • RE: SBS and remote access
    ... To set up Terminal Server we need another server, ... RWW and OWA to access SBS from remote ... Windows Small Business Server 2003 Environment ... Small Business Server 2003 client access license. ...
    (microsoft.public.windows.server.sbs)