Loading...

Knowledge Center


8.3 naming convention should be enabled on the ePolicy Orchestrator server
Technical Articles ID:   KB51431
Last Modified:  10/20/2016
Rated:


Environment

McAfee ePolicy Orchestrator (ePO) 5.x

Problem

ePO installation is blocked when the installation path contains extended characters, and the standard 8.3 naming convention is disabled.

Problem

The Installation Auditor tool flags the ePO server as having the 8.3 naming convention disabled. 

Cause

ePO no longer requires the 8.3 naming convention to function properly; however, many point product extensions still use 8.3 paths. The 8.3 naming convention should be enabled on the ePO server to avoid future problems. 

Solution

Enable the 8.3 naming convention on the ePO server.

NOTE: Installation to a path that failed before 8.3 naming was enabled will still fail to that same path. Point the installation to a new directory path, because 8.3 naming support is added to that path by default when enabled.
 
To enable the 8.3 naming convention:
  1. Click Start, Run, type regedit, and click OK.
  2. Navigate to, and select, the following registry key:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
     
  3. Right-click NtfsDisable8dot3NameCreation, and select Properties or Modify (depending on your version of Windows).
  4. Modify the Value data from 1 to 0.

    NOTE: On Windows Server 2008 the default value is 2; you must change it to 0.
     
  5. Restart your computer.
  6. Verify the 8.3 naming convention is enabled on the drive:
    1. Click Start, Run, type cmd, and click OK.
    2. Type the following command and press ENTER:

      dir /x.

      You should see that folders now have a column for short names, for example, Progra~1 for Program Files
       
    3. Type exit and press ENTER.
Now you can install ePO to a new directory.

Solution

Alternatively, use FSUTIL.EXE to change the value of the NtfsDisable8dot3NameCreation key.
 
Click Start, Run, type the appropriate command for your specific operating system, and then click OK:
  • On Windows Server 2008 or earlier: fsutil.exe behavior set disable8dot3 0
  • On Windows Server 2008 R2 or later: fsutil.exe 8dot3name set 0

Previous Document ID

613859

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.