Loading...

Knowledge Center


Considerations when using a third-party deployment solution to install VirusScan Enterprise
Technical Articles ID:   KB79568
Last Modified:  7/27/2017
Rated:


Environment

McAfee VirusScan Enterprise (VSE) 8.x

For details of VSE 8.x supported environments, see KB51111.

Summary

This article outlines the requirements that must be met when considering the use of a third-party deployment solution (not ePolicy Orchestrator) to install VSE. The main considerations are:
  • What files are needed
  • Using SetupVSE.exe to install the product
  • Using the (.MSI) file to install the product

Required files
The VSE installation files are contained within the initial (.zip) file that is downloaded, for example VSE880LMLRP4.zip.

NOTE: To help identify the package contents, the naming convention is: [Product][Version][License|Eval][Multi-Lingual][Repost][Patch level].zip

The (.zip) file contains the following files needed for installation of the product:
Filename Description
SetupVSE.exe, Setup.ini The installation launcher that orchestrates the installation phases.
UnInst.exe (Uninstx64.exe), Uninst.ini The universal uninstaller, which checks for incompatible software.
VSE880.msi 1 The core of the installation; an install package built with MSI technology.
vcredist_x64.exe, vcredist_x86.exe A redistributable package from Microsoft that ensures required runtime components are installed on the system.
WindowsInstaller-KB893803-v2-x86.exe A redistributable package from Microsoft that ensures required runtime components are installed on the system.
MSIStrings.bin A UI support file.
 
1 IMPORTANT: VSE 8.8 Patch 8 and later include constraints that prevent the execution of the .MSI or .MSP packages to install or upgrade VSE. This constraint was added because the packages cannot perform actions included in the installer, such as installation prerequisite checks to block installation on incompatible environments. Customers on earlier versions of VSE (pre VSE 8.8 Patch 8) are strongly advised not to use the MSI package for the same reasons it was removed in VSE 8.8 Patch 8.
The following is extracted from the VSE 8.8 Patch 8 Release Notes (PD26631):
 
Using (.MSI) or (.MSP) to start VirusScan Enterprise is now blocked and produces this error message: "You must use SETUPVSE.EXE or SETUP.EXE to start VirusScan Enterprise installation"

Solution

Using SetupVSE.exe to install the product  (VSE 8.8 Patch 8 and later)
NOTES:
  • This is the only option with VSE 8.8 Patch 8 and later due to the constraints that prevent the execution of the .MSI or .MSP packages to install or upgrade VSE.
  • The installer must be invoked with Administrator (or System) credentials. Also, the files listed above must be available and accessible to the SetupVSE.exe process when it is invoked.
The product development team recommends that you run SetupVSE.exe to install the product, for the following reasons:
  • It leverages a universal uninstaller, which contains logic to check for incompatible software that is on the system, and removes it.
  • It invokes other requisites that may be detected as missing from the system.

Solution

Using the .MSI file to install the product (VSE 8.8 Patch 7 and earlier only)
The product development team does not recommend this installation method because of inherent limitations with how the .MSI file is built. You can use this method if you first meet the following requirements:
  • All incompatible software has been removed from the target system. If not, you will potentially have incompatible products installed that will conflict and cause unpredictable issues. For example, your computer might become unresponsive, or enter a state that requires booting to Safe Mode to recover.
  • The MSI file has been prepared by importing the MSIStrings.bin (see KB79567).
NOTE: The installer must be invoked with Administrator (or System) credentials. With this approach there should be no need for the additional installation files.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Languages:

This article is available in the following languages:

English United States
Japanese

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.