background image

Release Notes for McAfee Agent 4.0.0 Patch 2 (Windows)

     

Installed disk space — 14–17 MB, including log files

     

Memory — 128 MB RAM minimum, 256 MB RAM recommended

     

Processor — Intel or compatible; Intel Pentium or Celeron (recommended); Itanium 2 processors.

     

Processor speed — 133 MHz minimum

     

Operating system: 

     

Windows 2000 Professional, SP 4

     

Windows 2000 Server, SP 4

     

Windows 2000 Advanced Server, SP 4

     

Windows 2000 Datacenter Server, SP 4

     

Windows 2003 Server, Standard Edition, SP 1 or 2

     

Windows 2003 Server, Enterprise Edition, SP 1 or 2

     

Windows 2003 Server R2, Standard Edition, SP 1 or 2

     

Windows 2003 Server R2, Enterprise Edition, SP 1 or 2

     

Windows 2003 Server, Standard x64 Edition, SP 1 or 2

     

Windows 2003 Server, Enterprise x64 Edition, SP 1 or 2

     

Windows 2003 Server R2, Standard x64 Edition, SP 1 or 2

     

Windows 2003 Server R2, Enterprise x64 Edition, SP 1 or 2

     

Windows XP Embedded

     

Windows XP Home, SP 1 and 2

     

Windows XP Professional, SP 1, 2, and 3

     

Windows XP Professional, x64 SP 2

     

Windows XP Tablet PC 2005

     

Windows Vista, SP 1

     

Windows Vista x64, SP 1

     

Windows Server 2008

     

Windows Server 2008 x64

This release does not support Windows 95, Windows 98, Windows Millennium Edition or Windows 

NT.

The McAfee Security single tray icon does not appear on 64-bit systems.

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 KB60681 at http://knowledge.mcafee.com for the most current 

information regarding this release. 

Known issues

Known issues in this release of the software are described below:

     

Issue: 

On systems with EMC’s Power Path software installed, the McAfee Agent fails to start and 

the error message “Cannot generate keypair” appears in the Agent_<system name> log file. 

(Reference: 452955, 436864, 445158, 447296, 451228, 437592 ) 

Summary of Contents for Agent 4.0

Page 1: ...t Encryption for Files and Folders 3 1 0 Endpoint Encryption for PC 5 1 5 ePolicy Orchestrator 3 6 1 and 4 0 McAfee Anti Spam for GroupShield 7 0 McAfee Encrypted USB 1 0 McAfee VDisk for Windows 4 1...

Page 2: ...1 Windows Server 2008 Windows Server 2008 x64 This release does not support Windows 95 Windows 98 Windows Millennium Edition or Windows NT The McAfee Security single tray icon does not appear on 64 bi...

Page 3: ...ed during the ping time sorting process 3 Issue When UNC repositories were configured to use the download credentials of the logged on user and the logged on user was not an Administrator the download...

Page 4: ...ectly 11 Issue The error message File is corrupt Downloading complete file again would be incorrectly written to the McScript log file during the update process Reference 440080 445479 Resolution The...

Page 5: ...atadir new folder folder the upgrade process did not remove the old data folder and used the new folder Reference 393182 Resolution Now when using the forceinstall switch and changing the data datadir...

Page 6: ...task now copies the sitestat xml file to the duplicated repository 12 Issue During a managed product update a dialog box could be presented requesting a system reboot The dialog box asked the user if...

Page 7: ...and the agent crashed on the next Policy Enforcement Reference 423070 Resolution The McAfee Agent now detects failed Policy Enforcements and retries the policy compilation until it completes successfu...

Page 8: ...e CMA360 nap from the extracted agent package to the ePolicy Orchestrator repository 3 Check in the agent package to the ePolicy Orchestrator repository 4 Use one of these methods to install the agent...

Page 9: ...stalled on any clients Tip This task requires the creation of an agent installation package FramePkg exe see Step 4 Installation of the package requires administrator rights 1 Download the current age...

Page 10: ...the agent with user selected policies Installing the agent and specifying the log folder Installing the agent with user selected site information and user selected keys Installing the agent by force I...

Page 11: ...ion commands Installing the agent with user selected site information and user selected keys Use this command to install the agent and specify a site list file and security keys srpubkey bin and reqse...

Page 12: ...e system Installing without requiring specific user privileges Use this command to allow all users access to agent files and registry regardless of their user privileges framepkg exe install agent def...

Page 13: ...ducts using it for updating remove it completely frminst exe remove agent Remove the agent completely but only if it is not connected to an ePO server and no point products are using it for updating f...

Page 14: ...systems where proxy settings are to be allowed 2 Select Systems Policy Catalog 3 In the Product field select McAfee Agent 4 In the Category field select General 5 Select a policy for example My Defaul...

Page 15: ...hted by Neil Winton 1995 1996 Software copyrighted by RSA Data Security Inc 1990 1992 Software copyrighted by Sean M Burke 1999 2000 Software copyrighted by Martijn Koster 1995 Software copyrighted by...

Page 16: ...ESTRATOR FOUNDSTONE GROUPSHIELD INTRUSHIELD LINUXSHIELD MAX MCAFEE SECURITYALLIANCE EXCHANGE MCAFEE NETSHIELD PORTALSHIELD PREVENTSYS SECURITYALLIANCE SITEADVISOR TOTAL PROTECTION VIRUSSCAN WEBSHIELD...

Reviews: