User manual MCAFEE AGENT 4.0 PATCH 2 FOR WINDOWS RELEASE NOTES 10-03-2009

[. . . ] Release Notes for McAfee Agent 4. 0. 0 Patch 2 (Windows) Release Notes for McAfee Agent 4. 0 Patch 2 (Windows) Thank you for using McAfee Agent software version 4. 0. We strongly recommend that you read the entire document. Contents q q q q q q q q q q About this release System requirements Rating Purpose Known issues Resolved issues Installation instructions Allowing users to configure proxy settings Finding release notes and documentation for McAfee enterprise products License attributions About this release Patch Release: March 10, 2009 Patch Package: 4. 0. 0. 1421 This release was developed for use with: q q q q q q q q q q q q q q q q q q q Data Loss Prevention 2. 1 and 2. 2 Endpoint 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. 0 Host Intrusion Prevention (Windows only) 7. 0 Network Access Control 2. 0, 2. 5, and 3. 0 Policy Auditor 5. 0, 5. 0. 1 and 5. 1 PortalShield 1. 0 and 2. 0 Safeboot Encrypted USB 1. 0 Safeboot Endpoint Encryption for File and Folder (Content Encryption) 3. 1. 0 Safeboot Endpoint Encryption for PC (Device Encryption) 5. 1. 5 Safeboot VDisk for Windows 4. 1. 0 SecurityShield 1. 0 SiteAdvisor Enterprise 1. 5, 1. 6. and 2. 0 System Compliance Profiler 1. 1 and 2. 0 VirusScan Enterprise 8. 0i, 8. 5i (Patch 7 and above), and 8. 7i (with AntiSpyware Enterprise) Make sure you have installed the correct version(s) before using this release. System requirements This section specifies the system requirements for McAfee Agent 4. 0. Release Notes for McAfee Agent 4. 0. 0 Patch 2 (Windows) q q q q q 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: r Windows 2000 Professional, SP 4 r Windows 2000 Server, SP 4 r Windows 2000 Advanced Server, SP 4 r Windows 2000 Datacenter Server, SP 4 r Windows 2003 Server, Standard Edition, SP 1 or 2 r Windows 2003 Server, Enterprise Edition, SP 1 or 2 r Windows 2003 Server R2, Standard Edition, SP 1 or 2 r Windows 2003 Server R2, Enterprise Edition, SP 1 or 2 r Windows 2003 Server, Standard x64 Edition, SP 1 or 2 r Windows 2003 Server, Enterprise x64 Edition, SP 1 or 2 r Windows 2003 Server R2, Standard x64 Edition, SP 1 or 2 r Windows 2003 Server R2, Enterprise x64 Edition, SP 1 or 2 r Windows XP Embedded r Windows XP Home, SP 1 and 2 r Windows XP Professional, SP 1, 2, and 3 r Windows XP Professional, x64 SP 2 r Windows XP Tablet PC 2005 r Windows Vista, SP 1 r Windows Vista x64, SP 1 r Windows Server 2008 r Windows Server 2008 x64 This release does not support Windows 95, Windows 98, Windows Millennium Edition or Windows NT. [. . . ] Tasks q q q q Installing on ePolicy Orchestrator 3. 6. x systems Installing on ePolicy Orchestrator 4. 0 systems Upgrading Installing, upgrading and uninstalling using Windows command-line switches Installing on ePolicy Orchestrator 3. 6. x systems This section provides instructions for installing McAfee Agent 4. 0 for use with ePolicy Orchestrator version 3. 6. x on each of the supported operating systems. Check in the NAP file, CMA360. nap, from the extracted agent package to the ePolicy Orchestrator repository. Use one of these methods to install the agent on client systems: r Push an agent using the Send Agent Install option. r For third-party deployment methods, create an agent installation package, FramePkg. exe, using the Agent Installation Package Creation wizard. r Create a deployment task. Installing on ePolicy Orchestrator 4. 0 systems This section provides instructions for installing McAfee Agent 4. 0 for use with ePolicy Orchestrator 4. 0 on Windows using two different methods. Tasks q q Installing on Windows using ePolicy Orchestrator 4. 0 Installing on Windows using third-party deployment methods Installing on Windows using ePolicy Orchestrator 4. 0 You must have administrator rights on the Windows system to perform this task. The agent extension must be installed on the ePolicy Orchestrator server before the agent is installed on any clients. Download the current agent extension, EPOAGENTMETA. zip, and the Patch 2 agent package, MA400P2WIN. zip, to the system containing the ePolicy Orchestrator server. Release Notes for McAfee Agent 4. 0. 0 Patch 2 (Windows) the agent extension: In the ePolicy Orchestrator 4. 0 console, click Configuration. Browse to the location containing EPOAGENTMETA. zip, select it and click OK. Check in the agent package to the ePolicy Orchestrator repository: Note: If installing on a computer running Common Management Agent 3. 6, the package must be checked in to the Current repository branch. Browse to the location containing MA400P2WIN. zip, select it and click Next. c. Installing on Windows using third-party deployment methods The agent extension must be installed on the ePolicy Orchestrator server before the agent is installed on any clients. Tip: This task requires the creation of an agent installation package, FramePkg. exe (see Step 4). Download the current agent extension, EPOAGENTMETA. zip, and the Patch 2 agent package, MA400P2WIN. zip, to the system containing the ePolicy Orchestrator server. Browse to the location containing EPOAGENTMETA. zip, select it and click OK. Using the ePolicy Orchestrator 4. 0 console, check in the agent package to the Current (default) repository branch. Note the location of the downloaded FramePkg. exe to identify it when using your third-party deployment system. You can add parameters and switches as allowed by your deployment system. For a list of available parameters, see Installing, upgrading and uninstalling using Windows command-line switches. Upgrading This section provides instructions for upgrading the agent from versions 3. 5. 5 and 3. 6 to McAfee Agent 4. 0. Release Notes for McAfee Agent 4. 0. 0 Patch 2 (Windows) Upgrading on Windows using FramePkg_upd. exe You must have administrator rights to perform this task. Download and extract the Patch 2 agent package, MA400P2WIN. zip, to a temporary location. From the command line on the client, type <path> /FramePkg_upd. exe /upgrade, where <path> is the location containing the copied file. This command is the equivalent of double-clicking FramePkg_upd. exe in the folder containing the installation package. Installing, upgrading and uninstalling using Windows command-line switches This section describes using selected command-line and MSI parameters to specify installation and upgrading preferences. [. . . ] | Software developed by the University of California, Berkeley and its contributors. Engelschall <rse@engelschall. com> for use in the mod_ssl project (http:// www. modssl. org/). | Software copyrighted by Steve Cleary, Beman Dawes, Howard Hinnant & John Maddock, © 2000. | Software copyrighted by Chuck Allison and Jeremy Siek, © 2001, 2002. [. . . ]