Problem
Veritas provides client support for Citrix based thin client provisioning. This support is limited to the installation and use of the Enterprise Vault client for Outlook, excluding Vault Cache or Virtual Vault. Support for Vault Cache and Virtual Vault is included only if the criteria specified in the Enterprise Vault Compatibility List are satisfied.
Veritas does not currently support any aspect of its Enterprise Vault server infrastructure provisioned via Citrix.
The Enterprise Vault (EV) client can be made available to users with Terminal Services; however, there are some outstanding issues to be aware of.
Error Message
- Microsoft Outlook 2016
The following errors are generated:
Cannot enable support for scripting. The functionality is not available.
Microsoft Office Outlook cannot provide form scripting support. This feature is not available.
Solution
Outlook 2016:
VBScript support for Outlook forms is not allowed by default on a Terminal Service installation. This default setting cannot be changed or added using the add-remove program wizard.
To obtain the GUID of the installed package and then install the VB Script functionality, perform the following:
- Verify the product name from Add/Remove programs or the Help > About menu
Open the registry, browse to:
For 32-bits OS version:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\Uninstall
For 64-bits OS version:
HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall- Identify the GUID as per Microsoft KB 928516 (e.g. {90120000-0030-0000-0000-0000000FF1CE} )
Office 2016 - https://docs.microsoft.com/en-us/office/troubleshoot/office-suite-issues/numbering-scheme-for-product-guid
- From command prompt, enter the following syntax: It is case sensitive.
msiexec /i {GUID.EN_US} ADDLOCAL=OutlookVBScript /qb
where {GUID.EN_US} is the string identified in step 3 above.
Examples for common versions of Office:
Note: There have been some instances reported where this did not resolve the problem. In those cases delete the OUTLVBS.DLL file from the Microsoft Office installation folder and try running the MSIEXEC command again.