How many CALs required?

  • Thread starter Thread starter compsosinc@gmail.com
  • Start date Start date
C

compsosinc@gmail.com

Guest
We have the following environment:

(1) SBS2000 Server as DC -- NOT SBS2003
(1) Windows 2003 Server Std Edition as a Terminal Server


We have:


(15) Users accessing the SBS2000 DC using XP Pro machines


We are adding:


(10) XP Pro newly purchased-clients (many users) accessing the
Windows
2003 Terminal Server


Question: How many and what type of CALs do we need in TOTAL to
support this
environment (assume we have none of the following):

SBS2000 CALs = ?
Windows Server CALs = ?
Terminal Server 2003 Device CALs = ?


Thanks !
 
Re: How many CALs required?

I would post this question in the sbs newsgroup. SBS licensing is
different from Windows licensing, especially the requirements in a
situation with additional servers in the domain.

microsoft.public.windows.server.sbs

SBS 2003 Licensing: Frequently Asked Questions
http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/li
censingfaq.mspx

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

compsosinc@gmail.com wrote on 13 sep 2007 in
microsoft.public.windows.terminal_services:

> We have the following environment:
>
> (1) SBS2000 Server as DC -- NOT SBS2003
> (1) Windows 2003 Server Std Edition as a Terminal Server
>
>
> We have:
>
>
> (15) Users accessing the SBS2000 DC using XP Pro machines
>
>
> We are adding:
>
>
> (10) XP Pro newly purchased-clients (many users) accessing the
> Windows
> 2003 Terminal Server
>
>
> Question: How many and what type of CALs do we need in TOTAL to
> support this
> environment (assume we have none of the following):
>
> SBS2000 CALs = ?
> Windows Server CALs = ?
> Terminal Server 2003 Device CALs = ?
>
>
> Thanks !
 
Re: How many CALs required?

On Sep 13, 4:29 pm, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
> I would post this question in the sbs newsgroup. SBS licensing is
> different from Windows licensing, especially the requirements in a
> situation with additional servers in the domain.
>
> microsoft.public.windows.server.sbs
>
> SBS 2003 Licensing: Frequently Asked Questionshttp://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/li
> censingfaq.mspx
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> compsos...@gmail.com wrote on 13 sep 2007 in
> microsoft.public.windows.terminal_services:
>
>
>
> > We have the following environment:

>
> > (1) SBS2000 Server as DC -- NOT SBS2003
> > (1) Windows 2003 Server Std Edition as a Terminal Server

>
> > We have:

>
> > (15) Users accessing the SBS2000 DC using XP Pro machines

>
> > We are adding:

>
> > (10) XP Pro newly purchased-clients (many users) accessing the
> > Windows
> > 2003 Terminal Server

>
> > Question: How many and what type of CALs do we need in TOTAL to
> > support this
> > environment (assume we have none of the following):

>
> > SBS2000 CALs = ?
> > Windows Server CALs = ?
> > Terminal Server 2003 Device CALs = ?

>
> > Thanks !- Hide quoted text -

>
> - Show quoted text -


Thanks, but I tried that and the MVPs just make fun of the fact that
we still have an SBS2000 box. They were wondering if we still had a
floppy drive...so if you can shed any light on this matter it would be
appreciated.
 
Re: How many CALs required?

compsosinc@gmail.com wrote:
> On Sep 13, 4:29 pm, "Vera Noest [MVP]" <vera.no...@remove-
> this.hem.utfors.se> wrote:
>> I would post this question in the sbs newsgroup. SBS licensing is
>> different from Windows licensing, especially the requirements in a
>> situation with additional servers in the domain.
>>
>> microsoft.public.windows.server.sbs
>>
>> SBS 2003 Licensing: Frequently Asked Questionshttp://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/li
>> censingfaq.mspx
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> compsos...@gmail.com wrote on 13 sep 2007 in
>> microsoft.public.windows.terminal_services:
>>
>>
>>
>>> We have the following environment:
>>> (1) SBS2000 Server as DC -- NOT SBS2003
>>> (1) Windows 2003 Server Std Edition as a Terminal Server
>>> We have:
>>> (15) Users accessing the SBS2000 DC using XP Pro machines
>>> We are adding:
>>> (10) XP Pro newly purchased-clients (many users) accessing the
>>> Windows
>>> 2003 Terminal Server
>>> Question: How many and what type of CALs do we need in TOTAL to
>>> support this
>>> environment (assume we have none of the following):
>>> SBS2000 CALs = ?
>>> Windows Server CALs = ?
>>> Terminal Server 2003 Device CALs = ?
>>> Thanks !- Hide quoted text -

>> - Show quoted text -

>
> Thanks, but I tried that and the MVPs just make fun of the fact that
> we still have an SBS2000 box. They were wondering if we still had a
> floppy drive...so if you can shed any light on this matter it would be
> appreciated.
>

Licensing issues can get very complicated. like taxes, the best thing is
to go to the source Contact Microsoft or your reseller to get the number...

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
 
Re: How many CALs required?

I'm sorry that you feel that way, but I can't agree with you.
I've read all of your posts during the last year in that newsgroup,
and I would say that you have received excellent advice, much more
knowledgeable than I can ever give you.
The guy who referred to the floppy only used this to forewarn you
that it could be a problem to install extra SBS2000 CALs, since
they apparantly come on a floppy disk. The fact that he warns you
about this twice only tells me that he is most likely used to blade
servers, which usually don't have a floppy drive.

That said, my guess, but it's not more than that, is:

> SBS2000 CALs = 15 (existing XP) + 10 (new XP) + 1 (2003 server)
> Windows Server CALs = would be none if the Windows Server was

running W2K. With a 2003 member server, I don't know
> Terminal Server 2003 Device CALs = one for every client which

connects to the TS. So at least 10 (for the new XPs), but maybe the
existing 15 XPs want to connect as well?

I totally agree with the advice give to you in the sbs newsgroup
and here by Hank: call your Microsoft Representative. Mixing
different products and versions makes licensing requirements
extremely complicated.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

compsosinc@gmail.com wrote on 14 sep 2007 in
microsoft.public.windows.terminal_services:

> On Sep 13, 4:29 pm, "Vera Noest [MVP]" <vera.no...@remove-
> this.hem.utfors.se> wrote:
>> I would post this question in the sbs newsgroup. SBS licensing
>> is different from Windows licensing, especially the
>> requirements in a situation with additional servers in the
>> domain.
>>
>> microsoft.public.windows.server.sbs
>>
>> SBS 2003 Licensing: Frequently Asked
>> Questionshttp://www.microsoft.com/windowsserver2003/sbs/techinfo
>> /overview/li censingfaq.mspx
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> compsos...@gmail.com wrote on 13 sep 2007 in
>> microsoft.public.windows.terminal_services:
>>
>>
>>
>> > We have the following environment:

>>
>> > (1) SBS2000 Server as DC -- NOT SBS2003
>> > (1) Windows 2003 Server Std Edition as a Terminal Server

>>
>> > We have:

>>
>> > (15) Users accessing the SBS2000 DC using XP Pro machines

>>
>> > We are adding:

>>
>> > (10) XP Pro newly purchased-clients (many users) accessing
>> > the Windows
>> > 2003 Terminal Server

>>
>> > Question: How many and what type of CALs do we need in TOTAL
>> > to support this
>> > environment (assume we have none of the following):

>>
>> > SBS2000 CALs = ?
>> > Windows Server CALs = ?
>> > Terminal Server 2003 Device CALs = ?

>>
>> > Thanks !- Hide quoted text -

>>
>> - Show quoted text -

>
> Thanks, but I tried that and the MVPs just make fun of the fact
> that we still have an SBS2000 box. They were wondering if we
> still had a floppy drive...so if you can shed any light on this
> matter it would be appreciated.
 
Re: How many CALs required?

Vera Noest [MVP] wrote:
>
> I totally agree with the advice give to you in the sbs newsgroup
> and here by Hank:


Awwwwww shucks........ <blush> < scratches floor with shoe> ;-)
--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
 
Re: How many CALs required?

On Sep 14, 4:25 pm, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
> I'm sorry that you feel that way, but I can't agree with you.
> I've read all of your posts during the last year in that newsgroup,
> and I would say that you have received excellent advice, much more
> knowledgeable than I can ever give you.
> The guy who referred to the floppy only used this to forewarn you
> that it could be a problem to install extra SBS2000 CALs, since
> they apparantly come on a floppy disk. The fact that he warns you
> about this twice only tells me that he is most likely used to blade
> servers, which usually don't have a floppy drive.
>
> That said, my guess, but it's not more than that, is:
>
> > SBS2000 CALs = 15 (existing XP) + 10 (new XP) + 1 (2003 server)
> > Windows Server CALs = would be none if the Windows Server was

>
> running W2K. With a 2003 member server, I don't know> Terminal Server 2003 Device CALs = one for every client which
>
> connects to the TS. So at least 10 (for the new XPs), but maybe the
> existing 15 XPs want to connect as well?
>
> I totally agree with the advice give to you in the sbs newsgroup
> and here by Hank: call your Microsoft Representative. Mixing
> different products and versions makes licensing requirements
> extremely complicated.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> compsos...@gmail.com wrote on 14 sep 2007 in
> microsoft.public.windows.terminal_services:
>
>
>
> > On Sep 13, 4:29 pm, "Vera Noest [MVP]" <vera.no...@remove-
> > this.hem.utfors.se> wrote:
> >> I would post this question in the sbs newsgroup. SBS licensing
> >> is different from Windows licensing, especially the
> >> requirements in a situation with additional servers in the
> >> domain.

>
> >> microsoft.public.windows.server.sbs

>
> >> SBS 2003 Licensing: Frequently Asked
> >> Questionshttp://www.microsoft.com/windowsserver2003/sbs/techinfo
> >> /overview/li censingfaq.mspx

>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___

>
> >> compsos...@gmail.com wrote on 13 sep 2007 in
> >> microsoft.public.windows.terminal_services:

>
> >> > We have the following environment:

>
> >> > (1) SBS2000 Server as DC -- NOT SBS2003
> >> > (1) Windows 2003 Server Std Edition as a Terminal Server

>
> >> > We have:

>
> >> > (15) Users accessing the SBS2000 DC using XP Pro machines

>
> >> > We are adding:

>
> >> > (10) XP Pro newly purchased-clients (many users) accessing
> >> > the Windows
> >> > 2003 Terminal Server

>
> >> > Question: How many and what type of CALs do we need in TOTAL
> >> > to support this
> >> > environment (assume we have none of the following):

>
> >> > SBS2000 CALs = ?
> >> > Windows Server CALs = ?
> >> > Terminal Server 2003 Device CALs = ?

>
> >> > Thanks !- Hide quoted text -

>
> >> - Show quoted text -

>
> > Thanks, but I tried that and the MVPs just make fun of the fact
> > that we still have an SBS2000 box. They were wondering if we
> > still had a floppy drive...so if you can shed any light on this
> > matter it would be appreciated.- Hide quoted text -

>
> - Show quoted text -


Thank you very much. Advice well taken. We were unsure if the new XP
clients would need SBS2000 CALs since they only need to use the TS of
the Windows 2003 Server.We have already purchased the 10 TS CALs &
additional Windows 2003 CALs. Guess we need 10 more SBS CALs.

Thanks again.
 
Back
Top