Loading...

Knowledge Center


Access Protection Policy content no longer displays in ePolicy Orchestrator after deploying the VirusScan Enterprise 8.8 Patch 5 or Patch 6 extension
Technical Articles ID:   KB84913
Last Modified:  4/7/2017
Rated:


Environment

McAfee ePolicy Orchestrator (ePO)
McAfee VirusScan Enterprise (VSE) 8.8 Patch 5 and Patch 6 extension

Problem

Access Protection Policy content no longer displays in ePO after deploying the VSE 8.8 Patch 5 or Patch 6 extension to a non-C: volume.

Cause

If ePO is installed on a volume where the 8.3 naming convention has been disabled, the VSE 8.8 Patch 5 or Patch 6 extension will not display Access Protection content.

ePO 5.x is supported on volumes where 8.3 (8.3 filename creation) is disabled; however, the VSE 8.8 Patch 5 or Patch 6 extension has an issue that causes the described symptom when 8.3 naming is disabled.

Solution

This issue is resolved in VSE 8.8 Patch 7. Patches are cumulative; Technical Support recommends that you install the latest one.

{VSE88PATCHES.EN_US}

Workaround

Perform the following steps to re-install the extension.

{GENRD.EN_US}

Preserve your current data
WARNING: McAfee strongly recommends that you back up your ePO server before you perform the steps in this workaround. This procedure removes product extensions, resulting in a total loss of any configured policies and tasks. Verify that your backup strategy allows for restoration, and that the policies and tasks exported below include all items that will be lost when the extensions are removed.
  1. Back up the ePO server.
  2. Verify your backup.
  3. Enable 8.3 on the volume where ePO is installed.
    Use the following fsutil.exe commands to Query and Enable 8.3 Per Volume on Windows 6.2+, where 'X:' is the volume where ePO is installed:
    • fsutil.exe 8dot3name query X:
    • fsutil.exe 8dot3name set X: 0
       
  4. Verify that 8.3 is now set to ENABLED for the volume where ePO is installed (regardless of the configuration of 8.3 on other volumes):
    1. Navigate to the following registry location:
                          
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
       
    2. Check the value of NtfsDisable8dot3NameCreation

      The ideal setting is either '0' or '2' where the volume setting for 'X:' is '0'.
       
  5. Restart the server.
  6. Export any policies and tasks for VSE-dependent products such as VSE for Storage, VSE for Offline Virtual Images, and VSE for SAP.
  7. Export the VSE 8.8 policies and tasks, the assignments for each, and any custom VSE queries.
  8. Verify all required policies and tasks, and any other content that will be lost as a result of extension removal, are present in the exports.

Remove and re-install the extensions
  1. Remove the extensions for any VSE-dependent products.
  2. Remove the VSE 8.8 Patch 5 or Patch 6 extension.
  3. Re-install the VSE 8.8 Patch 5 or Patch 6 extension.
  4. Install the extensions for any VSE-dependent products.
  5. Import the VSE 8.8 policies and tasks.
  6. Import any policies and tasks for VSE-dependent products.

Workaround

Enable 8dot3NameCreation on the drive where ePO was installed.

NOTE: This applies if NtfsDisable8dot3NameCreation has an existing value of '2' or a newly configured value of '0.'

This should not be attempted if 8dot3 enabled shortnames are already in use on the drive in question. Use the DIR /X command if you are uncertain whether or not 8dot3 enabled shortnames are currently in use.
  1. Stop the ePO services.

    IMPORTANT: If you do not stop the ePO services, you will see Access Denied messages when you attempt the setshortname commands below. You may also need to disable the ePO services and reboot the system to avoid any file locks.
     
  2. Run the following commands from an elevated command prompt, using the drive letter that hosts the ePO installation directory (example shown below as X:):

    fsutil.exe 8dot3name set X: 0
    fsutil file setshortname "X:\Program Files (x86)" PROGRA~2
    fsutil file setshortname "X:\Program Files (x86)\McAfee\ePolicy Orchestrator" EPOLIC~1
    fsutil file setshortname "X:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\VIRUSCAN8800" VIRUSC~1
    fsutil file setshortname "X:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\VIRUSCANREPORTS" VIRUSC~2
    fsutil file setshortname "X:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software\Current\BOCVSE__1000" BOCVSE~1

    NOTE: The last entry will exist only if a current Buffer Overflow DAT is already checked in to the Master Repository.
     
  3. Start the ePO services.

Workaround

Enable 8.3 names, move the VSE extensions directory to another location, and then replace it.
  1. Stop the ePO services.
  2. Open a command prompt as an Administrator and run the following command (example shown below as X:):

    fsutil.exe 8dot3name set X: 0
     
  3. Move the X:\Program Files (x86)\McAfee\ePolicy Orchestrator\Server\extensions\installed\VIRUSCAN8800\ directory to another location, and then move it back again.

    This will create the 8dot3 name automatically. This solution has resolved the issue during McAfee internal testing without the need to move the other above-mentioned directories.
     
  4. Start the ePO services.
 

Disclaimer

The content of this article originated in English. If there are differences between the English content and its translation, the English content is always the most accurate. Some of this content has been provided using Machine Translation translated by Microsoft.

Rate this document

Did this article resolve your issue?

Please provide any comments below

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

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