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 a Microsoft Windows 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 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.
Note Make sure that this computer and the Terminal Server are running the same version of Outlook when you copy the Outlvbs.dll file.
Copy the Outlvbs.dll file to the appropriate Office folder of the affected Terminal Server computer for your version of Office.
MSI-based installation: Program Files\Microsoft Office\Office16
Click-to-Run installation: Program Files\Microsoft Office\root\Office16
MSI-based installation: Program Files\Microsoft Office\Office15
Click-to-Run installation: Program Files\Microsoft Office 15\root\Office15
Office 2010: Program Files\Microsoft Office\Office14
Office 2007: Program Files\Microsoft Office\Office12
Office 2003: Program Files\Microsoft Office\Office11
Office 2002: Program Files\Microsoft Office\Office10
Note If your Operating system and Office version are not the same bitness, the location will be 'Program Files(x86)'.
Important When you install an Outlook Update on the Terminal Server, the Outlvbs.dll file is not updated. Therefore, you must install the same update on the other computer and follow these steps to copy the Outlvbs.dll file to the Terminal Server every time an update is installed.
Method 2: Install Microsoft Office with an additional property to let the VBScript component to be installed
To do this, follow these steps:
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 Professional Plus 2010, 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:
3120274 Description of the numbering scheme for product code GUIDs in Office 2016 2786054 Description of the numbering scheme for product code GUIDs in Office 2013 2186281 Description of the numbering scheme for product code GUIDs in Office 2010 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:
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