Terminal Services Basics

Hi All,

Hope someone can help with a basic question. It's probably been
covered many times, but I can't find anything substantial or
definitive...

Looking at Terminal Services on Windows Server 2003/Citrix
Presentation Server 4.5 for the first time. I'm uncertain of the
correct sequence of actions to build a farm.

There will be multiple servers, but only running Office and one or two
other (low intensity) applications.

The most logical sequence to *me* is

- establish "infrastructure" (licensing, data store, etc)
- install Windows Server 2003 SP2
- install and customise the applications
- test the applications (eg with a standard user account using Remote
Administration)

Once all the glitches and refinements have been identified,
- clone the server using WDS and SYSPREP
- on the imaged servers,
- join the domain
- install Terminal Services/Citrix Presentation Server
- publish the applications/desktop

Our organisation tends to refresh the desktop image annually (bunching
together all the software updates into a new image revision). My
sequence above would allow us to do this for our Terminal Services/
Citrix environment in a similar way (at the moment, it's extremely
difficult to make ANY change to the servers!)

Other guidance on the Internet suggests
- install Windows Server 2003 SP2
- patch
- install Terminal Services/(Citrix Presentation Server?)
- install applications (after switching to install mode)
- test the applications
- clone (if you dare!)
- either package up the applications and distribute across the farm,
or install manually

My approach seems far, far simpler; install once, clone, replicate
with 100% fidelity.

Some of you will no doubt be bewildered by the breathtaking level of
ignorance I'm showing... I'd love some URLs on what I SHOULD be
doing, and WHY (preferably according to Microsoft and Citrix)

Kind regards,

Anwar
.

Relevant Pages

  • Re: Using remote desktop and terminal services
    ... workstations, will I need to upgrade to XP Pro to get the Remote Desktop ... But am confused about the Terminal Services ... Licensing Server TS Cals. ... you must install Terminal Services *before* you ...
    (microsoft.public.windows.terminal_services)
  • Re: newbie question about terminal server
    ... Before you go ahead and install Terminal Services, ... trivial to install and manage applications and printers in a TS ... server will not work correctly in a multi-user environment. ...
    (microsoft.public.windows.terminal_services)
  • Re: Symantec System Center
    ... Yes this product is supported in a server environment. ... I am trying to install the SSC included with my ... >>> Symantec System Center installation on server operating systems ... Terminal Services' options are all ...
    (microsoft.public.windows.server.sbs)
  • Re: Using remote desktop and terminal services
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... You just install both from Control Panel - Add/Remove ... When you install Terminal Services on a 2003 server, ... the TS *must* be able to contact a TS Licensing ...
    (microsoft.public.windows.terminal_services)
  • Re: terminal server on windows 2000 allows only 2 sessions
    ... the choice between Remote Administration and Application Server ... go to Terminal Services Configuration - Server Settings - Licensing ... However, when you install in Application Server mode, you need to ...
    (microsoft.public.win2000.termserv.apps)
Quantcast