OL98: Troubleshooting Outlook on Windows Terminal Server 4.0 (230654)

MORE INFORMATION

If this is a new installation Outlook on Windows Terminal Server, and it does not function as expected, then it is likely that the correct installation procedures for Outlook were not followed. The following is designed to be a quick guide for installing Outlook on Windows Terminal Server:

Guidelines for Installation

• Installation should be performed from the console of the Windows Terminal Server, not from a client session.
• The person performing the installation needs to be logged on with an account with Administrative Rights.
• Whenever any software is installed, or configuration changes are made, make sure all users are logged off the system. Microsoft recommends that you disable client sessions while you are installing or configuring the server.
  
  For additional information about setting up programs on Windows Terminal Server, please see the following articles in the Microsoft Knowledge Base:

  186498 Terminal Server Application Integration Information

  192678 Add/Remove TS Client Requires Original Installation Point

  195014 Outlook 98 May Install Incorrectly on Windows NT Terminal Server

If you did not install Microsoft Internet Explorer 4.0 as part of the installation of Windows Terminal Server, install it and run its application compatibility script before you install Outlook.

NOTE: Do not add the Active Desktop component.

If you are installing Outlook and intend to use Microsoft Office 97, you must have Office installed as a shared application using the Change User utility, and the appropriate application compatibility script. You should also verify that all of the programs and features needed with Office are functioning properly as shared programs.

To Run the Application Compatibility Script

Before starting, download the application compatibility script from the following location: The downloaded file is a self-extracting file named CS_outlook.exe. Double-click CS_outlook.exe to extract the files, and then manually move them to the following locations:

Msoutlk.cmd belongs in the following folder: Msoutlk.key belongs in the following folder: Outlkusr.cmd belongs in the following folder: Double click the Msoutlk.cmd file to start the application compatibility script.

As you run the script, you may receive the following message that prompts you to modify Rootdrv2.cmd: NOTE: Make sure there are no spaces after the drive letter and colon.

When you have completed this task, save the file and quit NotePad to continue running the application compatibility script.

To Install Outlook

If you attempt to install Outlook without following all of these guidelines, it may be necessary to uninstall and then reinstall Office, and Outlook.

To install Outlook, use one of the following to enter and use Install mode on the Terminal Server client:

1. Click Start, point to Settings, click Control Panel, and then click Add/Remove Programs.

   -or-

2. Click Start, point to Programs,click Command Prompt, and then type Change User /install. This returns the server to its default running state.

To install Outlook on Terminal Server, follow these steps:

1. Run Outlook Setup. Once installation is complete, do not allow Setup to restart the system.
2. While still in Install mode, run the Msoutlk.cmd Application Compatibility script. This script optimizes the Windows registry settings and other variables for the multiuser environment. All scripts are located in the following folder on the server:

   %systemroot%\Application Compatibility Scripts\Install\

   where %systemroot% is the drive letter of your Terminal Server where the Windows NT system is installed. When running the Office Compatibility script a drive needs to be selected which is the first of 3 consecutive free drive letters. Drive W is recommended.
3. Restart your computer. Additional scripts, and information on how to write application scripts can be found at:

   http://www.microsoft.com/ntserver/terminalserver/exec/vendors/showcase/

Troubleshooting Outlook Configurations

If Outlook or a feature of Outlook was working previously, the first step is to determine whether the problem is specific to clients, or to the entire installation. The easiest method is to run Outlook while logged on to the console of the server as the administrator.

If Outlook does not run properly while logged on as the administrator, then use the same troubleshooting resources that you would use to troubleshoot an installation of Outlook on your computer.

If everything works correctly while you are logged on as the administrator, then perform the following test:

In User Manager, select the user account that is not working, and temporarily make the account part of the Account Operators group. This allows the account to log on locally to the Windows Terminal Server. Test the functionality of Outlook for this user. If you experience the problem at the console while logged on as the user, then the issue is most likely related to one of the following areas:

• The System Policies are too restrictive. To determine this, create and test a new account using User Manager and make sure that this account does not belong to any groups that have policy restrictions.
• The user's profile is damaged, or not set up correctly. Create a new user account, and log on with this account. This tests the new profile.
• NTFS file permissions are not set up properly.
  
  For additional information about NTFS file permissions, please see the following article in the Microsoft Knowledge Base:

  169387 Security Requirements When Using NTFS Partitions

Missing Outlook Functionality

Some features of Outlook do not function as expected, or have special considerations when used with Windows Terminal Server.

For additional information about Outlook features not available in Windows Terminal Server, please see the following articles in the Microsoft Knowledge Base: