This article was previously published under Q302003
If you are using Microsoft Outlook in a Terminal Services environment, you cannot use Visual Basic Scripting Edition (VBScript) in custom Outlook forms. This issue can occur when you are using Microsoft Windows NT 4.0 Terminal Server in Install mode or User mode. This issue also occurs with Windows 2000 Terminal Server in Application mode but not in Remote Administration mode.
By default, Microsoft Office XP, Microsoft Office 2003, and 2007 Microsoft Office programs do not install the VBScript component in Windows Terminal Server environments.
Use one of the following methods to work around this problem.
Method 1: Copy the Outlvbs.dll file to existing installations
To do this, follow these steps:
Copy the Outlvbs.dll file from a computer that is not running Microsoft Outlook on a Terminal Server.
Copy the Outlvbs.dll file to the Program Files\Microsoft Office\Office10 folder of the affected Terminal Server computer.
Note If the Terminal Server is running Microsoft Office 2003, copy the Outlvbs.dll file to the Program Files\Microsoft Office\Office11 folder.
Method 2: Use the Custom Installation Wizard to deploy Microsoft Office with an additional property to let the VBScript component to be installed
To do this, follow these steps:
Open the Custom Installation Wizard, and then create a new transform (.MST) file for the Microsoft Office installation.
Configure your installation requirement in the Custom Installation Wizard.
On the last available page of the Custom Installation Wizard, click Modify Setup Properties, and then add the following property name and value:
Note Both the property name and the value are case sensitive.
For Office XP, Modify Setup Properties is on page 21 of 22 of the Custom Installation Wizard. For Office 2003, Modify Setup Properties is on page 23 of 24 of the Custom Installation Wizard.
To enable VB Script support for Outlook forms when running Outlook 2007 on a Terminal Server computer, do the following:
Install Outlook 2007 as a standalone application or as part of a 2007 Office suite.
Determine the globally unique identifier (GUID) for the product that you just installed. If you installed Outlook, use that product GUID. If you installed Office Enterprise 2007, use that product GUID. For more information about how to determine the GUID of the product that you installed, click the following article number to view the article in the Microsoft Knowledge Base:
928516 Description of the numbering scheme for product code GUIDs in 2007 Office suites and programs
After you have the product GUID, run the following command line:
msiexec /i <Product Code GUID of [SKUName]WW.msi> ADDLOCAL=OutlookVBScript /qb
Note In this command, <Product Code GUID of [SKUName]WW.msi> is a placeholder for your product GUID.
For example, if you have Office Enterprise 2007 installed, your product GUID would be the following:
Therefore, the command line should appear as follows:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Microsoft Office and Outlook Setup detect when you are installing Outlook on a computer configured with Terminal Services. In these situations, the support files necessary to enable VBScript in Outlook custom forms are not installed. Therefore, if you try to start the Outlook Script Editor, you receive the following error message:
Unable to load this feature. Feature ID not registered.
If you try to use a custom Outlook form that contains VBScript, you do not receive an error message, but the VBScript code in the form does not run.
Note Earlier versions of Outlook supported VBScript in a Terminal Services environment.
For more information about available resources and answers to commonly asked questions about Microsoft Outlook solutions, click the following article number to view the article in the Microsoft Knowledge Base:
287530 Frequently asked questions about custom forms and Outlook solutions