Deploying Terminal Services

After you take the time to carefully plan Terminal Services deployment in the enterprise, the installation can begin. After the planning phase of a Terminal Services deployment, the service and applications can be installed and configured and later tested by the IT personnel or a designated pilot group. After all functionality and applications are tested and verified, the Terminal Server can be released to the production end users or clients.

For the step-by-step instructions in the following sections, the desktop environment uses the Windows Server 2003 standard Start menu. To verify the Start menu is in this mode, perform the following steps:

1.	Right-click the Start button and click Properties.
2.	On the Start Menu tab, be sure that Start Menu is selected as shown in Figure 27.2 and click OK. Figure 27.2. Setting the system's Start menu.

Enabling Remote Desktop for Administration

Terminal Services Remote Desktop for Administration mode is installed on all Windows Server 2003 servers by default and only needs to be enabled. To enable this feature, follow these steps:

1.	Log on to the desired server with Local Administrator privileges.
2.	Click Start, right-click the My Computer shortcut, and then click Properties.
3.	Select the Remote tab, and under the Remote Desktop section, check the Allow Users to Connect Remotely to This Computer check box, as shown in Figure 27.3. Figure 27.3. Allowing users to connect to the system remotely.
4.	A Remote Sessions dialog box will open stating that accounts must not have blank passwords to use Remote Desktop; click OK to continue.
5.	Click OK in the Systems Properties page to complete this process.

Enabling Remote Assistance

To configure remote assistance, follow these steps:

1.	Log on to the desired server with Local Administrator privileges.
2.	Click Start, right-click the My Computer shortcut, and then click Properties.
3.	Select the Remote tab, and under the Remote Assistance settings, check the Turn On Remote Assistance and Allow Invitations to Be Sent from this Computer check box.
4.	Click the Advanced button to configure whether remote control will be allowed and also to set an expiration policy for remote assistance invitations as shown in Figure 27.4. Figure 27.4. Enabling a computer for remote control.
5.	Click OK in the Advanced window and click OK in the System Properties page to complete this process.

Remote assistance for domain computer accounts can be configured using Group Policy. The following two settings are located in Computer Configuration\Administrative Templates\System\Remote Assistance, as shown in Figure 27.5:

Figure 27.5. Group Policy administrative templates for remote assistance.

• Solicited Remote Assistance This particular setting contains the same options available in the Remote System property page, previously described in this chapter. Use this setting to configure remote assistance standards across multiple workstations and servers.

• Offer Remote Assistance This setting can be configured only using Group Policy. Offer Remote Assistance allows a predefined "helper" to request a remote assistance session from another workstation on the network. Enabling this setting still leaves the end user with the control to allow or decline a session and also to set the level of remote assistance allowed.

Installing Terminal Server Mode

To install Terminal Services in Terminal Server mode, a Terminal Server administrator can use the Configure Your Server Wizard as follows:

1.	Log on to the desired server with Local Administrator privileges.
2.	Insert the Windows Server 2003 CD in the CD-ROM drive and close any autorun pop-up windows that open.
3.	Click Start, All Programs, Administrative Tools, Configure Your Server Wizard, as shown in Figure 27.6. Figure 27.6. Selecting the Configure Your Server Wizard option.
4.	Click Next on the Welcome screen to continue.
5.	Verify that you have completed the steps as outlined on the Preliminary Steps page and click Next to continue.
6.	From the Server Role page, shown in Figure 27.7, select Terminal Server from the list and click Next to continue. Figure 27.7. Selecting to install Terminal Services on the Server Role page.
7.	On the Summary of Selections page, Install Terminal Server should be listed in the summary. If this is correct, click Next to continue.
8.	When a pop-up warning message states that the server will be restarted as part of the installation process, click OK to continue.
9.	After the system restarts, log in with the same account used to install the Terminal Server.
10.	After the logon process completes, Terminal Server Help appears with direct links to Terminal Server checklists. Close this window or minimize it to review information later.
11.	When you see the Configure Your Server Wizard message stating This Server Is Now a Terminal Server, click Finish to complete the installation.

Installing Applications for Terminal Server

Applications should be installed on a Terminal Server after the Terminal Server is installed. Applications that are installed prior to installing the Terminal Server may not function properly for all users.

Applications must be installed on Terminal Servers only when the server is in Application Install mode. An administrator can put the server into Install mode by opening Add/Remove Programs from the Control Panel or at the command prompt. After the application is installed, the administrator can simply close the Add/Remove Programs window or change the server back to Execute mode at the command line. Execute mode allows users to access and use the applications from Terminal Server sessions.

To change modes at the command prompt, type

• Change user /Install before installing an application

• Change user /Execute after installing an application

• Change user /Query to check which mode the server is currently running in

Several applications have special instructions for Terminal Server installations, whereas others require running application compatibility scripts. Microsoft has tested some third-party applications such as Eudora Version 4 to run on a Terminal Server, and it has provided the application compatibility script to run after installing that program on the Terminal Server. The provided compatibility scripts are located in %SystemRoot%\ Application Compatibility Scripts\install, where %SystemRoot% is the directory containing your operating system files. Consult your software manufacturer's documentation before deploying applications on a Terminal Server.