Deploying Office XP on Windows Terminal Services

Microsoft® Windows NT® 4.0 Terminal Server and Terminal Services–enabled Microsoft Windows® 2000 Server provide a thin-client solution for Windows-based programs. Terminal Server and Terminal Services run applications and display the application's user interface on a client computer. For example, users who have computers with limited disk space, memory, or processing speed can connect to a Terminal Services computer and use Microsoft Office XP applications as if the applications were running on the local computer.


 Note    Installation of Office XP on a Terminal Services–enabled system requires the use of the Application Server mode configuration. A computer configured for Remote Administration mode is not recognized by Office XP Setup; Office XP will install as if it were being installed to a generic workstation.

Also, it is recommended to use Windows 2000 compatibility mode for Terminal Services when installing to a Windows 2000 server to preserve a locked-down state of the registry.


How Office XP works with Terminal Services

With Terminal Services, you can install a single copy of Office XP on a Terminal Services–enabled computer. Then, instead of running Office locally on a single user's computer, multiple users connect to a server and run Office from there.


 Note    With Office XP, you are no longer required to use a special transform to install Office on a Terminal Services–enabled computer, or on a Windows NT 4.0 Terminal Server computer. Office XP Setup detects that it is being run under Terminal Services and preconfigures all the proper options. For this detection to occur on Windows 2000 Server, Application Server mode must be enabled.


The following is an overview of how Office XP works with Terminal Services:

  1. The administrator installs a single copy of Office XP on the Terminal Services computer using the Application Server mode configuration.
  2. Users install Windows Terminal Services Client on their computers.
  3. Users log on to the Terminal Services computer remotely through the Terminal Services Client software and run Office from the server.

The Office applications run on the Terminal Services computer, and only the user interface is transmitted to users’ computers across the network.

In the Terminal Services environment, Office XP separates application and user data and uses environmental information supplied by Terminal Services. This arrangement allows multiple Terminal Services Client users to run Office from the same Office installation.

To improve performance in the Terminal Services environment, Office optimizes specific configuration options in Office applications during installation to reduce the amount of network traffic necessary to update the user’s display. For example, in the Terminal Services environment, Office applications display a text-based splash screen instead of the standard graphics-based screen because the text-based screen is faster to display.

How to install Office XP on a Windows server with Terminal Services

You install Microsoft Office XP on a Terminal Services–enabled Windows 2000 server, or on a Windows NT 4.0 Terminal Server computer, in much the same way that you install Office on a client computer. Some planning and customizations will help Office perform well in the Windows Terminal Services environment.

To run Office XP in a Terminal Services environment, follow these basic steps:

1. Install Office on the Terminal Services computer.

2. Set default Office application settings for Windows Terminal Client users.

3. Configure Microsoft Outlook® 2002.


 Note    If you are installing Office XP on a Windows 2000 computer, you must enable Terminal Services before running Office Setup. Setup needs to detect that Terminal Services is enabled in order to configure the installation automatically for that environment.


Install Office on the Terminal Services computer

To install Office on a Terminal Services computer, you first log on to the server with administrative privileges. Then you run Office Setup using the network administrative installation point or the Office XP CD as the source.

To install Office on a Terminal Services–enabled Windows 2000 server

  1. In Control Panel, double-click Add/Remove Programs.
  2. Click Add New Programs in the left pane, and then click CD or Floppy in the right pane.
  3. Insert the Office CD into the CD drive, and then click Next.

— or —

If you are installing from a network server, click Next and then enter the location of the administrative installation point for Office. If you have created a transform for your customizations, include it on the command line (for example, TRANSFORMS=MyTransform.mst).

  1. Click Finish to run Office Setup.

To install Office on a Windows NT 4.0 Terminal Server computer

  1. In Control Panel, double-click Add/Remove Programs, click Install, and then click Next.
  2. Click Browse.
  3. In the root folder of the Office CD, select setup.exe, and then click OK.

— or —

If you are installing from a network server, enter the location of the administrative installation point for Office, and then click OK. If you have created a transform for your customizations, include it on the command line (for example, TRANSFORMS=MyTransform.mst).

Setup.exe is added to the Command line for installation program box.

  1. On the command line, you can optionally add the following command after setup.exe, separated by a space:
/l* "%WINDIR%\Office XP Setup(0001).txt"

This command places the Setup log file in the Windows folder, rather than in the Temp folder, so that the log file is not deleted automatically by Windows.

  1. Click Next.
  2. Select All users begin with common application settings, and then click Next to run Office Setup.

 Important    When you install Office XP on a Windows NT 4.0 Terminal Server computer, you must use Add/Remove Programs in Control Panel with the All users begin with common application settings option selected. This setting runs Setup in Install mode, which installs Office for all Terminal Server Client users who connect to the Terminal Services computer.


Running Office in a Terminal Services environment is different from running it on a user’s computer. When you install Office on a Terminal Services computer, the users who connect to the server are limited to your Office configuration and cannot install or remove features (providing the registry remains locked down and they do not have administrative privileges).

In other words, all users running Office from a Terminal Services computer inherit the features selected during installation. If your users need different feature sets of Office functionality, you will need a separate Terminal Services server for each configuration.

Because of the multiuser nature of Terminal Services–enabled computers, Office XP Setup by default installs all features to one of the following installation states:

  • Run from My Computer

Most features are set to this state because they work well in the Terminal Services environment. Features that normally default to Installed on First Use are set to Run from My Computer.

  • Not Available

Features set to this state typically use additional animation or sound that generates excess data traffic between the Terminal Services computer and the Terminal Services Client computer. It is recommended to leave these features set to Not Available to maintain an optimized configuration.

If you want to accept the default Office configuration, you do not need to modify the Setup feature tree. However, if there are Office features that are not needed by any users, you can improve overall performance and conserve disk space by customizing the installation so that Office Setup does not install these features on the Terminal Services–enabled computer.

Set default Office application settings

To improve performance in a Terminal Services environment, you can customize the default Office user settings for all users logging on to the Terminal Services computer. You can change any of the existing default settings to the settings you need for your requirements; however, for optimal performance you should allow minimal use of animations and sounds.


 Note    By default, Menu Animations are disabled. Even though the Menu Animations combo box can be selected and users or administrators can select entries in the list box, the selected changes have no effect.


Customize Office settings

Consider making the following recommended changes to Office application settings. These changes should improve performance of Office XP by reducing network traffic, reduce system load on the Terminal Services server, and increase the possible number of users of the Terminal Services–enabled server. You can disable menu commands only through System Policy settings. For more information, see the How to Set System Policies topic in the Maintenance section of the Office Resource Kit.

Microsoft Outlook 2002

In this dialog box Change this setting
Tools | Options | Mail Format tab Clear the Use Microsoft Word to edit e-mail messages check box.
Tools | Options | Preferences tab | E-mail Options | Advanced E-mail Options Clear the Play a sound and Briefly change the mouse cursor check boxes.

Microsoft Access 2002

In this dialog box Change this setting
Tools | Customize Remove the Detect and Repair command from the Help menu.

Microsoft Excel 2002

In this dialog box Change this setting
Tools | Customize Remove the Detect and Repair command from the Help menu.
Tools | Options | Edit tab Clear the Provide feedback with animation check box.

Microsoft PowerPoint 2002

In this dialog box Change this setting
Tools | Options | General tab | Web Options | General tab Clear the Show slide animation while browsing check box.
Tools | Customize Remove the Detect and Repair command from the Help menu.
Tools | Options | Spelling and Style tab Clear the Check spelling as you type check box.

Microsoft Word 2002

In this dialog box Change this setting
Tools | Customize Remove the Detect and Repair command from the Help menu.
Tools | Options | Spelling and Grammar tab Clear the Check grammar as you type check box.
Default Office settings with Terminal Services

When you install Office XP on a Terminal Services server, Office Setup automatically changes the default settings for the following options. To improve performance, you should leave these options as Setup has configured them.

Microsoft Access 2002

In this dialog box Setup changes this setting
Tools | Customize | Options tab Sets Menu animations to (System default).
Tools | Options | General tab Clears the Provide feedback with sound check box.

Microsoft Excel 2002

In this dialog box Setup changes this setting
Tools | Customize | Options tab Sets the Menu animations option to (System default).
Tools | Options | General tab Clears the Provide feedback with sound check box.

Microsoft FrontPage 2002

In this dialog box Setup changes this setting
Tools | Customize | Options tab Sets the Menu animations option to (System default).

Microsoft Outlook 2002

In this dialog box Setup changes this setting
Tools | Customize | Options tab Sets the Menu animations option to (System default).
Tools | Options | Other tab | Advanced Options Clears the Provide feedback with sound check box.
Tools | Options | Mail Format tab Clears the Use Microsoft Word to edit e-mail messages check box.
Tools | Options | Preferences tab | E-mail Options Clears the Display a notification message when new mail arrives check box.

Microsoft PowerPoint 2002

In this dialog box Setup changes this setting
Tools | Customize | Options tab Sets the Menu animations option to (System default).
Tools | Options | General tab Clears the Provide feedback with sound to screen elements check box.
Tools | Options | General tab | Web Options | General tab Clears the Show slide animation while browsing check box.

Microsoft Word 2002

In this dialog box Setup changes this setting
Tools | Customize | Options tab Sets the Menu animations option to (System default).
Tools | Options | General tab Clears the Provide feedback with sound check box.

Distribute customized Office Settings to users

You can use the following to customize settings for Terminal Services users:

  • The Office XP Custom Installation Wizard
  • The Office XP Profile Wizard
  • The Office XP Custom Maintenance Wizard
  • Windows System Policies
Using the Office XP Custom Installation Wizard

If you install Office on a Terminal Services server from an administrative installation point, you have the option of using the Office XP Custom Installation Wizard to create a transform to hold the customized settings. You then install Office on the Terminal Services server by using that transform. All Office users who log on to the Terminal Services server receive the customized settings you defined in the transform.

Note, however, that any files added to the transform are not propagated to all users on a Terminal Services–configured server. All files added by using the Add/Remove Files page of the Custom Installation Wizard, as well as any files included in an Office Profile Wizard OPS file added to the transform — such as Normal.dot — are not propagated to each user.

To add files to an installation of Office XP so that all users receive a copy of the files, use the Office XP Custom Maintenance Wizard after Office XP is installed. Files added with the Custom Maintenance Wizard are installed as each user logs on to the Terminal Services computer and runs any Office application for the first time.


Toolbox     The Office XP Resource Kit includes the Custom Installation Wizard and the Custom Maintenance Wizard, which are installed by default when the Office Resource Kit Setup program is run. For more information, see Custom Installation Wizard in the Toolbox.


Using the Office XP Profile Wizard

You can install Office on a test computer, configure user options, and then save those options to an OPS file by using the Office Profile Wizard. You can then use the Office Profile Wizard to apply those changes by having each user of the system run the Office Profile Wizard with the OPS file you created. Each user is required to apply the settings in the OPS file to their profiles, or they will not receive the customizations.


Toolbox     The Office XP Resource Kit includes the Office Profile Wizard, which is installed by default when you run the Office Resource Kit Setup program. For more information, see Office Profile Wizard in the Toolbox.


Using the Office XP Custom Maintenance Wizard

You can configure Office after you have installed it on the Terminal Services computer by using the Custom Maintenance Wizard. When users log on to the Terminal Services computer and run an Office application for the first time, they receive your customized settings.


Toolbox     The Office XP Resource Kit includes the Custom Maintenance Wizard, which is installed by default when you run the Office Resource Kit Setup program. For more information, see Custom Maintenance Wizard in the Toolbox.


Using Windows System Policies

An additional method for configuring Office for users is to use Windows System Policies. Using the System Policy Editor or the Group Policy snap-in with the Office policy templates included in the Office Resource Kit, you can configure user options and then distribute those policies to users or groups within your network. Each time a user runs an Office application on the Terminal Services computer, the user’s options are configured according to the policies.


Toolbox     The Office XP Resource Kit includes the System Policy Editor and Office policy templates, which are installed by default when you run the Office Resource Kit Setup program. For more information, see System Policy Editor and Templates in the Toolbox.


Configure Microsoft Outlook 2002

To complete the installation of Microsoft Outlook 2002, you may need to provide write access to a portion of the Windows registry.

By default, Windows Terminal Services clients do not have write access to the registry on a Windows Terminal Services computer. To run some Outlook features, you might need to give users write access to some branches or keys. For example, to allow users use of custom MAPI forms for Outlook 2002, unlock the HKEY_CLASSES_ROOT\CLSID branch of the tree.

To give users write access to registry keys for Outlook

  1. Log on to the Terminal Services computer as the administrator.
  2. Click Start, and then click Run.
  3. Type regedt32.exe, and then click OK.
  4. To allow users to use custom MAPI forms, in the HKEY_CLASSES_ROOT window select CLSID.
  5. On the Security menu, click Permissions.
  6. In the Registry Key Permissions dialog box, select the Replace Permission on Existing Subkeys check box, and then click Add.
  7. In the Name box , click Everyone, click Add, and then click OK.

If you do not want to give all users this access, you can add specific users or groups of users in the Names box, rather than selecting Everyone.

  1. In the Type of Access box, select Special Access, and then select the Query Value, Set Value, and Create Subkey check boxes.
  2. Click OK and close the Registry Editor.

 Note    If you want Terminal Services users to use Outlook as a newsgroup reader, you must perform the additional step of running Outlook once on the server from an administrator account after installing Office. This allows Outlook to modify the necessary system resources that are normally unavailable to Terminal Services users. Without this step, Terminal Services users will encounter an error if they click a News: link on a Web page.


Related links

For more information about how to install a customized version of Office, see Installing and Customizing Office.

For more information about configuring Office after you install it, see Maintaining an Installation.

 
 
Applies to:
Deployment Center 2003