Windows NT newbie question about terminal server

  • Thread starter Thread starter DAXU@HOTMAIL.COM
  • Start date Start date
D

DAXU@HOTMAIL.COM

Hi,
>From windows components wizard, I see that I can add "Terminal Server"

component.
But I already has terminal service runing on the server by default and
people (limit is 2+1, isn't it?) can use remote desktop to connect to
this server.
Can someone tell me what I will get from adding this "terminal server"
component?

Many Thanks
Jerry
 
What you are using now is Remote Desktop for Administration, which
is limited to 2 + 1 connections, by default only available for
Administrators, and withour extra licensing requirements.
You can use this to remotely manage any type of server, i.e. a
Domain Controller, Print Server, SQL server, Exchange server, etc.

When you install the Terminal Services component, you turn the
server into a "proper" Terminal Server. This enables multiple
normal users to connect to the server and run their desktop
applications on the server itself. You basically turn the server
into a multiple-user desktop.
It requires additional licensing (a TS CAL for every user or
device). The number of connecting users is only limited by the
number of licenses and the hardware.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

DAXU@HOTMAIL.COM wrote on 09 jul 2007 in
microsoft.public.windows.terminal_services:

> Hi,
>>From windows components wizard, I see that I can add "Terminal
>>Server"

> component.
> But I already has terminal service runing on the server by
> default and people (limit is 2+1, isn't it?) can use remote
> desktop to connect to this server.
> Can someone tell me what I will get from adding this "terminal
> server" component?
>
> Many Thanks
> Jerry
 
Hi,
Thanks for your reply.
I am thinking of make this server an application server so that users
who has the access right to this machine will be able to use these
softwares.
Are there any compatiability issues with software(such as office,
spss, matlab etc)? Is it right for me to assume that if an application
can run under windows 2003/2000, then it will be able to run under
this windows terminal server (basically just a windows 2003 with
terminal service component installed)?
Many thanks
Jerry

On 9 Jul, 16:34, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
> What you are using now is Remote Desktop for Administration, which
> is limited to 2 + 1 connections, by default only available for
> Administrators, and withour extra licensing requirements.
> You can use this to remotely manage any type of server, i.e. a
> Domain Controller, Print Server, SQL server, Exchange server, etc.
>
> When you install the Terminal Services component, you turn the
> server into a "proper" Terminal Server. This enables multiple
> normal users to connect to the server and run their desktop
> applications on the server itself. You basically turn the server
> into a multiple-user desktop.
> It requires additional licensing (a TS CAL for every user or
> device). The number of connecting users is only limited by the
> number of licenses and the hardware.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> D...@HOTMAIL.COM wrote on 09 jul 2007 in
> microsoft.public.windows.terminal_services:
>
> > Hi,
> >>From windows components wizard, I see that I can add "Terminal
> >>Server"

> > component.
> > But I already has terminal service runing on the server by
> > default and people (limit is 2+1, isn't it?) can use remote
> > desktop to connect to this server.
> > Can someone tell me what I will get from adding this "terminal
> > server" component?

>
> > Many Thanks
> > Jerry
 
Before you go ahead and install Terminal Services, make sure to do
some reading, planning and testing.
Terminal Services itself is trivial to install, but it's not
trivial to install and manage applications and printers in a TS
environment.
Note that any applications that are currently installed on the
server will not work correctly in a multi-user environment. So if
you want to install Terminal Services, you must first uninstall all
user applications, then install TS, and then install the
applications again. The server has to be in "install mode" during
the installation, in order to capture changes to the registry and
make them available to multiple users.

You also have to think about performance. As far as I know,
MatLab, SPSS and Office are all resource-hungry applications.
Make sure that your server has the hardware to support the number
of concurrent users that you anticipate (and then some more...)
If users produce a lot of graphics in MatLab and SPSS and they are
connecting over a WAN link, then you have to check if the network
speed and latency allow for reasonably fast screen updates.

No, you cannot assume that an application which runs under Windows
200x runs in a Terminal Services environment.
The challenge is the multi-user support. The application must be
Terminal-Services aware and be able to handle multiple instances of
the application running on the same server, with separate
configurations for all instances.

Here are some starting points:

How Terminal Services Works
http://technet2.microsoft.com/WindowsServer/en/library/2cb5c8c9-
cadc-44a9-bf39-856127f4c8271033.mspx?mfr=true

Checklist: Plan your Terminal Server deployment
http://technet2.microsoft.com/WindowsServer/en/Library/2ff3d1b1-
1af2-48c8-b266-e10914a593051033.mspx

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

DAXU@HOTMAIL.COM wrote on 10 jul 2007 in
microsoft.public.windows.terminal_services:

> Hi,
> Thanks for your reply.
> I am thinking of make this server an application server so that
> users who has the access right to this machine will be able to
> use these softwares.
> Are there any compatiability issues with software(such as
> office, spss, matlab etc)? Is it right for me to assume that if
> an application can run under windows 2003/2000, then it will be
> able to run under this windows terminal server (basically just a
> windows 2003 with terminal service component installed)?
> Many thanks
> Jerry
>
> On 9 Jul, 16:34, "Vera Noest [MVP]" <vera.no...@remove-
> this.hem.utfors.se> wrote:
>> What you are using now is Remote Desktop for Administration,
>> which is limited to 2 + 1 connections, by default only
>> available for Administrators, and withour extra licensing
>> requirements. You can use this to remotely manage any type of
>> server, i.e. a Domain Controller, Print Server, SQL server,
>> Exchange server, etc.
>>
>> When you install the Terminal Services component, you turn the
>> server into a "proper" Terminal Server. This enables multiple
>> normal users to connect to the server and run their desktop
>> applications on the server itself. You basically turn the
>> server into a multiple-user desktop.
>> It requires additional licensing (a TS CAL for every user or
>> device). The number of connecting users is only limited by the
>> number of licenses and the hardware.
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> D...@HOTMAIL.COM wrote on 09 jul 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Hi,
>> >>From windows components wizard, I see that I can add
>> >>"Terminal Server"
>> > component.
>> > But I already has terminal service runing on the server by
>> > default and people (limit is 2+1, isn't it?) can use remote
>> > desktop to connect to this server.
>> > Can someone tell me what I will get from adding this
>> > "terminal server" component?

>>
>> > Many Thanks
>> > Jerry
 
Back
Top