Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Archiving and eDiscovery Community Blog
Showing posts tagged with Installation
Showing posts in English
StephenConnolly | 05 Jul 2012 | 0 comments

If you are using User Account Control (UAC) in your desktop environment, Windows Installer will request that you elevate an installer. The elevation request typically comes at the end of the installation wizard interview, just before the main installation transaction starts. 

Tthe Enterprise Vault Add-In Installer has to perform some specific operations that require the installation to be elevated at the start of the installation wizard. For this reason the installer will check to see whether UAC is enabled and whether elevation has already taken place. If UAC is enabled and the installer has not been elevated it will show the following message and quit with an error:

You cannot install the Symantec Enterprise Vault Outlook Add-In by launching this MSI file directly. You must launch setup.exe. For more information, contact your administrator.

To help you work around this issue you can use the setup.exe alongside the MSI packages which...

StephenConnolly | 01 Dec 2011 | 5 comments

In September 2011 Enterprise Vault adopted a new Digital Certificate for signing files. This certificate's root certificate is Verisign Class 3 Public Primary Certification Authority G5. Most systems that have an internet connection will get this certificate via an automatic update, but if that doesn't happen then you will get an error like this in the installation log when you attempt to install the FSA agent on that system:

DIFXAPP: ERROR: Signature verification
failed while checking integrity of driver package 'evmf.inf'
('C:\EV_Install\drivers\evmf.inf').

If you check the MSI package's digital signature on the target file server, you will see that the root certificate cannot be found on the local system.

To address the problem you will need to install the new root certificate on the file server. For more details about how to obtain the certificate, see the...

StephenConnolly | 14 Oct 2011 | 0 comments

In line with best practice at the end of September 2011 the EV team deployed a renewed code signing certificate used for digitally signing files. The new certificate's trusted root may not present in the list of trusted root certificates of your Windows Server. In most cases Windows is able to automatically download and update the missing trusted root certificate without user intervention, but if your system is on a segregated network with no access to the DMZ or the automatic certificate update mechanism is disabled you may experience problems when validating signed files on the target system.

In most cases the problem is no worse than that you will get an error 'The issuer of this certificate could not be found' when you inspect the digital signature of the signed file and view the corresponsing certificate's Certification Path.

In the case of the FSA Agent the problem is worse, as the installation will fail on x64 systems when it attempts...