Release Notes

McAfee ePolicy Orchestrator 4.6.6 Software

About this release
Rating
Known issues
Resolved issues
Installation instructions
Find product documentation

About this release

Thank you for choosing this McAfee product. This document contains important information about the current release. We strongly recommend that you read the entire document.

ImportantWe do not support the automatic upgrade of a pre-release software version. To upgrade to a production release of the software, you must first uninstall the existing version.

General information

Release date: March 26, 2013

Release build: 4.6.6.176

This release was developed for use with the following McAfee® ePolicy Orchestrator® ( McAfee ePO™ ) versions.
ePolicy Orchestrator 4.0 Patch 7 (build 1363 or later)
ePolicy Orchestrator 4.5 Patch 3 (build 937) or later
ePolicy Orchestrator 4.6 (build 1029 or later)
ePolicy Orchestrator 4.6.1 (build 1192 or later)
ePolicy Orchestrator 4.6.2 (build 201 or later)
ePolicy Orchestrator 4.6.3 (build 197 or later)
ePolicy Orchestrator 4.6.4 (build 202 or later)
ePolicy Orchestrator 4.6.5 (build 168 or later)

Rating

Mandatory. McAfee requires this release for all environments.

For more information about patch ratings, see McAfee KnowledgeBase article KB51560 .

Known issues

For a list of known issues specific to this release, see McAfee KnowledgeBase article KB77460 .

Resolved issues

This release corrects the following issues.

This patch includes resolved issues released in earlier patches. For a list of previously resolved issues, see the release notes for a specific patch.

Note McAfee doesn't disclose the nature of security-related issues and their resolutions.
1Issue — The server task log doesn't display the final McAfee® Agent wake-up call message in the server task log quickly. (Reference: 791691)

ResolutionMcAfee Agent wake-up calls appear in the server task log in a timely fashion.

2Issue — When you view assigned policies, the query filters the results by product feature, causing rule-based policies to appear in the wrong location. (Reference: 804853)

Resolution — Policies appear in the correct location.

3Issue — Windows 2012 SuperAgent repositories do not appear in the McAfee ePO server distributed repositories view. (Reference: 834774)

Resolution — SuperAgent repositories on all supported operating systems appear in the distributed repositories view.

4Issue — Saving a McAfee® Application Control policy generates an internal server error. (Reference: 808348)

ResolutionApplication Control policies are saved correctly.

5Issue — Selecting the Delete action in the Threat Event Log ignores custom filters. (Reference: 816826)

Resolution — Custom filters are applied when deleting items in the Threat Event Log.

6Issue — Users can set the agent-server communication ports to 21, 25, 70, 110, 119, or 143. Selecting these ports can cause some product functionality to fail. (Reference: 821710)

Resolution — The installer does not allow the user to set the agent-server communication ports to 21, 25, 70, 110, 119, or 143.

7Issue — Non-Windows systems appear as Affected Systems in the Run Client Task Now dialog box. (Reference: 825547)

Resolution — Non-Windows systems appear in the Run Client Task Now dialog box as Ignored Systems.

8IssueMcAfee Agent communication fails if the incoming property string contains a single quote in the beginning, or consecutive single quotes. (Reference: 831946)

ResolutionMcAfee Agent communication handles those odd strings properly.

9Issue — Once a Custom Property is set for a system, it persists on the McAfee ePO server after being removed on the system. (Reference: 833542)

Resolution — Performing a wake-up call task with Full Properties properly updates the McAfee ePO server after a Custom Property is removed.

10Issue — Automatic Active Directory user creation fails for users in child domains. (Reference: 813422)

Resolution — User auto-creation succeeds.

11Issue — In some instances, third-party libraries cause the McAfee ePolicy Orchestrator Application Server to stop. (Reference: 818014)

Resolution — Third-party libraries have been updated. The McAfee ePolicy Orchestrator Application Server runs normally.

12Issue — Leaving custom footers blank causes exporting to PDF to fail. (Reference: 820432)

Resolution — Exporting to PDF succeeds even with blank fields.

13Issue — Attempting to create an automatic response for threat events that occur within the last two days causes an error. (Reference: 823283)

Resolution — You can create an automatic response for threat events that occur within the last two days.

14Issue — When viewing the Server Task Log, if two dates are too far apart, an overflow message appears. (Reference: 836662)

Resolution — The Server Task Log can handle large date and time differences. No overflow warning message appears when dates are far apart.

15Issue — When performing a roll-up task, ExtraDAT Names don't appear in the report. (Reference: 825254)

Resolution — ExtraDAT names appear in the report.

16Issue — While upgrading from 4.6.x, the Agent to Server master key is reset to the default. (Reference: 839741)

Resolution — The Agent to Server master key does not change during an upgrade from 4.6.x.

17Issue — Violation of the UNIQUE KEY constraint allowed duplicate product properties to be inserted in the ePOProductProperties table, hampering performance. (Reference: 841213)

Resolution — The constraints on the ePOProductProperties table are not violated when inserting product properties.

18Issue — Completing or exiting the Client Task Assignment wizard always returns the user to the Client Task Assignments page. (Reference: 804648)

Resolution — Completing or exiting the Client Task Assignment wizard returns users to the page they started the wizard from.

19Issue — Invalid entries appear in the custom properties table. (Reference: 834199)

Resolution — Only valid entries appear in the custom properties table.

20Issue — Outdated license agreement content appears in the Software Manager. (Reference: 792261)

Resolution — The end-user license agreement (EULA) in the Software Manager is current.

21Issue — Certificate authentication can't be used to authenticate users who connect to the McAfee ePO server remotely. (Reference: 624205)

Resolution — Users who connect to the McAfee ePO server remotely receive a certificate prompt before arriving at the logon page.

22Issue — Disabling analytics on a dashboard doesn't disable query monitor analytics filters. (Reference: 792893)

Resolution — Filters can't be applied to monitors after analytics is disabled.

23Issue — Queries that pull data from different registered databases, but are otherwise identical, provide the same data. (Reference: 783672)

Resolution — The query datasource attribute now includes the database URI. When users run the queries, they see the data from each database.

24Issue — LDAP debugging does not log stack traces when it encounters an exception. (Reference: 837257)

Resolution — The stack trace for the exception is logged.

25Issue — Package types in the Check In Package wizard, such as "Install," are displayed in English on non-English operating systems. (Reference: 804086)

Resolution — Package types are translated correctly.

Package types are translated correctly.

26Issue — The ePolicy Orchestrator 4.6.x Event Parser service does not always start after a McAfee ePO server restart. (Reference: 834971)

Resolution — The ePolicy Orchestrator 4.6.x Event Parser service successfully starts after a server restart.

27Issue — The ePolicy Orchestrator software does not use the latest version of the Java Runtime Environment (JRE). (Reference: 837665)

Resolution — This version of the ePolicy Orchestrator software uses JRE version 1.6.0_39.

28Issue — The ePolicy Orchestrator interface does not allow users to determine whether the specified Online Certificate Status Protocol (OCSP) URL is the primary or fallback source for certificate revocation information. At logon, the OCSP URL is always used as a fallback source for revocation information.

In addition, the McAfee ePO server does not always use the non-standard port specified. (Reference: 838062)

Resolution — Users can choose whether the OCSP URL is a fallback or the primary source of revocation information. By default, the OCSP URL is the fallback information source.

The non-standard port specified is used when contacting the OCSP server.

29Issue — When using the Response Builder to create an Automatic Response, the Create Issue action is missing a space. (Reference: 834275)

Resolution — The Create Issue action is displayed correctly.

30Issue — The McAfee banner is not displayed properly on all pages. (Reference: 839477)

Resolution — The McAfee banner is displayed correctly on all pages where it appears.

Installation instructions

For information on installing or upgrading ePolicy Orchestrator software, see the McAfee ePolicy Orchestrator Installation Guide.

Important Before proceeding with the upgrade process, see McAfee KnowledgeBase article KB71825 for important steps to take before this upgrade.

Find product documentation

McAfee provides the information you need during each phase of product implementation, from installation to daily use and troubleshooting. After a product is released, information about the product is entered into the McAfee online KnowledgeBase.

Task
1 Go to the McAfee Technical Support ServicePortal at http://mysupport.mcafee.com.
2 Under Self Service, access the type of information you need:
To access... Do this...
User documentation
1Click Product Documentation.
2Select a product, then select a version.
3Select a product document.
KnowledgeBase
Click Search the KnowledgeBase for answers to your product questions.
Click Browse the KnowledgeBase for articles listed by product and version.