Download

McAfee KB

Resolved issues

Issues that are resolved in this release are listed below.

1. Issue: SuperAgent Repositories on Windows Vista and Windows 2008 systems did not appear as Distributed Repositories in the ePolicy Orchestrator console. (Reference: 371932, 405958)

Resolution: SuperAgent Repositories on Windows Vista and Windows 2008 systems now appear as Distributed Repositories in the ePolicy Orchestrator console.

2. Issue: A synchronization point could not be created, edited, or deleted for the “My Organization” group. (Reference: 384135)

Resolution: A synchronization point for the “My Organization” group can now be created, edited, and deleted.

3. Issue: Grouped Summary Table queries could not be ordered by label values when grouped by a version number column. For example, a group summary of managed systems grouped by group name and DAT version could not be ordered by the group name label and then by DAT version label. (Reference: 386121)

Resolution: Grouped Summary Table queries can now be ordered by the label values when grouped by a version number column.

4. Issue: When configuring an Active Directory synchronization group, the “Browse” button for browsing and “Add” button for exceptions were disabled unless the user first selected an NT domain synchronization type. (Reference: 391830)

Resolution: The “Browse” and “Add” buttons are now enabled without having to first select an NT domain synchronization type.

5. Issue: Active Directory synchronization failed when a synchronized folder name included a semicolon. (Reference: 392803)

Resolution: Active Directory folder names can now contain a semicolon.

6. Issue: When viewing the system properties of a system that has never communicated with the ePolicy Orchestrator server, clicking on the “more” link resulted in a blank page. (Reference: 398952)

Resolution: Selecting the “more” link for a managed system that has never communicated with the ePolicy Orchestrator server no longer results in a blank page.

7. Issue: Extra.DAT packages were not updated on Windows Vista or Windows 2008 Server managed systems. (Reference: 400563)

Resolution: Extra.DAT packages are now updated on Windows Vista and Windows 2008 Server managed systems.

Note: All Extra.DAT packages in the repository must be reinstalled before this change takes effect.

8. Issue: The McAfee Agent failed to enforce Host Intrusion Protection rule policies when the rule name contained an angled bracket character. (Reference: 400808)

Resolution: The McAfee Agent now enforces Host Intrusion Protection rule policies regardless of the rule name.

9. Issue: A client task with a “repeat starting at” schedule could have a repeat duration that was less than the repeat interval, resulting in the client task never running. (Reference: 401301)

Resolution: New or modified client tasks with a “repeat starting at” schedule must now have a repeat duration that is greater than or equal to the repeat interval.

10. Issue: When viewing the results of a query for Events, the “Show Related Systems” action is not available. (Reference: 402250)

Resolution: The “Show Related Systems” action is now available for Event queries.

11. Issue: Importing managed systems into the System Tree from a Unicode text file created erroneous entries in the System Tree. (Reference: 402271)

Resolution: An error message is now displayed when non-UTF-8 encoded text files are imported, and the System Tree is unaffected.

12. Issue:  An updated version of the System Compliance Profiler 2.0 extension is available. (Reference: 404381)

Resolution: Version 2.0.2.191 of the System Compliance Profiler 2.0 extension is now installed during ePolicy Orchestrator 4.0 Patch 3.

13. Issue: Running a previous upgrade a second time, after it had been successfully installed, failed. (Reference: 405288)

Resolution: The upgrade can now be run multiple times.

14. Issue: VirusScan DAT and Engine version information was missing on Managed System Rollup queries. (Reference: 405383)

Resolution: Managed System Rollup queries now include VirusScan DAT and Engine version information.

15. Issue: In the ePolicy Orchestrator console, the option that uninstalls the McAfee Agent from managed systems was not supported by non-Windows agents, but it was a selectable option. When this option was selected and the agents were manually uninstalled and later reinstalled, the managed systems never reappeared in the ePolicy Orchestrator System Tree. (Reference: 405859)

Resolution: A non-Windows managed system, which successfully reinstalls the McAfee Agent after a failed agent uninstall from the ePolicy Orchestrator console, now reappears in the ePolicy Orchestrator console System Tree.

16. Issue: An ePolicy Orchestrator 4.0 upgrade failed when the SQL Server UDP port was enabled for the initial ePolicy Orchestrator 4.0 installation and disabled before upgrading. The inverse scenario also caused the upgrade to fail. (Reference: 406814, 415166)

Resolution: The ePolicy Orchestrator 4.0 upgrade no longer fails when the SQL Server UDP port was enabled for the initial ePolicy Orchestrator 4.0 installation and disabled before upgrading. The inverse scenario has also been corrected.

17. Issue: The Synchronization Group Agent Deployment checkbox, “Force installation over existing Version,” does not remain selected after saving the Synchronization Group and accessing it again for editing. (Reference: 410246, 426930)

Resolution: The Synchronization Group Agent Deployment checkbox, “Force installation over existing Version,” now retains the selected value.

18. Issue: Installations in clustered server environments incorrectly set the ePolicy Orchestrator services to start “Automatically.” (Reference: 410543)

Resolution: Installations in clustered server environments now correctly set the ePolicy Orchestrator services to start “Manually.”

19. Issue: The managed system name is truncated to a length of 14 characters on the ePolicy Orchestrator console “Systems” tab. (Reference: 410779)

Resolution: The column “DNS Name,” containing a “Fully Qualified Domain Name,” can now be selected as the managed system name on the ePO console “Systems” tab.

20. Issue: The import policies process did not verify the ownership of the existing policies, which could result in policies being overwritten by users other than the owner. (Reference: 410917)

Resolution: The import policies process now verifies the ownership of the existing policies and prevents policies from being overwritten by users other than the owner.

21. Issue: Changes to existing policies were not recorded in the Audit Log. (Reference: 412589)

Resolution: Changes to existing policies are now recorded in the Audit Log.

22. Issue: The ePolicy Orchestrator Alerting extension, used by Rogue System Detection 2.0, was not localized. (Reference: 412661)

Resolution: The ePolicy Orchestrator Alerting extension is upgraded to a localized version, on ePolicy Orchestrator servers with Rogue System Detection 2.0 installed.

23. Issue: The ePolicy Orchestrator server failed to respond if a corrupt package file was checked in. (Reference: 413466)

Resolution: The ePolicy Orchestrator server responds correctly when a corrupt package file is checked in.

24. Issue: Editing a client task could result in the error message “An Unexpected error occurred” being displayed in the ePolicy Orchestrator console. (Reference: 413963)

Resolution: Editing client tasks no longer results in unexpected errors.

25. Issue: Client tasks, for managed product extensions that do not have a default policy, were not available for configuration. (Reference: 415739)

Resolution: Client tasks, for managed product extensions that do not have a default policy, are now available for configuration.

26. Issue: An ePolicy Orchestrator 4.0 upgrade stopped installing the included managed product extensions after the first failure was discovered. (Reference: 415974)

Resolution: An ePolicy Orchestrator 4.0 upgrade now attempts to install each of the included managed product extensions, even if an error occurs during the installation of a previous managed product extension.

27. Issue: When the ePolicy Orchestrator server did not have a “Master Agent to Server Communication Key,” the ePolicy Orchestrator 4.0 upgrade failed leaving the ePolicy Orchestrator server in a non-functional state. (Reference: 419859)

Resolution: The ePolicy Orchestrator 4.0 upgrade now verifies the ePolicy Orchestrator server has a “Master Agent to Server Communication Key” before it starts the upgrade.

28. Issue: An updated version of the Host Intrusion Prevention 7.0 extension is available. (Reference: 422819)

Resolution: Version 7.0.1.133 of the Host Intrusion Prevention 7.0 extension is installed during the ePolicy Orchestrator 4.0 upgrade.

29. Issue: The “delayload.log” file could grow without limit in the root (C:\) of the ePolicy Orchestrator server. (Reference: 425738)

Resolution: The “delayload.log” file is no longer used.

Note: The ePolicy Orchestrator 4.0 upgrade process does not remove existing “delayload.log” files.

30. Issue: Event queries could not be chained to ePolicy Orchestrator server task actions. (Reference: 427217)

Resolution: Event queries can now be chained to ePolicy Orchestrator server task actions.

31. Issue: Server tasks could not run an event query that was chained to these actions: apply, clear, or exclude tag actions. (Reference: 427708)

Resolution: Server tasks can now run an event query chained to these actions: apply, clear, or exclude tag actions.

32. Issue: The “View Logs” button could fail to display the correct installation log files after an ePolicy Orchestrator 4.0 upgrade failure. (Reference: 429819)

Resolution: The “View Logs” button now displays the main installation log files after an ePolicy Orchestrator 4.0 upgrade failure.

33. Issue: An initial ePolicy Orchestrator 4.0 installation, on a system with a local MSDE database and the UDP port disabled, could result in incorrect ePolicy Orchestrator service dependencies. (Reference: 430390)

Resolution: The ePolicy Orchestrator 4.0 upgrade repairs the ePolicy Orchestrator service dependencies for systems installed with a local MSDE database and the UDP port disabled.

34. Issue: Miscellaneous language translation and localization issues were reported. (Reference: 429847, 430581)

Resolution: The reported language translation and localization issues were addressed.

35. Issue: An updated version of the ePolicy Orchestrator Help extension is available. (Reference: 433198) 

Resolution: Version 1.0.6 of the ePolicy Orchestrator Help extension is now installed during the ePolicy Orchestrator 4.0 upgrade.

36. Issue: Inconsistent event times would appear in the Server Task Log. (Reference: 417725) 

Resolution: The problem of inconsistent event times appearing in the Server Task Log after applying patches has been fixed.

37. Issue: Console logons using NT authentication, worked only when the ePolicy Orchestrator console was located in a domain where a two-way trust existed between the console and ePolicy Orchestrator server domains. (Reference: 395894) 

Resolution: Authentication support for multiple domain controllers has been added to the product. (For more information see KB article: 616709)

38. Issue: The date formats are incorrect for the English (United Kingdom) locale. (Reference: 362588) 

Resolution: A new choice of English (United Kingdom) has been added to the Language drop-down list of the ePolicy Orchestrator Logon screen. 

39. Issue: When installing managed product extensions on ePolicy Orchestrator, the installation could fail with the message: “ERROR: java.lang.OutOfMemoryError: PermGen space.” (Reference: 407724) 

Resolution: The PermGen Memory allocation size has been increased to 128 MB on clean installations and upgrades. (For more information see KB article: 615843)

40. Issue: There was a performance bottleneck when processing a large number of unrelated dashboard requests. (Reference: 407724) 

Resolution: Performance has been improved to allow many users to view the dashboard.

41. Issue: Dashboard related caching is not functioning correctly, which caused the user to see stale data. (Reference: 411646) 

Resolution: Dashboard caching has been fixed so the user views the most current data. 

42. Issue: An unexpected error occurred while creating a query using a Grouped Bar Chart with Boolean types of data. (Reference: 415069)

Resolution: Grouped Bar Charts now correctly display data when using any of the supported data types.

43. Issue: Drilling down into a chart, a user could see an unexpected error page if there was a null value in the returned time field. (Reference: 413954, 419692) 

Resolution: Chart drill-down now works as expected and no longer returns an error when drilling down into null time-based reports.

44. Issue: Some international characters caused problems in the server log details page. (Reference: 411088) 

Resolution: Log entries are now correctly formatted prior to being written to the server task log.

45. Issue: Some valid characters caused problems when user names or passwords were typed in the ePO installer. (Reference: 395890)