Mcafee EPO Server Problem no Protection Policy visible (blank/empty)

by butsch 12. August 2015 22:15

 

Mcafee EPO Server Problem no Protection Policy visible (blank/empty)

 

After Upgrade to Version 5.3 and installed EPO to non c: drives and you did not enable 8.3 for that drive

After upgrade of a VSE product first time after you installed new EPO to non c: drives and you did not enable 8.3 for that drive

 

When you view the VSE Access Protection policy within the ePO console, the policy appears to be blank. This is because the manual only says to check and enable 8.3 naming convention on c: drives and forgets to mention other drives?

 

 

 

 

 

Check your drives where you have installed EPO binaries:

The Volume state is: 0 < This is how it should look

 

Here is how to change it and reboot.

 

fsutil.exe 8dot3name set d: 0 

 

 

Happens also if you upgrade to VSE 8.8 PATCH 5 AND you are a smart guy who installs EPO Binaries on D: like they teach you. (And not on c: because all that grows goes on D: ;-)

 

* Enable 8.3 Naming Convention (Short) for the Disk you have EPO Path installed and reboot did the trick ( fsutil.exe 8dot3name set d: 0 )

* Export all Policies and Assignments!!

* Remove Extension for VSE 8.8 Patch 5

 

 

* Download 8.8 patch 5 Repost and extract Extension files (two) from www.mcafee.com

* Import Extension from VSE 8.8 Packages (VIRUSCAN8800(392).zip, VIRUSCAN8800(392).zip)

 

* Import your exported Policies

 

 

 

 

 

 

DO NOT FORGET to import and EXPORT POLICIES, you will lose them if remove the VSE Extension!

 

 

 

Environment

McAfee ePolicy Orchestrator (ePO) 4.x, 5.0, 5.1

McAfee VirusScan Enterprise (VSE) 8.8 patch 4 and 5

 

 

Problem

When you view the VSE Access Protection policy within the ePO console, the policy appears to be blank.

 

An Administrator cannot modify the existing (default) Access Protection policies.

 

Cause

 

ePO was installed to a drive other than the C: drive on the local system. The ePO Extensions for VSE rely on the existence of the VSCAN.bof content file to display the necessary policy information. The file must be located in one of the following ePO directories:

 

<Drive:>\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software\Current\BOCVSE_1000\DAT\0000\

 

or:

 

<Drive:>\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\BOCVSE_1000\DAT\0000\

 

 

Solution from Mcafee

Perform a Master Repository pull in ePO and ensure that the option to check for Access Protection and Buffer Overflow content is selected. This will place the necessary content file in the required location.

 

Tags:

Comments are closed

Werbung von Drittfirmen (Nicht Butsch Informatik):

Werbung von Drittfirmen via Google Adsense: