Getting Started with W2K3 Terminal Services

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

compsosinc@gmail.com

Guest
We have a Windows 2003 Server R2 Standard Edition. It is in a domain
that has SBS2000 as the domain controller and its role is designated
as a "File Server". This Windows 2003 Server has our MRP software
installed on it. We are going to setup (10) XP Pro systems on our
manufacturing floor (used by more than one user) to access the
application on the Windows 2003 Server using the Termianl Services
capability of its OS. As we understand the licensing, we just need to
purchase (10) TS CALs in per Device mode; however we are confused by
the following from Microsoft website:

"Windows Server License
The Windows Server 2003 R2 licensing model requires a server license
for each copy of the server software installed. Terminal Services
functionality is included in the Windows Server license.

Windows Server Client Access License
In addition to a server license, a Windows Server Client Access
License (CAL) is required. If you wish to conduct a Windows session,
an incremental Terminal Server Client Access License (TS CAL) is
required as well. A Windows session is defined as a session during
which the server software hosts a graphical user interface on a
device. For Windows sessions, a TS CAL is required for each user or
device"


Question: It appears to state that we also need a Windows Server
Client Access License (CAL) in addition to the TS CAL for each client
-- do we need both?

We think we need to do the following, in ths order:

1. Change the role of the Server to a Terminal Server.
2. Activate the License Server on the same box.
3. Purchase (10) TS-CALs --Microsoft Part number R-19-00848 Per
Device.
4. Install the TS-CALs and connect the clients.

Thanks!
 
Re: Getting Started with W2K3 Terminal Services

Yes, you need both. Depending on the version of 2003 you
purchased (retail, oem, volume, etc.), you may already own
some of the required Windows Server CALs.

For example, if you purchased 2003 Standard (OEM) preinstalled
on a new server it will include 5 CALs. That would mean that
you need to purchase 5 additional Windows device CALs plus
10 TS Device CALs.

I would also recommend you consider purchasing Software Assurance
on your 2003 Server license, Windows CALs, and TS CALs so
that you will be entitled to upgrade to Server 2008.

-TP

compsosinc@gmail.com wrote:
> We have a Windows 2003 Server R2 Standard Edition. It is in a domain
> that has SBS2000 as the domain controller and its role is designated
> as a "File Server". This Windows 2003 Server has our MRP software
> installed on it. We are going to setup (10) XP Pro systems on our
> manufacturing floor (used by more than one user) to access the
> application on the Windows 2003 Server using the Termianl Services
> capability of its OS. As we understand the licensing, we just need to
> purchase (10) TS CALs in per Device mode; however we are confused by
> the following from Microsoft website:
>
> "Windows Server License
> The Windows Server 2003 R2 licensing model requires a server license
> for each copy of the server software installed. Terminal Services
> functionality is included in the Windows Server license.
>
> Windows Server Client Access License
> In addition to a server license, a Windows Server Client Access
> License (CAL) is required. If you wish to conduct a Windows session,
> an incremental Terminal Server Client Access License (TS CAL) is
> required as well. A Windows session is defined as a session during
> which the server software hosts a graphical user interface on a
> device. For Windows sessions, a TS CAL is required for each user or
> device"
>
>
> Question: It appears to state that we also need a Windows Server
> Client Access License (CAL) in addition to the TS CAL for each client
> -- do we need both?
>
> We think we need to do the following, in ths order:
>
> 1. Change the role of the Server to a Terminal Server.
> 2. Activate the License Server on the same box.
> 3. Purchase (10) TS-CALs --Microsoft Part number R-19-00848 Per
> Device.
> 4. Install the TS-CALs and connect the clients.
>
> Thanks!
 
Re: Getting Started with W2K3 Terminal Services

So even if the (10) computers on the factory floor do not join the
domain, and only conduct a TS session, we also need the Windows Device
CALs (MS Part # R18-00909) in addition to the TS-CALs?

Thanks again..

TP wrote:
> Yes, you need both. Depending on the version of 2003 you
> purchased (retail, oem, volume, etc.), you may already own
> some of the required Windows Server CALs.
>
> For example, if you purchased 2003 Standard (OEM) preinstalled
> on a new server it will include 5 CALs. That would mean that
> you need to purchase 5 additional Windows device CALs plus
> 10 TS Device CALs.
>
> I would also recommend you consider purchasing Software Assurance
> on your 2003 Server license, Windows CALs, and TS CALs so
> that you will be entitled to upgrade to Server 2008.
>
> -TP
>
> compsosinc@gmail.com wrote:
> > We have a Windows 2003 Server R2 Standard Edition. It is in a domain
> > that has SBS2000 as the domain controller and its role is designated
> > as a "File Server". This Windows 2003 Server has our MRP software
> > installed on it. We are going to setup (10) XP Pro systems on our
> > manufacturing floor (used by more than one user) to access the
> > application on the Windows 2003 Server using the Termianl Services
> > capability of its OS. As we understand the licensing, we just need to
> > purchase (10) TS CALs in per Device mode; however we are confused by
> > the following from Microsoft website:
> >
> > "Windows Server License
> > The Windows Server 2003 R2 licensing model requires a server license
> > for each copy of the server software installed. Terminal Services
> > functionality is included in the Windows Server license.
> >
> > Windows Server Client Access License
> > In addition to a server license, a Windows Server Client Access
> > License (CAL) is required. If you wish to conduct a Windows session,
> > an incremental Terminal Server Client Access License (TS CAL) is
> > required as well. A Windows session is defined as a session during
> > which the server software hosts a graphical user interface on a
> > device. For Windows sessions, a TS CAL is required for each user or
> > device"
> >
> >
> > Question: It appears to state that we also need a Windows Server
> > Client Access License (CAL) in addition to the TS CAL for each client
> > -- do we need both?
> >
> > We think we need to do the following, in ths order:
> >
> > 1. Change the role of the Server to a Terminal Server.
> > 2. Activate the License Server on the same box.
> > 3. Purchase (10) TS-CALs --Microsoft Part number R-19-00848 Per
> > Device.
> > 4. Install the TS-CALs and connect the clients.
> >
> > Thanks!
 
Re: Getting Started with W2K3 Terminal Services

Yes. The part numbers vary depending on the type of license.
For example, the number would be different if purchased via
Open Business license instead. If you want a retail 5-user pack
then the number you referenced looks correct.

-TP

compsosinc@gmail.com wrote:
> So even if the (10) computers on the factory floor do not join the
> domain, and only conduct a TS session, we also need the Windows Device
> CALs (MS Part # R18-00909) in addition to the TS-CALs?
>
> Thanks again..
 
Back
Top