Issues that are resolved in this release are listed below.
1. Issue: When an event package contained System Compliance Profiler and another point-product’s events, the System Compliance Profiler events would not be saved to the database. (Reference: 370718, 442064)
Resolution: System Compliance Profiler events are now saved in the database when included with other pointproduct events.
2. Issue: Replication to a UNC site could fail reporting error code 5 when different download and replication credentials are specified. (Reference: 411431)
Resolution: The download and UNC replication sessions have been modified to operate independently.
3. Issue: Registered executables with reserved HTML characters in their names could not be duplicated.
Release Notes for McAfee ePolicy Orchestrator 4.0 Patch 4 Page 2 of 24
Resolution: Registered executable names can now contain reserved HTML characters and be duplicated successfully.
4. Issue: Non-global administrators would receive the message “You are not authorized for this operation” when attempting to review McAfee Agent push failures. (Reference: 420764)
Resolution: The correct permissions are now enforced, allowing authorized users to review McAfee Agent push failures.
5. Issue: When manually checking in a package to the ePolicy Orchestrator’s master repository, a copy of the package would be abandoned in a temporary location. (Reference: 423560)
Resolution: The Patch installation removes all packages in the temporary location and prevents additional packages from being abandoned.
6. Issue: Purge Event Log Tasks would not delete events when the selection “Purge records older than:” was chosen. (Reference: 424692)
Resolution: The Purge Event Log Tasks routine has been modified to properly delete “Purge records older than:” events.
7. Issue: The Policy Assignment routine would incorrectly record the previously assigned policy as assigned, rather
than the newly assigned policy in the Audit log. (Reference: 424926)
Resolution: The Policy Assignment routine now correctly records newly assigned policies in the Audit log.
8. Issue: The Client Task Schedule option, “Only run this task once a day,” would not remain selected or be
enforced when a task was saved. (Reference: 431479)
Resolution: The selection of Client Task Schedule option, “Only run this task oncea day,” is now properly saved
9. Issue: When a system requested full policies, the Host Intrusion Protection policies were incomplete when
delivered. (Reference: 432785)
Resolution: The policy preparation routine was modified to ensure that Host Intrusion Protection policies are
10. Issue: An unexpected error occurred when executing an Events type query with a specified Tag Filter.
Resolution: The user is now able to execute Event type queries with a Tag Filter.
11. Issue: The VirusScan Enterprise DAT Deployment report would display “unexpected error occurred” when
attempting to drill into a DAT group of version “N/A.” (Reference: 437213)
Resolution: The VirusScan Enterprise DAT Deployment report has been modified to allow drilling into a DAT
group of version “N/A.”
12. 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
13. Issue: When an installation failed and reverted to the previous version, the Site Manager file was not reregistered.
Release Notes for McAfee ePolicy Orchestrator 4.0 Patch 4 Page 3 of 24
Resolution: The installation routine has been modified to correctly re-register all critical files when reverting to
the previous version.
14. Issue: The installation routine could replace Tomcat configuration files, causing Tomcat to fail to start.
Resolution: The installation routine has been modified to avoid replacing Tomcat configuration files.
15. 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
16. Issue: Improperly formatted event files resulted in prolonged Event Parser performance degradation.
Resolution: The Event Parser has been modified to skip improperly formatted event files.
17. 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
18. Issue: Changing the owner of a policy with a large number of registered users could result in error. (Reference:
Resolution: Changing the owner of a policy is no longer dependant on the number of registered users.
19. 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.
20. 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.
21. 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
22. 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 ePO 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.
23. Issue: Adding a filter to a list of systems with a specific tag had no effect on the systems returned. (Reference:
Resolution: The process for filtering tagged systems has been modified to filter the results correctly.
Release Notes for McAfee ePolicy Orchestrator 4.0 Patch 4 Page 4 of 24
24. Issue: Non-Microsoft Windows-based McAfee Agents that failed to uninstall through ePolicy Orchestrator, were
manually uninstalled and reinstalled, never reappeared in ePolicy Orchestrator. (Reference: 445488)
Resolution: Non-Microsoft Windows-based McAfee Agents are now listed in ePolicy Orchestrator as expected.
25. Issue: SuperDAT packages could not be deployed from ePolicy Orchestrator to Microsoft Windows 2008 Server
and Microsoft Windows Vista systems. (Reference: 450405)
Resolution: SuperDAT packages can now be deployed from ePolicy Orchestrator to Microsoft Windows 2008
Server and Microsoft Windows Vista systems.
26. Issue: Under certain conditions the server was becoming non-responsive, and non-paged pool memory for
apache.exe would grow very large. (Reference: 447222)
Resolution: The condition has been addressed so that the server does not become unresponsive, but rather
waits until error handling services are running before issuing error pages.
27. Issue: The “unexpected error occurred” page would be displayed when the user clicked “Update Filter” or
“Remove Filter” from within the Notification Log Report. (Reference: 450126)
Resolution: There is no longer an error when the user clicks the “Update Filter” or “Remove Filter” links.
28. Issue: Upgrading the Issues extension to version 1.5.1 failed. (Reference: 431353)
Resolution: Upgrading the Issue extension to version 1.5.1 now is performed correctly.
29. Issue: There was a failure when trying to install a particular version of the Help files. (Reference: 450059)
Resolution: Help files are now installed without incident.
30. Issue: The ePO Help Index tab was empty after upgrading. (Reference: 446253)
Resolution: The ePO Help Index tab is now correctly populated.
31. Issue: Remote command execution was failing if the admin password included non-standard ASCII characters,
HI-ASCII characters, or double-byte characters. (Reference: 395890)
Resolution: Remote command execution now works correctly if the admin password contains any of the
32. Issue: Pie charts did not have the option to limit the number of pie slices when sorting labels from A to Z or Z
to A. (Reference: 428377)
Resolution: The user now has the option to select the number of pie slices when sorting labels from A to Z or Z
to A in a pie chart.
when the dashboards were rendered. (Reference: 438775)
Resolution: The dashboards are now correctly displayed if there are double quotation marks in the returned
data of the dashboard.
34. Issue: Double-byte characters were causing problems when submitted to the server on some pages.
Resolution: The encoding has been changed so that double-byte characters do not cause a problem.
Release Notes for McAfee ePolicy Orchestrator 4.0 Patch 4 Page 5 of 24
35. Issue: The file names of PDF attachments were garbled when sent to a Lotus Notes server. (Reference:
Resolution: The configuration type has been changed so that the file names are no longer jumbled.
36. Issue: An unexpected error occurred when exporting an audit log query. (Reference: 447865)
Resolution: The user is now able to export audit log queries.
37. Issue: A “Page has expired” error message would be displayed when clicking the Back button after drilling down
into query details. (Reference: 447968)
Resolution: A warning is no longer displayed when clicking the Back button after drilling down into query
38. Issue: If a query was exported to PDF with drill-down tables, the drill-down data was not exported to the
report. (Reference: 450205)
Resolution: The drill-down data is now exported if the option is specified in the export page.
39. Issue: The Patch installer was failing when it tried to install on a previously installed version of ePolicy
Orchestrator. (Reference: 447907)
Resolution: The Patch installer now installs correctly on top of ePolicy Orchestrator 4.0 and its patches.
40. Issue: A newer version of the Java Runtime Environment was available. (Reference: 442560)
Resolution: The Patch updates the Java Runtime Environment to version 1.6.0_07.
41. Issue: The Patch installer failed in clustered systems if backup files already existed on the target system.
Resolution: The Patch installer now works correctly, regardless of whether backup files exist on the target
42. Issue: Filtering on a Boolean property did not work. (Reference: 426018)
Resolution: Filtering on a Boolean property now works correctly.
43. Issue: Exporting data as a result of an automated server task caused database problems. (Reference: 426432)
Resolution: Exporting data in the Comma Seperated Value (csv) format during an automated server task
44. Issue: Filtering in the System Tree was not working correctly. (Reference: 437587)
Resolution: Filtering in the System Tree area now works correctly.
45. Issue: The language selection was not remembered after logging out. (Reference: 438245)
Resolution: The system now remembers the language selected at the last log-on.
46. Issue: The user could not delete an automated response. (Reference: 446974)
Resolution: A user with the correct permissions can now delete an automated response.
Release Notes for McAfee ePolicy Orchestrator 4.0 Patch 4 Page 6 of 24
47. Issue: The user was not able to complete the server mapping when creating a new ticketing server. (Reference:
Resolution: The user can now complete the mapping when creating a ticketing server.
48. Issue: When a user tried to assign policies by drilling down in a Compliance Summary query, the user got an
“Unexpected Error” and was unable to assign policies. (Reference: 448620)
Resolution: The user can now successfully assign policies.
49. Issue: Column selection did not work from the System Tree page. (Reference: 448653)
Resolution: Column selection on the System Tree page now works correctly.
50. Issue: An unexpected error occurred while trying to remove the filter from the query in the query page.
Resolution: The user can now successfully remove filters from the query page.
51. Issue: Clicking the update filter button would cause an unexpected error. (Reference: 450224)
Resolution: Clicking the update filter button no longer causes an unexpected error.
53. Issue: Queries import displayed an error stating that the user was not authorized for the operation. (Reference:
Resolution: Query import is now properly validated against the user's permissions.
54. Issue: The dashboard data for one administrator was viewable by another administrator upon initial log in.
(Reference: 456088, 456090)
Resolution: Users now see only the dashboard data they are authorized to view.