Re: Using remote desktop and terminal services

The whole idea with a Terminal Server is that it functions as a
multi-user workstation.
So your users start their Remote Desktop client on their
workstations (comes with XP, so they probably already have it
installed), and they all connect to the same Terminal Server.
They will all work on the server without being aware of each other,
in totally separated sessions.

Note that setting up a Terminal Server and installing applications
on it is not a trivial task, because of the multi-user
functionality.
For one thing, you must install Terminal Services *before* you
install the application, so if it is already installed on the
server, you'll have to uninstall the application first, then
install TS, then install the application again.
Installing applications for multi-user access must be done while
the server is in "install mode", to guarantee that each user gets
its own private settings.

When you run a Terminal Server for multi-user access, you will also
need to install a Terminal Services Licensing Server, and buy and
install TS CALs on it (the exact requirements depend on the OS on
the clients as well as the workstations).

You might want to do some more reading first:

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

Technical Overview of Windows Server 2003 Terminal Services
http://www.microsoft.com/windowsserver2003/techinfo/overview/termse
rv.mspx
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFya3Vz?= <Markus@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
13 nov 2006 in microsoft.public.windows.terminal_services:

I have an app that will slow down if run over a WAN, and would
like to use Terminal Services instead. Am a beginner to this,
so hope someone can help here.

My most important question is - If this app is planned to be
used by 5 users, and if I use Terminal Services, does this mean
I will need to run Remote Desktop on the 5 remote user machines,
and also have 5 computers at the server side to connect to to
run the app? Or is there a way for each remote user to connect
to the server directly and run the app without a computer for
each?

Thanks in advance for any ideas on this,
Mark
.

Relevant Pages

  • Re: Terminal Server with SBS 2K3
    ... when a normal user logs on the terminal server ... have enough permission to install and uninstall printer drivers. ... If the printer driver for Windows 2003 server is not ...
    (microsoft.public.windows.server.sbs)
  • Re: Changing from App mode to Remote Admin mode via registry
    ... applications on the terminal server. ... Remote admin mode is simply activated by going ... Microsoft MVP - Terminal Server ... We'd like to do this because our application doesn't install right now in ...
    (microsoft.public.windows.terminal_services)
  • The local policy of this system does not allow you to log on inter
    ... I also checked "Deny Logon Locally" and nothing is configured. ... I am trying to logon to the Terminal Server ... I have added the group Domain Users to the Builtin Group Remote Desktop ...
    (microsoft.public.windows.terminal_services)
  • Re: Changing from App mode to Remote Admin mode via registry
    ... You can detect if your application is running in a remote ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Remote Administration mode for a Win2K3 terminal server without ... users not to install from a remote session? ...
    (microsoft.public.windows.terminal_services)
  • RE: The local policy of this system does not allow you to log on inter
    ... If the server is a 2003 Member Server, then the only things required for RDP ... Member of the local Remote Desktop User's Group, or a group with User & ... Users do NOT require the logon locally right for 2003 TS, ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)