We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Message Archiver

How to Enable Barracuda Archive Search for Outlook in a Microsoft Terminal Server Environment

  • Last updated on

If you are using Windows Defender Antivirus, you must disable the Block Office applications from creating child processes policy to use Archive Search for Outlook.

This article refers to the Barracuda Message Archiver firmware 5.2 or higher, and the Barracuda Archive Search for Outlook version 5.2 or higher. Barracuda Archive Search for Outlook supports Outlook versions 2010, 2013, 2016, and 2019.

Verify the Archive Search for Outlook version (available for download on the USERS > Client Downloads page in the Barracuda Message Archiver web interface) is the same major revision as the Barracuda Message Archiver firmware for proper functionality.

By default Microsoft Office 2010, 2013, and 2016 do not install the VBScript component in Windows Terminal Server environments. For this reason, if you are running a copy of Outlook 2010, 2013, and 2016 in a Windows Terminal Server with remote users connecting to the server to run Outlook, users may encounter an error similar to the following when using the Barracuda Outlook Add-In with Outlook 2010, 2013, and 2016 running in this environment:

Contact your Terminal Services Administrator for more information on your organization's setup.

For additional information, refer to the Microsoft Support article Forms with VBScript do not work with Terminal Services in Outlook.

You can use the following methods to work around this issue and to enable Archive Search for Outlook.

Method 1: Copy the Outlvbs.dll File to Existing Installations

Use the following steps to copy the Outlvbs.dll file to existing installations:

  1. Log onto a computer that is running a full, standalone version of Microsoft Office.
  2. Copy the file Outlvbs.dll from the folder:
    • For Microsoft Office 2010, copy the file from  Program Files\Microsoft Office\Office14
    • For Microsoft Office 2013, copy the file from Program Files\Microsoft Office\Office15
    • For Microsoft Office 2016, copy the file from Program Files\Microsoft Office\Office16
  3. Log onto a computer that is running Microsoft Outlook from the Terminal Server, and is encountering the form scripting error.
  4. Paste the file Outlvbs.dll from step 2 to the folder:
    • For Microsoft Office 2010, paste the file into the folder Program Files\Microsoft Office\Office14  
    • For Microsoft Office 2013, paste the file into the folder Program Files\Microsoft Office\Office15
    • For Microsoft Office 2016, paste the file into the folder Program Files\Microsoft Office\Office16  

Method 2: Custom Installation Wizard

Use the following steps to use the Custom Installation Wizard to deploy Microsoft Office 2010, 2013, or 2016 with an additional property to let the VBScript component to be installed.

  1. Log onto the Microsoft Terminal Server, and Install Microsoft Outlook 2010, 2013, or 2016 as a standalone application or as part of an Office suite.
  2. Determine the globally unique identifier (GUID) for the product that you installed in Step 1. If you installed Outlook, use that product GUID. If you installed Office Enterprise, use that product GUID.

  3. After you have the product GUID, at a command line, run the following command:

    msiexec /i <Product Code GUID of [SKUName]WW.msi> ADDLOCAL=OutlookVBScript /qb

    Where <Product Code GUID of [SKUName]WW.msi> is your product GUID.

    For example, if your GUID is: {90120000-0030-0000-0000-0000000FF1CE}

    The command line should appear as follows: msiexec /i {90120000-0030-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript

Determine the GUID
Depending on the installed version of Microsoft Outlook, you may need to check the registry to determine which GUID to put in place so that the Barracuda Outlook Add-In installs properly. The string you need to use with the msiexec command is located in the following registry path:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\<GUID here>

Enter the GUID to the command: 

msiexec /i <GUID here> ADDLOCAL=OutlookVBScript /qb

Examples by Version
Microsoft Office Standard 2010

msiexec /i {90140000-0012-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Microsoft Office Basic 2010

msiexec /i {90140000-0013-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Microsoft Office Professional 2010

msiexec /i {90140000-0014-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Microsoft Office Enterprise 2010

msiexec /i {90140000-0030-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Microsoft Office 2013 Standard x86

msiexec /i {90150000-0012-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Microsoft Office 2013 Pro Plus x64

msiexec /i {90150000-0011-0000-1000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Microsoft Office 2016 Standard x86

msiexec /i {90160000-0012-0000-0000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb

Microsoft Office 2016 Pro Plus x64

msiexec /i {90160000-0011-0000-1000-0000000FF1CE} ADDLOCAL=OutlookVBScript /qb  

 

 

 

 

 

Last updated on