Forms with VBScript do not work with Terminal Services in Outlook

Method 1: Copy the Outlvbs.dll file to existing installations

1. 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.
   
   
2. Copy the Outlvbs.dll file to the appropriate Office folder of the affected Terminal Server computer for your version of Office.
   
   • Office 2016:
     
     • MSI-based installation: Program Files\Microsoft Office\Office16
     • Click-to-Run installation: Program Files\Microsoft Office\root\Office16
   • Office 2013:
     
     • 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

1. 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
   
   
2. After you have the product GUID, run the following command line:
   
   
   msiexec /i <Product Code GUID> ADDLOCAL=OutlookVBScript /qb
   
   Note In this command, <Product Code GUID> is a placeholder for your product GUID.
   
   For example, if you have Office Professional Plus 2016 installed, your product GUID would be the following:
   
   {90160000-0011-0409-0000-0000000FF1CE}
   
   In this example, the command line should appear as follows:
   
   msiexec /i {90160000-0011-0409-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb