Advertisement
Quick Links
Release Notes for McAfee ePolicy Orchestrator 4.0 Patch 5
Thank you for using McAfee
about this release. We strongly recommend that you read the entire document.
Contents
About this release
Rating
Purpose
Known issues
Resolved issues
Installation Instructions
Finding documentation for McAfee enterprise products
License attributions
About this release
Patch Release: May 12, 2009
Patch Package: 4.0.0.1293
This release was developed for use with:
McAfee ePolicy Orchestrator 4.0
McAfee ePolicy Orchestrator 4.0 Patch 1
McAfee ePolicy Orchestrator 4.0 Patch 2
McAfee ePolicy Orchestrator 4.0 Patch 3
McAfee ePolicy Orchestrator 4.0 Patch 4
McAfee Total Protection for Endpoint
Make sure you have installed the correct version(s) before using this release.
Rating
McAfee recommends this release for all environments. This update should be applied at the earliest convenience. For more
information, see KB article KB51560.
Purpose
This document supplements the McAfee ePolicy Orchestrator 4.0 Readme file in the release package, and details fixes included
in ePolicy Orchestrator 4.0 Patch 1, Patch 2, Patch 3, Patch 4, and Patch 5.
Refer to online KnowledgeBase article
this release.
Known issues
Known issues in this release of the software are described below.
1.
Issue: Not all characters are allowed with ePolicy Orchestrator or SQL usernames and passwords, specifically regarding
use with the ePolicy Orchestrator installer. (Reference: 387883, 395890)
Workaround: Here is a list of the allowed and disallowed characters for the usernames and passwords used by the
ePolicy Orchestrator 4.0 Patch 5 installer. This list is known to be valid only for the ePolicy Orchestrator Patch 5 installer
and might not represent the character sets allowed for previous patch installers.
ePO username and password official character set for the Patch 5 installer
Allowed
Exceptions (for both user names and passwords, except as noted)
®
®
ePolicy Orchestrator
software version 4.0 Patch 5. This document contains important information
KB65506
at
https://mysupport.mcafee.com/
All printable characters with a hex value of 0x20 – 0x7E (ASCII 32 through 126), with exceptions
listed below.
No leading space, trailing spaces, or passwords made up of solely spaces
No double quotes (")
for the most current information regarding
Advertisement
Related Manuals for McAfee EPOLICY ORCHESTRATOR 4.0 PATCH 5 - RELEASE NOTES 12-05-2009
Summary of Contents for McAfee EPOLICY ORCHESTRATOR 4.0 PATCH 5 - RELEASE NOTES 12-05-2009
- Page 1 McAfee Total Protection for Endpoint Make sure you have installed the correct version(s) before using this release. Rating McAfee recommends this release for all environments. This update should be applied at the earliest convenience. For more information, see KB article KB51560. Purpose This document supplements the McAfee ePolicy Orchestrator 4.0 Readme file in the release package, and details fixes included...
-
Page 2: Resolved Issues
System Tree in the ePolicy Orchestrator console. (Reference: 391040) Workaround: On Windows 2008 servers, the McAfee ePolicy Orchestrator 4.0.0 Application Server service must have sufficient permissions to complete the request. For more information, see KB article KB53861. - Page 3 Resolution: The agent key updater package now allows non-Windows agents to use new agent-server secure communication keys. Issue: Distributed repositories are not used for global updating if the master repository has been updated with packages other than DATs and Engines. (Reference: 419665) Resolution: Global updating will use distributed repositories even if the master repository has been updated with packages other than DATs and Engines.
- Page 4 been created. (Reference: 450163, 480057) Resolution: The download credentials for source repository sites can now be edited. Issue: Checking a new agent package into the ePolicy Orchestrator repository does not always update the ePolicy Orchestrator list of supported platforms correctly. (Reference: 467664) Resolution: Checking a new agent package into the ePolicy Orchestrator repository correctly updates the ePolicy Orchestrator list of supported platforms.
- Page 5 Issue: An event purge fails for Purge with 0 Days. (Reference: 471355) Resolution: An event log will Purge with 0 days. Issue: Users get a message "Exception occurred in OrionCore.dialogBoxOkHandler!" when trying to purge Notification Logs. (Reference: 472788) Resolution: Users no longer receive an exception message when purging the Notification Logs. Issue: Items Event Group and Event Type cannot be sorted in the Response Builder.
- Page 6 McAfee Agent push failures. (Reference: 420764) Resolution: The correct permissions are now enforced, allowing authorized users to review McAfee Agent push failures. 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.
- Page 7 Resolution: The Client Task wizard has been modified to list only the client task types the user has permission to edit. 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.
- Page 8 Resolution: The process for filtering tagged systems has been modified to filter the results correctly. 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.
- Page 9 Issue: An unexpected error occurred when exporting an audit log query. (Reference: 447865) Resolution: The user is now able to export audit log queries. Issue: A “Page has expired” error message would be displayed when clicking the Back button after drilling down into query details.
- Page 10 Issue: An unexpected error occurred while trying to remove the filter from the query in the query page. (Reference: 450209) Resolution: The user can now successfully remove filters from the query page. 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.
- Page 11 Resolution: ExtraDAT packages are now updated on Windows Vista and Windows 2008 Server managed systems. Note: All ExtraDAT packages in the repository must be reinstalled before this change takes effect. Issue: The McAfee Agent failed to enforce Host Intrusion Protection rule policies when the rule name contained an angle bracket character. (Reference: 400808) Resolution: The McAfee Agent now enforces Host Intrusion Protection rule policies regardless of the rule name.
- Page 12 Resolution: Installations in clustered server environments now correctly set the ePolicy Orchestrator services to start “Manually.” 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 ePolicy Orchestrator console “Systems”...
- Page 13 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. 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.
- Page 14 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. 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.
- Page 15 Resolution: A purge action has been added for the Rollup Systems, Rollup Compliance, and Compliance History registered types. Issue: An audit log entry was not created when a package was deleted from a repository. (Reference:384013) Resolution: An audit log entry is now created when a package is deleted from a repository. Issue: When exporting Systems to a CSV file, a blank window appeared and the export failed.
- Page 16 (Reference: 373129) Resolution: Now extensions can be removed right after being installed without generating an error. Issue: In the McAfee Agent “More” properties, the Last Update property displayed the server’s time rather than Coordinated Universal Time. (Reference: 382716) Resolution: The Last Update property in the McAfee Agent “More”...
- Page 17 Resolution: The computer property “Is 64 bit OS” now includes the end node state on the Query Filters, Tag Criteria, and System Details pages for end nodes using McAfee Agent 4.0. This property continues to show “unknown” for end nodes running Common Management Agents released prior to McAfee Agent 4.0.
- Page 18 Resolution: Clicking the “Version” header on the Master Repository page now sorts the report by version. Issue: When modifying a new Update Task (Systems | Schedule tab | Options), data can be entered even though the fields appear disabled. (Reference: 335892) Resolution: On the Systems | Schedule tab | Options page, data can no longer be entered in the disabled fields when modifying a new Update Task.
- Page 19 Issue: Updates to point product extensions are available. (Reference: 384955) Resolution: The following point product extensions are upgraded to the following versions during the Patch installation: McAfee Agent version 4.0.0.207 VirusScan Enterprise 8.0i version 8.0.0.182 VirusScan Enterprise 8.5 version 8.5.0.172 System Compliance Profiler version 2.0.1.189...
- Page 20 Resolution: The computer property “Is Laptop” now includes the end node state on the Query Filters, Tag Criteria, and System Details pages for end nodes using the McAfee Agent 4.0. This property continues to show “Unknown” for end nodes running Common Management Agents released prior to McAfee Agent 4.0.
- Page 21 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.
- Page 22 Installing ePolicy Orchestrator 4.0 Patch 5 on each node Run the ePolicy Orchestrator Patch 5 setup on each of the nodes. McAfee strongly recommends that you install the Patch on one node at a time, and that all other nodes are shut down.
- Page 23 For any such software covered under the GPL, the source code is made available on this CD. If any Free Software licenses require that McAfee provide rights to use, copy or modify a software program that are broader than the rights granted in this agreement, then such rights shall take precedence over the rights and restrictions herein.
- Page 24 No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of McAfee, Inc., or its suppliers or affiliate companies.