McAfee EPOLICY ORCHESTRATOR 4.0 PATCH 5 - RELEASE NOTES 12-05-2009 Release Note page 7

version "N/A."
11. Issue: Event ID 1038 was incorrectly associated with the event category, "Virus Detected but not
Removed." (Reference: 437525)
Resolution: Event ID 1038 indicates that no particular action was taken and is now associated with the event category
"Non-compliance."
12. Issue: When an installation failed and reverted to the previous version, the Site Manager file was not re-registered.
(Reference: 437841)
Resolution: The installation routine has been modified to correctly re-register all critical files when reverting to the
previous version.
13. Issue: The installation routine could replace Tomcat configuration files, causing Tomcat to fail to start. (Reference:
438104)
Resolution: The installation routine has been modified to avoid replacing Tomcat configuration files.
14. Issue: Saving an Enforcement Message Policy Client Assignment could result in the message "unexpected error
occurred." (Reference: 439548)
Resolution: The Enforcement Message Policy Client Assignment process has been modified to correctly save policy
updates.
15. Issue: Improperly formatted event files resulted in prolonged Event Parser performance degradation. (Reference:
440091)
Resolution: The Event Parser has been modified to skip improperly formatted event files.
16. Issue: The installation process would fail if the SQL Server Agent service was not running. (Reference: 441846)
Resolution: The installation routine has been modified, removing the dependency on the SQL Server Agent service.
17. Issue: Changing the owner of a policy with a large number of registered users could result in error. (Reference: 442364)
Resolution: Changing the owner of a policy is no longer dependant on the number of registered users.
18. Issue: Communication with ePolicy Orchestrator would fail when a system reported its CPU Speed as greater than
32,767 MHz. (Reference: 442734)
Resolution: The ePolicy Orchestrator system update process has been modified to limit CPU Speed properties to 32,767
MHz, allowing the system update to succeed.
19. Issue: Setting the Filter Data option on the Event Log had no effect on the returned events. (Reference: 427905,
434696, 440692, 443370, 444508, 444813, 445867)
Resolution: The process for filtering the Event Log has been modified to include the correct Filter Data options.
20. Issue: When configuring new client tasks in the Client Task wizard, the list of available client task types included client
types the user could only view. (Reference: 443963)
Resolution: The Client Task wizard has been modified to list only the client task types the user has permission to edit.
21. Issue: When a Microsoft Windows-based McAfee Agent was uninstalled through ePolicy Orchestrator before it first
communicated with ePolicy Orchestrator, the corresponding record would not be removed from the ePolicy Orchestrator
database. This system would then continue to be included in compliance reporting, resulting in incorrect information.
(Reference: 444928)
Resolution: Now when a Microsoft Windows-based McAfee Agent is uninstalled before its first communication with
ePolicy Orchestrator, the corresponding record is marked for removal and removed when necessary.
22. Issue: Adding a filter to a list of systems with a specific tag had no effect on the systems returned. (Reference: 445161)