Knowledge Center

How to enable debug logging for Drive Encryption Go
Technical Articles ID:   KB73165
Last Modified:  8/2/2017


McAfee Drive Encryption (DE) 7.2.x
McAfee Drive Encryption GO (DEGO) 7.1.x

For details of DE supported environments, see KB79422.


Use this article to enable debug level log files when you are troubleshooting an issue with DEGO  Logging levels are controlled on the client by either the command line or the registry on Windows clients, and only via the registry on the ePolicy Orchestrator (ePO) server. Debug logging produces significantly more log entries, whether or not there is an error. This allows for more granularity. 
IMPORTANT: Because debug logging generates so many more entries, ensure you disable the debug levels after the issue has been reproduced and the details captured in the logs.
CAUTION: This article contains information about opening or modifying the registry.
  • The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
  • Before proceeding, Technical Support strongly recommends that you back up your registry and understand the restore process. For more information, see: http://support.microsoft.com/kb/256986.
  • Do not run a REG file that is not confirmed to be a genuine registry import file.


Enabling debug logging on the client
The diagnostic information in the client Eego.log file has a similar format to the MfeEpe.log, with levels of Error, Warning, Info and Debug. The log information at Info level shows a basic trace of pings and tests. At Debug level, it shows all data and messages sent to and from the client with detailed traces of each test.
You can use either the registry or the command line to control and configure the logging level on the client.
Option 1: Change the logging level via the registry
The following registry entry is created at installation to allow the McAfee Agent to report that DEGO is installed:

NOTE: DEGO was formerly known as EEGO with Endpoint Encryption for PC (EEPC); the registry keys for DE still refer to EEPC.

32-bit systems 
HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Application Plugins\EEGO____1000\

64-bit systems
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Network Associates\ePolicy Orchestrator\Application Plugins\EEGO____1000
  • When the registry key is used, the setting is reread at service startup, to collect/send and enforce policies.
  • LoggingLevel [DWORD] values are 0 - 4.
DWORD value
Errors only
Warning and Errors only
3 Information, Warning and Errors
4 Debug, Information, Warning and Errors

To enable debug logging:
  1. Click Start, Run, type regedit, and then click OK.
  2. Locate the required registry keys (32-bit/64-bit):

    HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Application Plugins\EEGO____1000\

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Network Associates\ePolicy Orchestrator\Application Plugins\EEGO____1000

  3. Right-click the REG_DWORD entry LoggingLevel and select Modify (create the entry if it does not exist).
  4. In the Value data box, type 4.
  5. Click OK.  
    The Eego.log will be produced in: <installation directory>\EEGo\Eego.log 
To disable  debug logging:
  1. Delete the LoggingLevel key.
  2. Modify the LoggingLevel key value to 0. 

Option 2: Change the logging level via Command Line (Client)

  • If the command line option is given, then that level is used regardless of the registry key setting.
  • If a command line option is not given, then the registry key level is used (if present).
  • If the command line option is not given and the registry key is not present, then logging defaults to off.
Service Command line parameters:
  • -logging-none,
  • -logging-error,
  • -logging-warning
  • -logging-info
  • -logging-debug


Enabling debug logging on the ePO server
The log information at debug level shows all data and messages sent to and from the server. Debug level messages are added to the ePO server's Orion.log.
To configure logging:
  1. Edit log-config.xml which is located under Server/conf/orion/log-config.xml.
  2. Add the following entries:

    <logger name="com.mcafee.eego">
        <level value="debug"/>
  3. Save the file. 
  4. Restart the ePO services:
    1. Click Start, Run, type services.msc, and then click OK.
    2. Right-click on each of the following Services and select Restart:

      McAfee ePolicy Orchestrator x.x.x Event Parser
      McAfee ePolicy Orchestrator x.x.x Application Server
      McAfee ePolicy Orchestrator x.x.x Server
    3. Close the Services window.

Rate this document

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.