Thursday, March 4, 2010

Installation

Windows Server 2000

You start the installation of Terminal Services through
Start - Control Panel - Add/Remove programs - Add/Remove Windows components
Select "Terminal Services". You will be offered a choice between:
  1. Terminal Services in Remote Administration mode
    This mode gives you a maximum of 2 simultaneous connections to the server, without additional licensing requirements. Designed for Administrators, to access the server remotely. By default, only Administrators can access a server in Remote Administration mode.
  2. Terminal Services in Application Server mode
    This is the "real" thing: allows for multi-user access, limited only by the number of Terminal Services Client Access Licenses (TS CALs) and your hardware.
    When asked which compatibility mode you want, be sure to choose "Permissions compatible with Windows 2000 Users".

Windows Server 2003

With the introduction of 2003, terminology for Terminal Services has changed. What was called "Terminal Services in Application Server mode" on W2K is now simply called "Terminal Services".
What was called "Terminal Services in Remote Administration mode" on W2K is now called "Remote Desktop for Administration". This mode is already pre-installed, and has only to be enabled. This is done in

Start - Control Panel - System - Remote
To install Terminal Services (implying: in Application Server mode - for multi-user access), go to:
   Start - Control Panel - Add/Remove programs - Add/Remove Windows components
  • Select "Terminal Services"
  • When asked which compatibility mode you want, be sure to choose "Full Security"
  • Accept the default settings for the Internet Explorer Enhanced Security Configuration
  • (preventing Administrators from downloading files or running ActiveX controls from the Web, and allowing users to do so)
  • Add your users to the Remote Desktop Users group on the Terminal Server

Automating installation

It's perfectly possible to automate the installation of Terminal Services. You can install it together with the base OS through an unattended installation, or later, as a scripted installation of a Windows Component. Both methods will require an answer file.

Here's how:

Inplace upgrade

I am not a fan of inplace upgrades of OSes. In fact, I've never done it. Upgraded servers tend to experience more problems, which can be hard to pinpoint. Moreover, if you experience a problem on an upgraded server which does not occur on a clean installation of the OS, it will be difficult to get support (other than the advice to perform a clean installation).

If you are planning to perform an inplace upgrade from SBS2000 or W2K to (SBS) 2003, be sure to read this (and then think again :-)

  • 939087 - You experience problems when you upgrade a Windows 2000-based server that has Terminal Server enabled to Windows Server 2003
  • 828056 - A terminal server no longer runs in application mode after you upgrade the terminal server to Windows Small Business Server 2003

Installing Remote Desktop Web Connection

Once you have installed Terminal Services, you can choose to let your users connect to the Terminal Server through their Internet Explorer webbrowser, in stead of with the Remote Desktop Client. You'll need a server which runs IIS, this can be the same server as the TS or a separate webserver.

On the webserver, install the Remote Desktop Web Connection as follows:
   Start - Control Panel - Add/Remove programs - Add/Remove Windows components   
Click Application Server - Details
Select Internet Information Services - Details
Subcomponents of IIS - World Wide Web Service - Details
Subcomponents of WWW Service - Remote Desktop Web Connection
Click OK three times
Windows Components wizard - Next
Connection types - RDP-Tcp connection - Next
This will install the latest version of the TSweb files. By default, the files will be copied to:
   C:\WINDOWS\Web\TSWeb

More information:

Windows Server 2008

What was called "Terminal Services (implied: in Application Server mode) on a Windows 2003 server is now called the Terminal Server role service on a Windows 2008 server.

No comments:

Post a Comment