Resolution: The field’s label has been changed from “Return Address” to “From Address.” This more correctly identifies
the From Address field for customers.
59. Issue: Server task log allows deletion of both completed and active waiting tasks. (Reference: 364316)
Resolution: The purge function now purges only tasks that are in the following states: SUCCESSFUL, FAILED,
TERMINATED, and STOPPED.
60. Issue: Queries for dashboards fail if the default language used to access SQL is non-English. (Reference: 371826)
Resolution: SQL server now treats the string as ISO8601-compliant in time format, which provides accurate results in
any language.
61. Issue: Data exports from reporting to CSV format that include the IPV4 source or destination addresses are not being
converted correctly in the CSV export. (Reference: 374270)
Resolution: IPV4 addresses are now correctly exported in CSV formatted files.
62. Issue: When a query was exported via SMTP mail and the query name had HI-ASCII characters in it, the HI-ASCII
characters were dropped during the export in the attachment name. (Reference: 375097)
Resolution: HI-ASCII characters are now supported in attachments being sent through the email export feature. The
exported file name retains the HI-ASCII characters.
63. Issue: Server task corruption occurs in replication tasks with more than 80 individually selected SuperAgent
repositories. (Reference: 384144)
Resolution: The maximum length allowed by the SchedulerTaskAction class for command URIs has been changed from
4000 to 1073741823. This allows for a task with 1000 repositories.
64. Issue: Default server tasks that are not directly related to a plug-in are being marked as invalid (and cannot be
accessed through the user interface). (Reference: 385880)
Resolution: Server tasks are now checked to see if they are valid.
65. Issue: Connection objects were declared but never used. (Reference: 370991)
Resolution: The orphaned connection has been removed.
66. Issue: The Scheduler ran a task regardless of whether it was in a valid or invalid state. (Reference: 375327)
Resolution: Only valid tasks are allowed to be edited, viewed, run, or duplicated.
ePolicy Orchestrator 4.0 Patch 5 installation instructions
ePolicy Orchestrator 4.0 Patch 5 installation prerequisites
z
You must have ePolicy Orchestrator 4.0 (build 1015), Patch 1 (build 1083), Patch 2 (build 1113), Patch 3 (build 1151),
Patch 4 (build 1186 or 1221) or McAfee Total Protection for Endpoint installed prior to upgrading to ePolicy Orchestrator
4.0 Patch 5.
z
You must be logged on to the ePolicy Orchestrator 4.0 server as a Local Administrator on the system.
z
You must know the user name and password for at least one Global Administrator that is valid for the ePolicy
Orchestrator 4.0 server you are trying to upgrade.
z
The ePolicy Orchestrator and SQL Server services must be running during this upgrade (with the exception of when the
automated upgrade stops and starts your ePO services).
Before installing ePolicy Orchestrator 4.0 Patch 5
1. Back up your ePolicy Orchestrator server and ePolicy Orchestrator database before upgrading to ePolicy Orchestrator 4.0
Patch 5.
2. Ensure that there are no repository pulls or replications that are scheduled to run during the installation or that are
currently running.
Note: If the master repository is locked, package check-ins fail, causing the installation to fail and roll back.
