OL98: Troubleshooting Outlook on Windows Terminal Server 4.0

ID: Q230654

The information in this article applies to:

Microsoft Outlook 98

SUMMARY

Outlook can be configured to run on Microsoft Windows Terminal Server, however there are some special considerations. Use the following to help determine where to start troubleshooting Outlook on Windows Terminal Server:

On new installations, you must ensure that the Windows Terminal Server is in Install mode during the installation, and the application compatibility script must be run immediately following installation.

For existing installations, determine whether the installation works correctly for the administrator, while logged on locally. You should also create a new user in User Manager, to see if it is a problem with an existing user profile or System Policies.

Some features of Outlook do not work while using Windows Terminal Server. Check the "Missing Outlook Functionality" section for more information.

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:

Q186498 Terminal Server Application Integration Information

Q192678 Add/Remove TS Client Requires Original Installation Point

Q195014 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 have installed Office 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 Compatability Script

Before starting, download the application compatability script from the following location:

http://www.microsoft.com/ntserver/downloads/bin/terminalserver/cs_outlook.exe

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


%systemroot%\application compatibility scripts\install

for example:


C:\Winnt\application compatibility scripts\install

Msoutlk.key belongs in the following folder


%systemroot%\application compatibility scripts\install\template

for example:


C:\Winnt\application compatibility scripts\install\template

Outlkusr.cmd belongs in the following folder


%systemroot%\application compatibility scripts\logon\template

for example:

C:\Winnt\application compatibility scripts\logon\template

Double click the Outlkusr.cmd file to start the application compatibility script.

As you run the script, you may be prompted to modify the Rootdrv2.cmd file. The following message is displayed:

Before running the application compatibility script, you must designate a drive letter to be mapped to each user's home folder. Update the "Set RootDrive" statement at the end of the Rootdrv2.cmd file to indicate the desired drive letter.

If you have no preference, the drive W: is suggested.

For example: Set RootDrive=W:

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.

Once the compatability scripts have been run, to install Outlook, follow these steps:

Place the server in Install mode. From a command prompt, type:


Change User /install

Run Setup.exe from the installation media of Outlook.

When setup has completed, you may be prompted to reboot the server.

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:

Q169387 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:

Q190234 PRB: How to Modify the Personal Folder for All New Users

Q187144 Options Set in Outlook Are Not Used from the Send To Menu

Q219447 Logging on to Terminal Server Shows Someone Else's Accounts

Q137245 Cannot Open or Compose Message in Windows Messaging

Additional query words: 98, WTS Metaframe


Keywords          : kbdta 
Version           : WINDOWS:
Platform          : WINDOWS 
Issue type        : kbinfo

Last Reviewed: August 3, 1999