Re: Using remote desktop and terminal services
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Nov 2006 12:38:47 -0800
You're welcome, Mark.
Good luck with your testing, and feel free to come back here if you
need further assistance.
_________________________________________________________
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
17 nov 2006 in microsoft.public.windows.terminal_services:
Vera,.
Thanks and thanks again for all the details. Think all is clear
now for me to go forward.
Mark
"Vera Noest [MVP]" wrote:
Terminal Services and TS Licensing Service are core components
of Windows 2003 Server. So you don't have to obtain a special
trial version of TS, it's already there on any Windows 2003
Server. You just install both from Control Panel - Add/Remove
programs - Add Windows components.
And no, you do not have to upgrade your clients to get the rdp
client, it's downloadable for free:
http://www.microsoft.com/downloads/details.aspx?familyid=80111f2
1- d48d-426e-96c2-08aa2bd23a49&displaylang=en
Better still, install the client which is included in your
Windows 2003 server. You'll find it in
C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi
When you install Terminal Services on a 2003 server, it will
allow you to run without any TS Licensing Server for a period
of 120 days. This is called the grace period.
After 120 days, the TS *must* be able to contact a TS Licensing
Server, so you must install that. Then, if you haven't bought
any TS CALs yet, the TS Licensing Server starts to issue
temporary licenses to clients. These temporary licenses last
for 90 days. When the temporary licenses expire, the show is
over, meaning that you then *must* buy and install TS CALs to
be able to connect to your TS.
So that gives you a total period of 120 + 90 days to test and
evaluate Terminal Services.
_________________________________________________________
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 16 nov 2006 in microsoft.public.windows.terminal_services:
Vera,
Many thanks for the help and explanation. I see where I can
get a trial versoin of Server 2003 for 180 days. If I
already have XP SP2 Home on the workstations, will I need to
upgrade to XP Pro to get the Remote Desktop client on the
workstations?
Just one more - If I get the trial version and wish to test
out the app, sounds like I can install it on one machine and
use XP workstations to test out multiuser capabilities. But
am confused about the Terminal Services Licensing Server TS
Cals. Sounds like I will also need this in order to test out
multiuser access with the app - did I understand that
correctly, and do you know if there is a trial version I can
obtain to do my testing?
Many thanks again for all your help,
Mark
"Vera Noest [MVP]" wrote:
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/2ff3d1
b1- 1af2-48c8-b266-e10914a593051033.mspx
Technical Overview of Windows Server 2003 Terminal Services
http://www.microsoft.com/windowsserver2003/techinfo/overview/
ter mse 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
- References:
- Re: Using remote desktop and terminal services
- From: Vera Noest [MVP]
- Re: Using remote desktop and terminal services
- From: Markus
- Re: Using remote desktop and terminal services
- From: Vera Noest [MVP]
- Re: Using remote desktop and terminal services
- From: Markus
- Re: Using remote desktop and terminal services
- Prev by Date: Re: serving individual apps
- Next by Date: Re: Need Multithreaded?
- Previous by thread: Re: Using remote desktop and terminal services
- Next by thread: Re: Using remote desktop and terminal services
- Index(es):
Relevant Pages
|
