
File name Log type Location Description
<ExtensionFileName>
.cmd
Temporary
%temp%\McAfeeLogs
\ePO500
‑troubleshoot
\OutputFiles
Created by the ePolicy Orchestrator
installer. Contains the command
(sent to Remote‑Client) to check in
extensions.
If the installation succeeds,
these files are deleted.
MFS500‑CommonSetup.log
Installation
%temp%\McAfeeLogs
Contains MFS installer details.
Server logs
Server log files contain details on server functionality and various administrator services used by
ePolicy Orchestrator.
File name Log type Location Description
EpoApSvr.log
Primary
[InstallDir]\DB
\Logs
Application Server log file with details of
repository actions such as:
• Pull tasks
• Checking in deployment packages to the
repository
• Deleting deployment packages from the
repository
This file is not present until after initial service
startup.
Errorlog
.<CURRENT
_DATETIME>
Apache
[InstallDir]
\Apache2\logs
Contains Apache service details.
This file is not present until after the Apache
service is started for the first time.
Eventparser
.log
Primary
[InstallDir]\DB
\Logs
Contains ePolicy Orchestrator event parser
services details, such as product event parsing
success or failure.
Jakarta
_service
_<DATE>.log
Tomcat
[InstallDir]
\Server\logs
*
Contains ePolicy Orchestrator Application Server
service details.
This file is not present until after the initial
Tomcat service startup.
Localhost
_access_log
.<DATE>.txt
Tomcat
[InstallDir]
\Server\logs
*
Records all McAfee ePO server requests received
from client systems.
This file is not present until after the initial
Tomcat service startup.
Orion.log
Primary
[InstallDir]
\Server\logs
*
Contains McAfee Foundation Services platform
details and all extensions loaded by default.
This file is not present until after the ePolicy
Orchestrator Application Server service is
started for the first time.
Troubleshooting and log file reference
Log files for troubleshooting
6
McAfee ePolicy Orchestrator 5.1.0 Software Installation Guide
61
Komentáře k této Příručce