About this release
Patch Release: August 26, 2009
Patch Package: 4.0.0.1494
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 Agent 4.0 Readme file in the release package, and details fixes included in
McAfee Agent 4.0 Patch releases.
This Patch contains a variety of improvements. McAfee has spent a significant amount of time finding, fixing, and
testing the fixes in this release. Please review the Known and Resolved Issues lists for additional information on the
individual issues.
Refer to online KnowledgeBase article KB65953 at https://kc.mcafee.com for the most current information regarding
this release.
1. Issue: The McAfee Agent installation process checked for the existence of the “My Documents” folder. If it was
not present or mapped to a network folder, the installation failed. (Reference: 474870)
Resolution: The McAfee Agent installation process no longer requires the “My Documents” folder to be present.
2. Issue: The McAfee Agent upgrade process failed to update the sitelist.xml file with all of the required policy
information, resulting in the incorrect repository sort order being used. (Reference: 450082)
Resolution: The McAfee Agent upgrade process has been updated to trigger the system to request the current
site list from the ePolicy Orchestrator server.
3. Issue: The McAfee Agent installation process would fail when the current user's user name contained non-ASCII
(ex. Japanese) characters. (Reference: 453206)
Resolution: The McAfee Agent installation process now allows user names to contain non-ASCII characters.
4. Issue: The presence of certain environment variables (i.e. http_proxy, ftp_proxy) caused the McAfee Agent to
attempt to communicate using the proxy address specified in the variable. (Reference: 457621)
Resolution: The McAfee Agent now uses the proxy specified on the Proxy Policy Setting page only and avoids
the use of any environment variables.
5. Issue: When attempting to determine if the system is a laptop the Property Collection process could cause the
McAfee Agent to crash or fail to respond. (Reference: 457837)
Resolution: The Property Collection process has been updated to always return even if it cannot determine
whether the system is a laptop. The system appears as “Unknown” in the ePolicy Orchestrator console when this
occurs.
6. Issue: The “/forceinstall” switch failed to cause a new McAfee Agent GUID to be created when installing over an
existing installation. (Reference: 462869)
Resolution: The “/forceinstall” switch now regenerates the McAfee Agent GUID when installing over an existing
installation.
Note: When using the “/forceinstall” switch in combination with the “/upgrade” switch a new McAfee Agent
GUID is not generated.
7. Issue: When the Update process failed to download a file from a UNC repository the download would not be
attempted from the next repository. (Reference: 462898)
Resolution: The Update process now attempts to download the file from all defined repositories until it is
successfully downloaded or all available repositories are exhausted.
8. Issue: When a product detection or installation script was executing and the Update process failed to download
a requested file and failed over to a subsequent repository, a second Update dialog box was displayed.
(Reference: 462953)
Resolution: The Update process now only displays one Update dialog box per update.
9. Issue: When the Update process failed to download a requested file and failed over to a subsequent repository,
a DAT or Engine update could fail. (Reference: 464970)
Resolution: The Update process now allows DAT or Engine updating to complete when failing over to a
subsequent repository.
10. Issue: On 64-bit Microsoft Windows systems with no users logged on the error message “Failed to Open
Process. Error code 57” appeared in the Agent_ log file. (Reference: 468073)
Resolution: The McAfee Agent no longer records this message.
11. Issue: The McAfee Agent allowed an update task to be postponed, but it did not allow deployment tasks to be
postponed. (Reference: 469427)
Resolution: The McAfee Agent now allows update and deployment tasks to be postponed.
12. Issue: When a SuperAgent repository had more than five systems waiting to connect for download, subsequent
system connections were rejected causing the associated download to fail. (Reference: 471505)
Resolution: SuperAgent repositories now support up to 200 systems waiting to connect for download.
13. Issue: On Microsoft Vista machines, the reported User Name property was always the name of the first user to
log on after the system was restarted. (Reference: 472980)
Resolution: The User Name property is now reported as the most recently logged on user.
14. Issue: When the McAfee Agent failed to connect to ePolicy Orchestrator or ePolicy Orchestrator rejected the
connection during a McAfee Agent “Wakeup with Full Properties” request, the McAfee Agent would only send
incremental properties the next time it reported its properties. (Reference: 475006)
Resolution: McAfee Agent “Wakeup with Full Properties” requests are now retried until successfully sent to the
ePolicy Orchestrator.
15. Issue: During passive transfers the McAfee Agent failed to respond correctly to certain non-Microsoft FTP
responses causing the deployment or update to fail. (Reference: 477298)
Resolution: The McAfee Agent now properly responds to standard passive FTP transfer response codes.
16. Issue: The “/upgrade” switch failed to remove or upgrade obsolete data from previous installations. (Reference:
479814)
Resolution: The “/upgrade” switch now properly removes or upgrades obsolete data from previous installations.
17. Issue: When viewed through the Windows Task Manager, the McAfee Status Monitor process (udaterui.exe)
reported 16 I/O Reads per second at idle. (Reference: 484245)
Resolution: The McAfee Status Monitor process now only performs read operations when required.
18. Issue: When policy enforcement occurred while the repository was being sorted, the McAfee Agent would leak
virtual memory. (Reference: 484776)
Resolution: The McAfee Agent no longer leaks memory when enforcing policies during a repository sort.
19. Issue: When directed to use a language other than the system default through the “UseLanguage” feature, the
reported language remained the system default language. (Reference: 492157)
Resolution: The McAfee Agent now properly reports the language in use.
20. Issue: The McAfee Agent did not support the ePolicy Orchestrator “Duplicate List” feature. (Reference: 494754,
500714)
Resolution: The McAfee Agent now supports the ePolicy Orchestrator “Duplicate List” feature.
21. Issue: When the “catalog.z” file was larger than 4,096 bytes, updates via Local and Distributed UNC
repositories failed and the error message “Error occurred while downloading catalog.z” appeared in the Agent_
log file. (Reference: 480163)
Resolution: The McAfee Agent is no longer dependant on the size of the “catalog.z” file.
22. Issue: The McAfee Agent was vulnerable to the issue described in Security Bulletin SB10002, “McAfee Security
Bulletin - ActiveX security issue in CMA and McAfee Agent. (Reference: 495121)
Resolution: The McAfee Agent upgrade process has been updated to implement the required registry
modifications.
23. Issue: The McAfee Agent did not provide an embedded credential installation package. (Reference: 432427)
Resolution: An embedded credential installation package is now available. The embedded credential package is
separate from the General Use package. If you require the embedded credentials package
(MA400P3Win_EMBEDDED.zip), it is available on the McAfee download and ServicePortal sites.
Note: The embedded credentials package is several megabytes larger than the General Use package. Please
note that this can result in a significant impact in some environments. The ability to embed credentials is the
only difference between the packages.
老规矩，我们D版用户还要段日子才能下到。。。。。。 |
发表于 2009-8-27 07:17:49
楼主
