Microsoft KB Archive/230654

= OL98: Troubleshooting Outlook on Windows Terminal Server 4.0 =

Article ID: 230654

Article Last Modified on 11/28/2000

-

APPLIES TO


 * Microsoft Outlook 98 Standard Edition

-



This article was previously published under Q230654



SUMMARY
Outlook can be configured to run on Microsoft Windows Terminal Server, however, there are some special considerations. To help determine where to start troubleshooting Outlook on Windows Terminal Server, use the following:
 * 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:

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:

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: <pre class="fixed_text">C:\Winnt\application compatibility scripts\logon\template

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:

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.

To install Outlook, use one of the following to enter and use Install mode on the Terminal Server client: <ol> Click Start, point to Settings, click Control Panel, and then click Add/Remove Programs.

-or-

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

To install Outlook on Terminal Server, follow these steps: <ol> Run Outlook Setup. Once installation is complete, do not allow Setup to restart the system.</li> 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.</li> 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/

</li></ol>

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.</li> 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.</li> 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

</li></ul>

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:

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

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

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

137245 Cannot Open or Compose Message in Windows Messaging

Additional query words: 98, WTS Metaframe compatability

Keywords: kbinfo KB230654

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.