I have SBS 2000 with 25 Windows CALs. The license says
that these CALs cannot be used as Terminal Services CALs,
except if the client machine is Windows 2000 Pro or
Windows XP Pro.

I then found that if you have internet type users
accessing the server, then you will need the Internet
Connector License.

I have also read that if the external users are minimal,
then the Internet Connector License is optional.

What is the exact license setup for allowing internal
users as well as minimal external users to connect
through Terminal Services ?

Microsoft's website states that the Windows 2003 External
Connector License (ECL) has replaced the Internet
Connector License. Will the ECL work on SBS 2000 ?

Re: Terminal Services CALs by Javier

Javier
Tue Jan 25 07:29:57 CST 2005

First of all, whats your TS box? Windows 2000 or 2003? You are not running
SBS2k in TS (app sharing mode)? right?

Now... I don't think you need "Connector Licenses" because those are for big
enterprises that don't know beforehand who's going to be logging on their
servers. AFAIK you can't buy a connector when the users are in your own
company... so lets forget about this for a minute.

If your TS box is Windows 2000-> You need an SBS CAL for each device
connecting AND a Win2k TS CAL for every other OS than Windows 2000 or XP.
So, lets say you have a Linux or Win9x box accessing the TS server you would
need both CALs.

If your TS box is Windows 2003-> You need an SBS CAL and a Win2k3 TS CAL
always (there are no "built-in" TS CALs in Win2k3). However, if you had SA
or you got Windows XP before Win2k3 launch date you are (or were) entitled
to free TS CALs for those systems.

--
Javier [SBS MVP]
www.msmvps.com/javier
<< SBS ROCKS !!! >>

"Sam" <anonymous@discussions.microsoft.com> wrote in message
news:05d401c502df$1e7a9600$a601280a@phx.gbl...
>I have SBS 2000 with 25 Windows CALs. The license says
> that these CALs cannot be used as Terminal Services CALs,
> except if the client machine is Windows 2000 Pro or
> Windows XP Pro.
>
> I then found that if you have internet type users
> accessing the server, then you will need the Internet
> Connector License.
>
> I have also read that if the external users are minimal,
> then the Internet Connector License is optional.
>
> What is the exact license setup for allowing internal
> users as well as minimal external users to connect
> through Terminal Services ?
>
> Microsoft's website states that the Windows 2003 External
> Connector License (ECL) has replaced the Internet
> Connector License. Will the ECL work on SBS 2000 ?



Re: Terminal Services CALs by Sam

Sam
Tue Jan 25 09:03:47 CST 2005

Thanx. That makes sense and answers my question.

I don't know if I must open a new post, but can the SQL
Server packaged with SBS2k be used by a web app. that is
accessed via the internet by our clients ?

>-----Original Message-----
>First of all, whats your TS box? Windows 2000 or 2003?
You are not running
>SBS2k in TS (app sharing mode)? right?
>
>Now... I don't think you need "Connector Licenses"
because those are for big
>enterprises that don't know beforehand who's going to be
logging on their
>servers. AFAIK you can't buy a connector when the users
are in your own
>company... so lets forget about this for a minute.
>
>If your TS box is Windows 2000-> You need an SBS CAL for
each device
>connecting AND a Win2k TS CAL for every other OS than
Windows 2000 or XP.
>So, lets say you have a Linux or Win9x box accessing the
TS server you would
>need both CALs.
>
>If your TS box is Windows 2003-> You need an SBS CAL and
a Win2k3 TS CAL
>always (there are no "built-in" TS CALs in Win2k3).
However, if you had SA
>or you got Windows XP before Win2k3 launch date you are
(or were) entitled
>to free TS CALs for those systems.
>
>--
>Javier [SBS MVP]
>www.msmvps.com/javier
><< SBS ROCKS !!! >>
>
>"Sam" <anonymous@discussions.microsoft.com> wrote in
message
>news:05d401c502df$1e7a9600$a601280a@phx.gbl...
>>I have SBS 2000 with 25 Windows CALs. The license says
>> that these CALs cannot be used as Terminal Services
CALs,
>> except if the client machine is Windows 2000 Pro or
>> Windows XP Pro.
>>
>> I then found that if you have internet type users
>> accessing the server, then you will need the Internet
>> Connector License.
>>
>> I have also read that if the external users are
minimal,
>> then the Internet Connector License is optional.
>>
>> What is the exact license setup for allowing internal
>> users as well as minimal external users to connect
>> through Terminal Services ?
>>
>> Microsoft's website states that the Windows 2003
External
>> Connector License (ECL) has replaced the Internet
>> Connector License. Will the ECL work on SBS 2000 ?
>
>
>.
>

Re: Terminal Services CALs by Javier

Javier
Tue Jan 25 09:20:38 CST 2005

> I don't know if I must open a new post, but can the SQL
> Server packaged with SBS2k be used by a web app. that is
> accessed via the internet by our clients ?

SBS2k licensing doesn't allow that. However, SBS2k3Premium does... so you
have a reason to upgrade :-)

--
Javier [SBS MVP]
www.msmvps.com/javier
<< SBS ROCKS!!! >>



Re: Terminal Services CALs by Cris

Cris
Tue Jan 25 09:43:46 CST 2005

No it cannot with SBS 2000
That changes in SBS 2003 and is permitted

--
Cris Hanna [SBS - MVP]
---------------------------------------
Please reply only to the newsgroup and not to me directly so that everyone
can benefit from the information
"Sam" <anonymous@discussions.microsoft.com> wrote in message
news:068701c502ef$12208e90$a601280a@phx.gbl...
> Thanx. That makes sense and answers my question.
>
> I don't know if I must open a new post, but can the SQL
> Server packaged with SBS2k be used by a web app. that is
> accessed via the internet by our clients ?
>
>>-----Original Message-----
>>First of all, whats your TS box? Windows 2000 or 2003?
> You are not running
>>SBS2k in TS (app sharing mode)? right?
>>
>>Now... I don't think you need "Connector Licenses"
> because those are for big
>>enterprises that don't know beforehand who's going to be
> logging on their
>>servers. AFAIK you can't buy a connector when the users
> are in your own
>>company... so lets forget about this for a minute.
>>
>>If your TS box is Windows 2000-> You need an SBS CAL for
> each device
>>connecting AND a Win2k TS CAL for every other OS than
> Windows 2000 or XP.
>>So, lets say you have a Linux or Win9x box accessing the
> TS server you would
>>need both CALs.
>>
>>If your TS box is Windows 2003-> You need an SBS CAL and
> a Win2k3 TS CAL
>>always (there are no "built-in" TS CALs in Win2k3).
> However, if you had SA
>>or you got Windows XP before Win2k3 launch date you are
> (or were) entitled
>>to free TS CALs for those systems.
>>
>>--
>>Javier [SBS MVP]
>>www.msmvps.com/javier
>><< SBS ROCKS !!! >>
>>
>>"Sam" <anonymous@discussions.microsoft.com> wrote in
> message
>>news:05d401c502df$1e7a9600$a601280a@phx.gbl...
>>>I have SBS 2000 with 25 Windows CALs. The license says
>>> that these CALs cannot be used as Terminal Services
> CALs,
>>> except if the client machine is Windows 2000 Pro or
>>> Windows XP Pro.
>>>
>>> I then found that if you have internet type users
>>> accessing the server, then you will need the Internet
>>> Connector License.
>>>
>>> I have also read that if the external users are
> minimal,
>>> then the Internet Connector License is optional.
>>>
>>> What is the exact license setup for allowing internal
>>> users as well as minimal external users to connect
>>> through Terminal Services ?
>>>
>>> Microsoft's website states that the Windows 2003
> External
>>> Connector License (ECL) has replaced the Internet
>>> Connector License. Will the ECL work on SBS 2000 ?
>>
>>
>>.
>>