There are many known issues related to running Microsoft Outlook with Windows Terminal Server.
Outlook features that do not work include the following:
- Offline store (OST) files and features that rely on the OST (i.e., Cached Exchange and Offline mode, client side Junk E-mail filtering)
- Forms Designer and the Microsoft Visual Basic Scripting Edition (VBScript) editor.
- You can view a custom form, but you cannot design a new form or revise an existing form.
- Changing the Time Zone from within Outlook as the time zone is a system setting.
- Changing Zone security settings from within Outlook as this is a system setting.
- Changing the status of a Microsoft Exchange Client Extension. If the extension is enabled by default, it should work correctly.
- Adding stationery that was not included with Outlook as part of the Terminal Services installation.
- Outlook animations, such as Send/Receive animation and the Search Folder creation icon, are disabled.
Outlook 2007 | Outlook 2003 | Outlook 2002 | Outlook 2000
Outlook 98 | Outlook 97 | More Information
Outlook 2007
Outlook 2003
- Considerations when Installing Outlook in a Terminal Services Environment
- Error Message When You Start Outlook 2003 by Using a Terminal Services Client
Outlook 2002
If you install Outlook 2002 on a machine that is running Terminal Services, the setup program does not copy a file that Outlook needs to run custom forms. You can fix this problem by copying Outlvbs.dll from a non-terminal server Outlook 2002 machine to the Office10 directory of system running Terminal Services. Also see:
- OL2002 Custom MAPI Forms Do Not Work on Terminal Server
- OL2002 Terminal Server Clients Cannot Connect to an Exchange Server
- OL2002 Word Is Not the Default E-mail Editor on Terminal Server
Outlook 2000
- OL2000 Installing Outlook to Run from Terminal Server
- OL2000 (IMO): Outlook IMO on Terminal Server Is Unsupported
- OL2000 Failure When Opening a Form on Windows NT 4.0 and WINNT Terminal Server – Fixed in SR-1/1a
- Windows 2000 Terminal Services Does Not Support Outlook Offline Storage
- OL2000: ODBC Import-Export Does Not Work on Terminal Server
- OL2000: Can Not Import ECCO on Windows Terminal Server
- OL2000: Unable to Open a Shared .pst File Without a Password
- OL2000: All Users Are Forced to Use Schedule+ as Calendar on Terminal Server
- OL2000: Can Not Mix Users and Distribution Lists In a Net Folder Invitation
- OL2000: Default Profile Name is the Microsoft Windows Terminal Server Administrator’s Name
- OL2000: Error Message The Form You Selected Could Not Be Displayed Using Terminal Server
- OL2000: MAPI Error Message When a Novell WordPerfect Document Is Sent Using Microsoft Outlook
- OL2000 Switching from Corporate or Workgroup to Internet Mail Only Mode Causes Outlook to Stop Responding
- OL2000 Cannot Run the Spelling Checker in Another Language on Terminal Services
- OL2000 The Create New Word Document Option Is Not Available
Outlook 98
- OL98 Troubleshooting Microsoft Outlook ’98 on Windows Terminal
- Outlook 98 May Install Incorrectly on Windows NT Terminal Server
- Non-Administrator Terminal Server Users Do Not Have Access to Internet E-Mail in Outlook 98
Outlook 97
- OL97: New Terminal Server User Receives Someone Else’s Profile
- Allowing Users to Select an E-Mail Editor For Outlook 97
More Information
Options Set in Outlook Are Not Used from the Send To Menu
Using Microsoft Exchange Forms with Terminal Server
Error- “No Transport Provider” Trying to Send Mail in Terminal Server
Cannot Insert File Attachment From Locally Mapped Drive to Outlook Messages
Terminal Server Client Cannot Perform ‘Send To-Mail Recipient’ Action If Outlook Is Not Already Started
STOP 0×00000050 Error Message in Windows Terminal Server
Terminal Server User Profiles Do Not Unload Resulting in Loss of Settings
Articles that may interest you:
Last reviewed on Dec 2, 2011


Hot Topics