About this documentThank you for choosing this McAfee product. This document contains important information about the current release. We strongly recommend that you read the entire document.
New Features Here is a list of new and updated features included with this Beta release of the McAfee Agent 4.6.0.
Run client tasks nowYou can now run client tasks on demand. ePolicy Orchestrator 4.6.0 includes a Run Client Task Now action which, when using a version 4.6.0 Agent, queues the selected task for immediate execution on the selected systems. This feature requires both ePolicy Orchestrator 4.6.0 and McAfee Agent 4.6.0. If there is a network address translation layer (NAT) between the ePolicy Orchestrator server and the Agent client, the Run Client Task Now task will run the next time the agent communicates with the ePolicy Orchestrator server.
SuperAgent lazy cachingSuperAgent (SA) repositories now only pull needed content from ePolicy Orchestrator servers instead of receiving all content on push replications. This reduces the bandwidth required to distribute content to SA repositories. The SA repository caches any packages it has pulled, so subsequent requests by end nodes are served locally without pulling from the master repository. In previous versions, ePolicy Orchestrator pushed all content to SA repositories regardless of whether it was actually needed.
Performance improvementsThe Agent now consumes less memory on the client, uses less CPU time, and allows you to reduce process priority to improve end node performance.
Repository policy breakoutThere is a new Repository policy category allowing you to configure repository policies independently from general policies. This allows you to set your general policies globally and your repository policies locally. In addition, you can now use drag-and-drop to reorder the repository list.
Default policy type for large organizationsMcAfee Agent now provides a default policy type specifically designed for large organizations called Large Organization Default. This policy is intended as a starting point from which large organizations can create their own custom policies, and covers policies in the General category.
Agent event refinementsEvent generation in failure cases has been enhanced. Property collection and policy enforcement failures are now reported on first instance only, and product update and deployment failure events are more precise.
Endpoint language selectionMcAfee Agent 4.6 allows you to configure the language used by the Agent through policy. This language selection overrides the local settings. It is used for both the Agent user interface on the client, and the agent log files generated by that client. This is useful when your administrators or support personnel speak a different language than the one used by the end node users. | Note | If you configure the Agent to use a language other than the users' selected language, the text displayed in the Agent user interface on their machine will be in the language you selected, and not the same as the rest of the users' interface. Regardless of language selection, some detailed log text remains in English for troubleshooting purposes by McAfee. |
Improved cluster awarenessThe agent is now more aware of the network cluster environment in which it resides, and sends additional cluster and node properties back to ePolicy Orchestrator.
Agent deployment to Unix-based systemsYou can now deploy agents to some Unix-based systems using push deployment. Push deployment is currently supported for Macintosh OS versions 10.5 (Leopard) and 10.6 (Snow Leopard), and Red Hat Linux Enterprise versions 4 and 5.
Unix-based Command AgentThe Command Agent tool (cmdagent) is now available on all operating systems supported by McAfee Agent 4.6. The Command Agent allows you to control the agent on the client system by invoking actions such as policy enforcement, collecting and sending properties, and checking for new policies and tasks on the server.
Known issues Here is a list of known issues that we were aware of at production time.
Compatibility Issues| 1 | Issue — McAfee Agent 4.6 is incompatible with builds of the McAfee VirusScan(R) Enterprise 8.8 beta prior to build 625. (Reference: 622512) Workaround — If you are participating in the VirusScan Enterprise 8.8 beta, upgrade VirusScan Enterprise to the most recent beta version before upgrading or installing McAfee Agent 4.6. | | 2 | Issue — Deploying McAfee Security for Macintosh 1.0 onto a Macintosh system with McAfee Agent 4.6.0 already installed will cause the agent to crash during the next agent/server communication. (Reference: 542939) Workaround — Do not use both McAfee Agent 4.6.0 and McAfee Security for Macintosh 1.0 on the same system. |
Install/Uninstall issues| 1 | Issue — Inserting double quotation marks (") in custom properties fields when using frminst.exe results in the following error: The parameter is incorrect(Reference: 479943) Workaround — Avoid using double quotation marks in custom properties fields. | | 2 | Issue — When manually installing the agent using FramePkg.exe, adding double-byte or extended characters to the Datadir path will cause installation to fail with error 1603. (Reference: 624442) Workaround — Avoid using double-byte or extended characters in the Datadir path. | | 3 | Issue — If you attempt to force a non-embedded-credentials version of FramePkg.exe to install with embedded credentials, the error message displayed is always in English. (Reference: 613814) Workaround — There is no current workaround. |
McAfee System Tray issues| • | Issue — Disabling the Show the McAfee system tray icon General policy setting for end nodes running Windows XP and VirusScan Enterprise 8.7 Patch 2 or earlier causes the McAfee system tray icon to crash. (Reference: 544451) Workaround — Enable the Show the McAfee system tray icon policy setting, or upgrade the version of VirusScan Enterprise running on the end node to version 8.7 Patch 3 or later. |
McAfee Agent Monitor issues| • | Issue — Double-byte characters are currently not displayed correctly in the New policy for <system name>\<user> line in the McAfee Agent Monitor. (Reference: 495766) Workaround — There is no current workaround. |
SuperAgent issues| 1 | Issue — SuperAgent wake up calls initiated from an Agent Handler are not successful. (Reference: 537985, 576516) Workaround — From the ePolicy Orchestrator server interface, in the Agent Handler assignments page, add your ePolicy Orchestrator server to the custom handler list for the Agent Handler your SuperAgents use to communicate. | | 2 | Issue — Specifying a SuperAgent repository path that exceeds 100 characters causes Replication tasks on that repository to fail. (Reference: 538319) Workaround — Specify SuperAgent repository paths that do not exceed 100 characters. | | 3 | Issue — Replication to a McAfee 4.6 Beta 1 SuperAgent fails. (Reference: 623805) Workaround — Check the McAfee Agent 4.6 Beta 1 AgentKeyUpdater package (AgentKeyUpdater.zip) into the master repository prior to SuperAgent replication. This package can be found in the ePolicy Orchestrator 4.6 Beta 2 Software Manager, or where this McAfee Agent beta release was posted. | | 4 | Issue — A SuperAgent with lazy cache enabled and no access to the master repository will fail to provide updates to end nodes. (Reference: 617199) Workaround — Ensure your SuperAgents using lazy caching have a policy applied that gives them access to the master repository. |
Policy issues| • | Issue — When importing policies into an ePolicy Orchestrator 4.6 server, any existing policy that is the same type and name as the policy being imported should be overwritten. Currently, agent Repository policies that match this pattern are not being overwritten. As a result, importing Repository policies of the same name and type are duplicated in your policy catalog. (Reference: 541623) Workaround — Backup existing agent Repository policies before importing policies into an ePolicy Orchestrator 4.6 server. After import, examine previously existing Repository for unintended changes. |
Task related issues| 1 | Issue — Mirror repository client tasks configured to mirror from Linux HTTP and FTP repositories might fail. (Reference: 622878) Workaround — Only use Windows servers for HTTP or FTP repositories. | | 2 | Issue — Passwords on HTTP and FTP repositories are reset to the ePolicy Orchestrator master repository password during the first agent/server communication. (Reference: 625230) Workaround — Set HTTP and FTP repository passwords to the same as the ePolicy Orchestrator master repository password, or set HTTP or FTP repository authentication to Anonymous. | | 3 | Issue — The "Run When Idle" task scheduling option is no longer supported. (Reference: 384605) Workaround — There is no current workaround. | | 4 | Issue — The Postpone dialog for the Update task does not always display correctly on non-English systems. (Reference: 623460) Workaround — There is no current workaround. |
Cluster issues| • | Issue — In cluster environments with more than one cluster server managed by the ePolicy Orchestrator server, agent communications report the cluster IP address instead of the node IP address. This can cause a problem when one node fails over and a passive node becomes active. When this scenario occurs, the server can no longer communicate with the passive node because it has the wrong IP address. (Reference: 360552) Workaround — There is currently no workaround for this issue. The IP address is corrected automatically, and the communication channel restored, at the passive node's next agent-server communication. |
Reporting and logging issues| • | Issue — When installing managed products on an end node, the server task log might not correctly report installations that have failed. (Reference: 575767) Workaround — The task's final status is reported as failed, and the exact product whose installation failed can be deduced by examining the products installed with that task. |
Documentation issues| 1 | Issue — The McAfee Agent Beta 1 help extension is not automatically installed when checking the agent product extension into your server and must be installed manually. Workaround — To install the help extension: | a | Download the help_msa_460.zip file to a temporary location from one of the following: | • | The ePolicy Orchestrator Software Manager (Menu | Software | Software Manager). | | • | The root folder of the McAfee Agent Beta 1 software download package. | | • | The McAfee Agent Beta download site. |
| | b | From within the ePolicy Orchestrator interface, click Menu | Software | Extensions. | | c | In the Extensions page click Install and browse to the location where you downloaded the extension, then click OK. | | d | Click OK to confirm the installation. |
| | 2 | Issue — All product documentation provided with the McAfee Agent 4.6 Beta release is in draft format. As a result, some information might be incorrect. Workaround — There is no current workaround. |
http://download.nai.com/products/naibeta-download/MA_460/MA_460_Beta1_Readme.html
| 
发表于 2010-10-21 14:39:19
