May 14, 1999

By using Microsoft Windows NT® Server version 4.0, Terminal Server Edition, you can take full advantage of Microsoft Office 2000 without having to upgrade every computer in your organization. Users can work with the latest productivity tools in Office 2000 even when their computers have limited disk space, memory, or processing speed.

Windows Terminal Server allows you to run Windows-based programs on a server and display them remotely on client computers. For example, you can install a single copy of Microsoft Outlook® 2000 on a Windows Terminal Server computer. Then, instead of running Outlook locally, multiple users can connect to the server and run Outlook from there.

Running Outlook 2000 in a Windows Terminal Server environment comes with some special requirements. First, you must use the transform TermSrvr.mst to install Office on the Terminal Server computer. Then, in the Custom Installation Wizard, you must choose features and installation options that work well in a Terminal Server environment.

Toolbox   The Office Resource Kit includes the transform Termsrvr.mst. Office Setup does not install Office on a Windows Terminal Server computer without this transform. To obtain Termsrvr.mst and other Terminal Server tools, install the Office Resource Kit (orktools.exe). You can find this downloadable file on the Office 2000 Resource Kit Downloads page.

Setting installation states

When you install Outlook 2000 (or any other Office 2000 application) on a Terminal Server computer, you must choose carefully which installation options you set for Office features. When you select options in the Set Feature Installation States panel of the Custom Installation Wizard, follow these guidelines:

• Set the Outlook features that you want to install to Run from My Computer.
• Set all other features to Not Available.
• Do not set any features to Run from Network, Run from CD, or Installed on First Use. These settings do not work in a Terminal Server environment.

For example, if you want to make the Proofing Tools available to Outlook 2000 users, you can use the Custom Installation Wizard to modify the TermSrvr.mst file and set the Proofing Tools to Run from My Computer.

Selecting Outlook features

Some features of Outlook 2000 do not work properly in the Windows Terminal Server environment, regardless of their installation state. When you select Outlook features to install, keep in mind the following:

• Use Outlook 2000 Calendar features and set Schedule+ features to Not Available.
• Set NetMeeting features to Not Available.

System Policy Tip   You can use a system policy to disable NetMeeting features. In the System Policy Editor, set the Microsoft Outlook 2000\Miscellaneous\NetMeeting, policy and then select the Disable all NetMeeting options and online meetings in Outlook check box. For more information, see Using the System Policy Editor in the Office 2000 Resource Kit.

The Outlook features you choose to install can also affect the performance of Windows Terminal Server. For example, to increase performance, you can set the Publish Calendar to the Web feature in Outlook 2000 to Not Available in the Custom Installation Wizard.

Unlocking registry settings

By default, Windows Terminal clients do not have write access to the registry on the Terminal Server computer. To run certain Outlook features, you might need to give users write access to some portions of the registry. For example:

• To use custom MAPI forms for Outlook 2000, unlock the subtree HKEY_CLASSES_ROOT\CLSID.
• To allow Outlook users running under Windows Terminal Server to directly book Schedule+ resources, unlock the subkey HKEY_LOCAL_MACHINE\Software\Microsoft\Schedule+ \Application.

Related links

For a complete description of how to customize TermSrvr.mst and install Office 2000 on a Windows Terminal Server computer, including more customizations for Outlook 2000, see Installing Office in a Windows Terminal Services Environment in the Office 2000 Resource Kit.