How to install Outlook on a Terminal Server

This article was previously published under Q222303
This article has been archived. It is offered "as is" and will no longer be updated.
This article describes special steps that need to be followed to successfully install Outlook on a Microsoft Terminal Server. This information is also contained in the Microsoft Office 2000 Resource Kit (ORK).
More information

Terminal Server Considerations

The Windows Installer, used to set up and configure programs and components of Office, uses a transform file to allow a network administrator to designate options and features that will be installed. Because the Terminal Server environment is different than the usual network environment, Microsoft has supplied a transform file to specifically handle the Terminal Server installation. If you attempt to use a customized transform not designated for use with Terminal Server, Office will not be installed

The transform file is named TermSrvr.mst and is available with the ORK. Although Termsrvr.mst can be customized to include options and features that you wish to make available to Terminal Server client users, modification of the TermSrvr.mst is not supported by Microsoft.

Special steps which a Terminal Server administrator should be aware are:
  1. Before any user runs Outlook on the Terminal Server computer, log on to the Terminal Server computer as the administrator.
  2. Run Outlook as the administrator. Remaining installation tasks are completed.
  3. Quit Outlook.
By default, users have write access to all portions of the Windows registry on the Terminal Server computer. However, if you have any custom Outlook forms installed on the computer, and you have configured the Windows registry on the Terminal Server computer to restrict user access, then you need to make sure that users have write access to the following registry key:

Using Custom Forms from a Terminal Server Client

Outlook registers custom forms the first time that they are opened, and this requires that the user have write access to this portion of the registry. To give users write access to the CLSID subkey, follow these steps:
  1. Log on to the Terminal Server computer as the administrator.
  2. Click Start, and click Run. Type regedt32.exe and click OK.
  3. Click to expand the HKEY_CLASSES_ROOT key, and then select CLSID.
  4. On the Security menu, click Permissions.
  5. In the Registry Key Permissions dialog box, select the Replace Permission on Existing Subkeys check box, and then click Add.
  6. In the Name box, click Everyone, click Add, and then click OK.NOTE: If you do not want to give all users this access, you can add specific users or groups of users in the Name box, rather than selecting Everyone.

  7. In the Type of Access box, select Special Access, and then select the Query Value, Set Value, and Create Subkey check boxes. Click OK, and then on the File menu, click Exit to close the Registry Editor.
Complete information about installing Outlook 2000 in various configurations is available in the ORK and at the following Web site: For additional information about installing Office on a Microsoft Terminal Server, please see the following article in the Microsoft Knowledge Base:
217640Setup fails when installing Office 2000 on a Windows Terminal Server
For additional information about the Microsoft Office 2000 Resource Kit, please see the following article in the Microsoft Knowledge Base:
203953 Office Resource Kit is not available for download

Article ID: 222303 - Last Review: 12/05/2015 13:24:22 - Revision: 4.0

Microsoft Outlook 2000 Standard Edition

  • kbnosurvey kbarchive kbtermserv kbsetup kbinfo kbnofix KB222303