After installing the September 2017 security patch for Outlook, Veritas Enterprise Vault shortcuts are no longer working.
This is a known issue which occurs after installing the security updates listed in the following KB articles.
- Outlook 2007
- Outlook 2010
- Outlook 2013
- Outlook 2016
This document describes the issues fixed by the following release update to Enterprise Vault 12.2: Enterprise Vault 12.2.1; Enterprise Vault 12.2.1 provides an updated version of the Veritas Quick Assist tool, which is launched by the Deployment Scanner when you choose to gather support information using the Gather information through Veritas Quick Assist option. Dears, I have created package for Symantec Enterprise Vault using below command. Msiexec.exe /i 'XXX.mxi' /qn REBOOT=ReallySuppress. It is working fine on Newly installed OS without EV. But when i tried to deploy on old version of EV machines, it. Hi all As some of you may be aware Enterprise Vault 11 shipped on the 5th May. The official announcement is available here.
After applying this update, custom form script is now disabled by default and requires setting registry keys to re-enable it.
To resolve the issue, take the following actions:
1. The new setting has a default value of 1, which indicates form script should not run. To allow the form script to run, first create the following key (if it does not exist).
2. Then create DWORD (32-bit) Value 0 and set the name to DisableCustomFormItemScript to enable custom form scripts.
3. Once custom form scripts have been enabled, they must then be allowed per form message class. For instance, if you have a form with the message class IPM.Note.Custom, we must register 'IPM.Note.Custom' as a trusted form message class. To do this, first create this key:
4. Then, create REG_SZ values in this key for each form you wish to allow scripts to run. In the above example, you would create a REG_SZ value named 'IPM.Note.Custom' with empty data.
Please Note: The registry key will be different depending on the office version / build and the OS build (64bit vs. 32bit). Below are the registry keys that were provide by Veritas required to resolve this for each supported configuration.
Outlook 2010:
EVClient_OL2010_x64_Win_x64:
EVClient_OL2010_x86_Win_x64:
Access Enterprise Vault Outlook
EVClient_OL2010_x86_Win_x86:
Outlook 2013:
Enterprise Vault Outlook Download
EVClient_OL2013_x64_Win_x64:
EVClient_OL2013_x86_Win_x64:
EVClient_OL2013_x86_Win_x86:
Outlook 2016:
Outlook Enterprise Vault
EVClient_OL2016_x64_Win_x64:
EVClient_OL2016_x86_Win_x64:
EVClient_OL2016_x86_Win_x86:
Fixes or workarounds for recent issues in Outlook for Windows
https://support.office.com/en-us/article/Fixes-or-workarounds-for-recent-issues-in-Outlook-for-Windows-ecf61305-f84f-4e13-bb73-95a214ac1230
Custom form script is now disabled by default
https://support.office.com/en-us/article/Custom-form-script-is-now-disabled-by-default-bd8ea308-733f-4728-bfcc-d7cce0120e94
Email retrieval fails after installing Security Patch for Outlook 2010, 2013 and 2016
https://www.veritas.com/support/en_US/article.000127958