Release Notes for McAfee Agent 4.0

Thank you for using McAfee Agent 4.0. This document contains important information about this release. We strongly recommend that you read the sections of the document appropriate to your operating system.

Contents

New features

This section describes new and updated features in the current release of the software.

Support for new operating systems

Microsoft Windows Server 2008 (last release prior to this document’s publication date)

Laptops distinguished from desktops by properties

Laptops running Windows operating systems are differentiated from desktops, allowing separate ePolicy Orchestrator policies for each.

New installer technology

Microsoft Windows Installer (MSI) technology replaces the previous installation technology. MSI technology provides the ability to:

  • Self-repair damaged or missing installation files.
  • Perform a rollback to the agent previously installed by MSI when the installation of a newer version generates an error.
  • Distribute the installation package to Administrative Installation Points on the network from which the package can be run.
  • Use Active Directory to make the installation package accessible to users who might otherwise not be able to access it.
  • Avoid installation failures when upgrading to a later version of the agent, thus eliminating the use of the /forceinstall command-line switch except for certain specific purposes. For additional information about /forceinstall see Installing the agent by force

Expanded identification information of SuperAgent

The Sitelist.xml file now provides DNS and Netbios information along with the IP address of SuperAgents, facilitating identification of SuperAgents that do not have a static IP address.

Multi-language packages

The agent installation package includes support for thirteen languages, eliminating the need for language packs.

Multiple repositories

Three repositories (Current, Previous and Evaluation) are provided. If you are running McAfee Agent 4.0 and ePolicy Orchestrator 4.0, you can check any package into any of the repository branches. This facilitates controlled testing and rollout of new product releases and patches as well as engines and DATs.

Remote configuration of proxy settings for HTTP and FTP

Laptop users of Windows can configure proxy settings for downloading McAfee VirusScan updates while in the field. See Allowing users to configure proxy settings for details.

Supported products

These products are supported in this release:

  • Data Loss Prevention 2.0
  • ePolicy Orchestrator 3.6, 3.61 and 4.0
  • GroupShield for Lotus Domino 7.0
  • GroupShield for Microsoft Exchange 6.0.2 and 6.0.3 (with SpamKiller), and 7.0
  • Host Intrusion Prevention (Windows only) 6.1 and 7.0
  • Network Access Control 2.0 and 2.5.
  • PortalShield 1.01 and 2.0
  • SecurityShield 1.0
  • SiteAdvisor Enterprise 1.5
  • System Compliance Profiler 1.1 and 2.0
  • VirusScan Enterprise 8.0i and 8.5i (with AntiSpyware Enterprise)

System requirements

This section specifies the system requirements for McAfee Agent 4.0.

  • Installed disk space — 14–17MB, including log files
  • Memory — 128MB RAM minimum, 256MB RAM recommended
  • Processor — Intel or compatible; Intel Pentium or Celeron (recommended); Macintosh OS 10.4 or later on Intel and PowerPC; SPARC; PA-RISC.
  • Processor speed — 133MHz minimum
  • Operating system:
    • Solaris 8
    • Solaris 9
    • Solaris 10 (32- and 64-bit on Sparc)
    • 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 1and 2
    • Windows XP Professional, x64 SP 2
    • Windows XP Tablet PC 2005
    • Windows Vista
    • Windows Vista x64
    • 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.

Installation and upgrade

This section provides instructions for installing and upgrading McAfee Agent 4.0 for use with ePolicy Orchestrator versions 3.6.x and 4.0.

Tasks

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.
Tasks

Installing on Windows using ePolicy Orchestrator 3.6.x

You must have administrative privileges to perform this task.

  1. Download and extract the agent package, MA400WIN.zip.
  2. Check in the NAP file,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 on client systems:
    • Push an agent using the Send Agent Install option.
    • For third party deployment methods, create an agent installation package, FRAMEPKG.EXE, using the Agent Installation Package Creation wizard.
    • Create a deployment task.

Installing on Solaris with ePolicy Orchestrator 3.6.x

You must have root privileges on the Solaris system to perform this task.

  1. Download and extract the agent package, MA400SLR.zip.
  2. Install CMA370.nap into ePolicy Orchestrator. See ePolicy Orchestrator documentation for information on using the Add NAP function.
  3. Copy MFEcma.pkg from the extracted package to the Solaris computer.
  4. On the client, open Terminal and switch to the location where MFEcma.pkg was copied.
  5. Run the command: pkgadd -d MFEcma.pkg MFEcma
  6. Click All or press Enter in response to the instruction “Select package(s) you wish to process“.
  7. When prompted:
    1. Type Y in response to the question: Is your ePO server version less than 4.0?
    2. Type the IP address of the system containing the ePolicy Orchestrator server.
    3. Type the agent-to-server port number of the ePolicy Orchestrator server.
    4. To start the agent service immediately, type Y in response to the question: Do you want to start agent service?
      Note: To start the service later, type N. You can start the agent at any time by running the command: /etc/init.d/cma start.
      When the message “Agent successfully installed“ appears in Terminal, verify that the agent process is running by running: /etc/init.d cma status.
    5. Following the message “This package contains scripts which will be executed with super-user permission during the process of installing this package,” type Y; in response to the question: Do you want to continue with the installation of MFEcma? typing N terminates the installation.

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 each of the supported operating systems.
Tasks

Installing on Windows using ePolicy Orchestrator 4.0

You must have administrator privileges 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.

  1. Download both the agent extension, EPOAGENTMETA.zip and the agent package, MA400WIN.zip to the system containing the ePolicy Orchestrator server.
  2. Install the agent extension:
    1. In the ePolicy Orchestrator 4.0 console, click Configuration.
    2. On the Extensions tab, click Install extension.
    3. Browse to the location containing EPOAGENTMETA.zip, select it and click OK. The Install Extensions summary page appears.
    4. Click OK to complete the installation of the extension.
  3. 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 the Current repository branch.
    1. In ePolicy Orchestrator, click Software.
    2. Click Check In Package.
    3. Browse to MA400WIN.zip, select it and click Next.
    4. Ensure that Current is selected in the Branch field.
    5. Click Save.
  4. Create a deployment task or push the agent to client systems. If using the push method, follow these steps:
    1. In ePolicy Orchestrator, click Systems
    2. Select the target systems or groups.
    3. Click Deploy Agent.
    4. Select the version of the agent to be deployed.
    5. Type valid credentials in the Domain, User name, and Password fields.
    6. Click OK.

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). Installation of the package requires administrator credentials.
  1. Download both the agent extension, EPOAGENTMETA.zip and the agent package, MA400WIN.zip to the system containing the ePolicy Orchestrator server.
  2. Install the agent extension:
    1. In the ePolicy Orchestrator 4.0 console, click Configuration.
    2. On the Extensions tab, click Install extension.
    3. Browse to the location containing EPOAGENTMETA.zip, select it and click OK. The Install Extensions summary page appears.
    4. Click OK to complete the installation of the extension.
  3. Using the ePolicy Orchestrator 4.0 console, check agent package into one of the repository branches, Current (default), Previous or Evaluation.
  4. Create an installation package:
    1. In the ePolicy Orchestrator 4.0 console, click Systems.
    2. Click New Systems, at the bottom of the System Tree.
    3. Select Create and download agent installation package.
    4. Deselect Use Credentials.
    5. Click OK. The Download file dialog box opens.
    6. Select FRAMEPKG.EXE and save it to the desktop.
  5. 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.
  6. To embed credentials, modify the local security policy on the client computers:
    1. Log on to the desired computer using a user account with local administrator permissions.
    2. Run SECPOL.MSC to open the Local Security Settings dialog box.
    3. In the console tree under Security Settings | Local Policies, select User Rights Assignment.
    4. In the details pane, double-click Impersonate a client after authentication in the Policy column to open the Local Security Policy Setting dialog box.
    5. Click Add to open the Select Users or Groups dialog box.
    6. Select the user or group that the user is likely to run as (for example, Everyone or Users), then click Add.
    7. Click OK.
    Tip: On Windows 2000 computers, you need to restart the computer before deploying the package

Installing on Solaris with ePolicy Orchestrator 4.0

You must have root privileges on the Solaris system to perform this task. The agent extension must be installed on the ePolicy Orchestrator server before the agent is installed on any clients.

  1. Download both the agent extension, EPOAGENTMETA.zip and the agent package, MA400SLR.zip to the system containing the ePolicy Orchestrator server.
  2. Install the agent extension, as follows:
    1. In the ePolicy Orchestrator 4.0 console, click Configuration.
    2. On the Extensions tab, click Install extension.
    3. Browse to the location containing EPOAGENTMETA.zip, select it and click OK. The Install Extensions summary page appears.
    4. Click OK to complete the installation of the extension.
  3. Using the ePolicy Orchestrator 4.0 console, check agent package into one of the repository branches, Current (default), Previous or Evaluation.
    Tip: The path includes the name of the selected repository. For example, if checked into the Current branch of the ePolicy Orchestrator software repository, the path of the required files is: C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3700SLR\Install\0409.
  4. Copy the file install.sh from the repository selected in the previous step to the target Solaris client(s).
  5. Log on to the target client as “root.”
  6. On the client, open Terminal, then switch to the location where install.sh was copied.
  7. Run the command: chmod +x install.sh
  8. Run the command: ./install.sh -i
  9. To start the agent service immediately, type Y in response to the question: Do you want to start agent service?
    Note:

    If you want to start the service later, type N. You can start the agent at any time by running the command: /etc/init.d/cma start.

    Upon completion, the message “Agent successfully installed“ appears. To verify the success of the installation, run the command: /etc/init.d/cma status.

Upgrading

This section provides instructions for upgrading the agent from versions 3.5.5, 3.6, and 3.7 to McAfee Agent 4.0. These instructions apply only to systems using ePolicy Orchestrator 3.6.

Agent version 3.6 (a Windows agent) cannot be upgraded to version 3.7 (a UNIX version).

Tasks

Upgrading on Windows using FramePkg_upd.exe

You must have administrative privileges to perform this task.

  1. Download and extract the agent package, MA400WIN.zip, to a temporary location.
  2. Copy FramePkg_upd.exe to a location on the target client.
  3. 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.

Upgrading on Solaris platforms

  1. Download the agent package MA400SLR zip, and check it into the ePolicy Orchestrator software repository intended to serve as the source for the target clients.
  2. In ePolicy Orchestrator, create a deployment task that pushes the client to the target(s).
    1. In ePolicy Orchestrator, click Systems
    2. Select the target systems or groups.
    3. Click Deploy Agent.
    4. Select the version of the agent to be deployed.
    5. Type valid credentials in the Domain, User name, and Password fields.
    6. Click OK.

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. Use the list of tasks as a menu from which to select those that suit your circumstances and preferences.
Tasks

Installing the agent and data in their default locations using default site list and key information

Use this command to install the agent, site list and keys in their default locations. This command is the equivalent of double-clicking the program file in the installation package.

framepkg.exe

Installing the agent in specified folders

Use this command to install the agent in a folder other than the default. The example shown here specifies a folder for the installation files (instdir) and a folder for the data files (datadir). These can be the same or different folders.

framepkg.exe /install=agent /instdir=<target folder name> /datadir=<target folder name>

Installing the agent with user-selected policies

Use this command for installation and upgrade to include policies selected by the administrator rather than the default policies.

framepkg.exe /install=agent /agentpolicy=<full path of user-defined server.xml file>

Note: Policies are stored in a file, server.xml. To create this file:
  1. Configure the policies on an ePolicy Orchestrator server.
  2. Enforce the policies on a selected client. The client’s server.xml file now includes the user-selected policies. The server.xml can be found on the client at Documents and Settings\All Users\Application Data\McAfee\ Common Framework.
  3. Copy the new server.xml file from the client to a shared location.

Installing the agent and specifying the log folder

Use this command to install the agent in its default location and specify a log file other than the default log file as the record of the agent’s activities.

framepkg.exe /install=agent /logdir=<target folder name>

Note: The /logdir parameter can be appended to other installation 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 reqseckey.bin) other than the defaults. This command is useful when upgrading an agent using framepkg_upd.exe. It specifies the server with which the agent communicates irrespective of the site information embedded in the original installation package.

framepkg.exe /install=agent /siteinfo=<full path of sitelist.xml>

The security keys must be located in the same folder as the site list. Use ePolicy Orchestrator to export the files:

  1. Export the siteinfo file:
    1. Select Software | Master Repository.
    2. Click Export Sitelist.
    3. Save the file to a new location.
  2. Export the security keys:
    1. Select Configuration | Server Settings | Security Keys, and click Edit.
    2. Select Master Agent-server secure communication key, and click Export.
    3. Save the files to the same location as the siteinfo file.

Installing the agent by force

Use this command to delete the currently installed agent and install a different agent only when:

  • Downgrading to an earlier version of the agent.
  • Changing the names of the folders that contain the agent.
  • Restoring the agent’s settings to a default state.

framepkg.exe /install=agent /forceinstall

Note: McAfee strongly advises against using /forceinstall to install a new agent because a forceinstall:
  • Deletes current program files and restores data files to a default state. As a result, all user-configured repositories and user-created tasks are lost.
  • Removes the currently installed agent and introduces the risk that installation of the replacement agent could fail. As a result, one or more systems could have no agent at all.
  • Requires on occasion a restart of the 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 /defaultpermissions

Installing silently

Use this command to install the agent without displaying information dialog boxes on the client.

framepkg.exe /install=agent /s or framepkg.exe /install=agent /silent

Installing with specification of interface and log file language

Use this command to install the agent and specify a language other than the target computer’s native language.

framepkg.exe /install=agent /uselanguage=<language code>

Language codes are:

Language Code
Chinese (Simplified) 0804
Chinese (Traditional) 0404
Dutch 0413
English 0409
French 040C
German 0407
Italian 0410
Japanese 0411
Korean 0412
Polish 0415
Portuguese 0416
Spanish 040A
Swedish 041D
Note: To restore the computer’s native language, type /resetlanguage

Upgrading agent to a new version

Use either command to upgrade the agent to a new version.

framepkg_upd.exe or framepkg.exe /upgrade

Using these commands is the equivalent of double-clicking framepkg_upd.exe in the installation package.

Uninstalling the agent

Some managed products incorporate their own copies of the agent. Uninstalling the agent may involve removing the agent that controls managed mode and removing or upgrading the agent(s) that are embedded in products such as McAfee VirusScan Enterprise and McAfee Host Intrusion Prevention.
  • Uninstall the agent that controls ePolicy Orchestrator managed mode and upgrading the agent(s) embedded in managed products:

    frminst.exe /remove=agent

  • Uninstall the agent that controls ePolicy Orchestrator managed mode and the agents embedded in managed products if they are not in use:

    frminst.exe /uninstall

  • Uninstall the agent that controls ePolicy Orchestrator managed mode and the agents embedded in managed products whether or not they are in use:

    frminst.exe /forceuninstall

Converting from unmanaged mode to managed mode

Use this task to convert a client currently operating in unmanaged mode to managed mode.

If the sitelist.xml is from ePolicy Orchestrator 4.0.0 or later, the security keys must be located in the same folder as the site list.

frminst.exe /install=agent /siteinfo=<full path of target server’s sitelist.xml file>

Converting from managed mode to unmanaged mode

Use this task to convert a client currently operating in managed mode to unmanaged mode.

frminst.exe /remove=agent

Changing server

Use this task to change the server with which a client communicates.

The security keys must be located in the same folder as the site list.

frminst.exe /siteinfo=<full path of target server’s sitelist.xml file>

Allowing users to configure proxy settings

Laptop users of Windows can configure proxy settings for downloading McAfee VirusScan updates while in the field. This requires making changes in the ePolicy Orchestrator console and in the VirusScan console. The ePolicy Orchestrator changes must be completed before making the VirusScan changes.

Changes in the ePolicy Orchestrator console

You must have ePolicy Orchestrator administrator privileges to perform this task.
  1. Select Systems | System Tree and select or create the 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 Default”) and click “Edit.”
  6. Click Proxy.
  7. Select “Use Internet Explorer settings (Windows only),” then select “Allow user to configure proxy settings.” The new policy is enforced at the next agent-to-server communication interval (ASCI). Alternatively, you can trigger enforcement by invoking an agent wake-up call. See the ePolicy Orchestrator Product Guide for instructions.

Changes in the VirusScan console

Any remote user who can access VirusScan Enterprise can perform this task.
  1. From the Tools menu, select Edit AutoUpdate Repository List.
  2. Select the Proxy settings tab.
  3. Select “Use Internet Explorer settings (Windows only),” then select “Allow user to configure proxy settings.”
  4. Click Configure, then supply the required HTTP and FTP information and click OK.

Known issues

Known issues in this release include:

  1. The upgrade to McAfee Agent 4.0 may fail if you have installed McAfee Host Intrusion Prevention 7.x or McAfee Data Loss Prevention 2.1 on a system running VirusScan Enterprise 8.5 and you have not restarted that system. McAfee strongly recommends that you restart any such computers before installing the agent. You may want to schedule the agent upgrade to coincide with your server regular periodic maintenance when restarts are likely to be required.
  2. If McAfee Host Intrusion Prevention Firewall is enabled the McAfee Agent 4.0 updating feature fails unless there is a Firewall Rule that allows the following traffic:
    • Direction: Outgoing
    • Transport Protocol: TCP
    • Local Service: 1024-65535
    • Remote Service: <Agent-server communication port>
    • Remote Address: <address of ePolicy Orchestrator server>
    • Process: McScript_InUse.exe

    If you use Quarantine mode, the same rule must be added to the Quarantine Rules policy to avoid or correct the updating failure. You must restart the client after adding the rule to the Quarantine policies.

  3. If you are running McAfee Host Intrusion Prevention 6.1, you may receive a message that McScript_InUse (the McAfee updater) has encountered a problem and must quit. This message is generated erroneously after McScript_InUse has completed its processing task and is being removed from memory. The message can be safely ignored.
  4. Including a Windows reserved word, such as the file name extension CON in the path of the SuperAgent, can result in the creation of an unwanted and undeletable file. If created at the root of C:\, the file’s path is C:\CON. Other reserved words that can produce similarly undesired results include: PRN, AUX, NUL, COM*, LPT*. Do not include Windows reserved words when naming files and folders for use with McAfee Agent 4.0.
  5. If VirusScan Enterprise is installed in unmanaged mode with McAfee Agent 4.0, the agent is not uninstalled when VirusScan is removed.
  6. It is possible to assign an operating system-specific task to a group of computers that includes a variety of operating systems. Agents on those computers only execute the task if they are running the appropriate operating system. For instance, if you assign a VirusScan Enterprise deployment task to a group of computers that includes Linux servers, only the computers running Windows actually install VirusScan.
  7. McAfee Agent 4.0 is not compatible with the Microsoft Data Execution Prevention (DEP) feature.
  8. The McAfee Security single tray icon does not appear on 64-bit systems.
  9. The McAfee Security single tray icon may display a character (i) indicating the presence of additional information even if no additional information is present.
  10. If McAfee Agent 4.0 is installed on a client and you want to:
    • use a server running ePolicy Orchestrator 4.0 to deploy ePO agent 3.6, the installation of the agent will fail.
    • use ePO agent 3.6 on the clients, use the “force installation” option to downgrade from McAfee Agent 4.0. To use this option, select “Systems”. On the “System Tree” dialog box, select one or more existing systems and click “Deploy Agents”. Then, on the “Deploy McAfee Agent” dialog box, select “Force installation over existing version”. (Note: If the target system is not already listed, you must first create it by selecting “New Systems” on the “System Tree,” defining it on the “New Systems” dialog box and then selecting it on the “System Tree” dialog box).
    • preserve McAfee Agent 4.0 on the clients to redirect their communication to a new ePolicy Orchestrator server, or to apply ePolicy Orchestrator Managed Mode to them, check McAfee Agent 4.0 into the ePolicy Orchestrator repository and deploy it.
  11. You cannot deploy the agent for Solaris from an Internet Information Services (IIS) 6.0 HTTP repository.
  12. The Windows MSI installer does not distinguish identically named files in different paths. As a consequence, it could display a “Files In Use” message if a file being installed has the same name as another file located in a different folder, although none of the files being installed is, in fact, in use. When installing McAfee Agent 4.0 while an ePolicy Orchestrator 3.6 console is open, the “Files In Use” message may instruct the user to close ePolicy Orchestrator. To proceed with the installation, click “Ignore”, or close ePolicy Orchestrator and then click “Retry.”
  13. If you use framepkg_upd.exe and have a beta version earlier than build 1085 installed, you need to specify /siteinfo=<path to sitelist> on the command line. If not, agent.ini and server.xml will be missing.

License attributions

This product includes or may include:

Software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). | Cryptographic software written by Eric A. Young and software written by Tim J. Hudson | Some software programs that are licensed (or sublicensed) to the user under the GNU General Public License (GPL) or other similar Free Software licenses which, among other rights, permit the user to copy, modify and redistribute certain programs, or portions thereof, and have access to the source code. The GPL requires that for any software covered under the GPL, which is distributed to someone in an executable binary format, that the source code also be made available to those users. 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. * Software originally written by Henry Spencer, Copyright 1992, 1993, 1994, 1997 Henry Spencer. | Software originally written by Robert Nordier, Copyright © 1996-7 Robert Nordier. | Software written by Douglas W. Sauder. | Software developed by the Apache Software Foundation (http://www.apache.org/). A copy of the license agreement for this software can be found at www.apache.org/licenses/LICENSE-2.0.txt. | International Components for Unicode ("ICU") Copyright © 1995-2002 International Business Machines Corporation and others. | Software developed by CrystalClear Software, Inc., Copyright © 2000 CrystalClear Software, Inc. | FEAD® Optimizer® technology, Copyright Netopsystems AG, Berlin, Germany. | Outside In® Viewer Technology © 1992-2001 Stellent Chicago, Inc. and/or Outside In® HTML Export, © 2001 Stellent Chicago, Inc. | Software copyrighted by Thai Open Source Software Center Ltd. and Clark Cooper, © 1998, 1999, 2000. | Software copyrighted by Expat maintainers. | Software copyrighted by The Regents of the University of California, © 1996, 1989, 1998-2000. | Software copyrighted by Gunnar Ritter. | Software copyrighted by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A., © 2003. | Software copyrighted by Gisle Aas. © 1995-2003. | Software copyrighted by Michael A. Chase, © 1999-2000. * Software copyrighted 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 Brad Appleton, © 1996-1999. | Software copyrighted by Michael G. Schwern, © 2001. | Software copyrighted by Graham Barr, © 1998. | Software copyrighted by Larry Wall and Clark Cooper, © 1998-2000. | Software copyrighted by Frodo Looijaard, © 1997. | Software copyrighted by the Python Software Foundation, Copyright © 2001, 2002, 2003. A copy of the license agreement for this software can be found at www.python.org. | Software copyrighted by Beman Dawes, © 1994-1999, 2002. | Software written by Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek © 1997-2000 University of Notre Dame. | Software copyrighted by Simone Bordet & Marco Cravero, © 2002. | Software copyrighted by Stephen Purcell, © 2001. | Software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). | Software copyrighted by International Business Machines Corporation and others, © 1995-2003. | Software developed by the University of California, Berkeley and its contributors. | Software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http:// www.modssl.org/). | Software copyrighted by Kevlin Henney, © 2000-2002. | Software copyrighted by Peter Dimov and Multi Media Ltd. © 2001, 2002. | Software copyrighted by David Abrahams, © 2001, 2002. See http://www.boost.org/libs/bind/bind.html for documentation. | Software copyrighted by Steve Cleary, Beman Dawes, Howard Hinnant & John Maddock, © 2000. | Software copyrighted by Boost.org, © 1999-2002. | Software copyrighted by Nicolai M. Josuttis, ©1999. | Software copyrighted by Jeremy Siek, © 1999-2001. | Software copyrighted by Daryle Walker, © 2001. | Software copyrighted by Chuck Allison and Jeremy Siek, © 2001, 2002. | Software copyrighted by Samuel Krempp, © 2001. See http://www.boost.org for updates, documentation, and revision history. | Software copyrighted by Doug Gregor (gregod@cs.rpi.edu), © 2001, 2002. | Software copyrighted by Cadenza New Zealand Ltd., © 2000. | Software copyrighted by Jens Maurer, © 2000, 2001. | Software copyrighted by Jaakko Järvi (jaakko.jarvi@cs.utu.fi), © 1999, 2000. | Software copyrighted by Ronald Garcia, © 2002. | Software copyrighted by David Abrahams, Jeremy Siek, and Daryle Walker, © 1999-2001. | Software copyrighted by Stephen Cleary (shammah@voyager.net), © 2000. | Software copyrighted by Housemarque Oy <http://www.housemarque.com>, © 2001. | Software copyrighted by Paul Moore, © 1999. | Software copyrighted by Dr. John Maddock, © 1998-2002. | Software copyrighted by Greg Colvin and Beman Dawes, © 1998, 1999. | Software copyrighted by Peter Dimov, © 2001, 2002. | Software copyrighted by Jeremy Siek and John R. Bandela, © 2001. | Software copyrighted by Joerg Walter and Mathias Koch, © 2000-2002. | Software copyrighted by Carnegie Mellon University © 1989, 1991, 1992. | Software copyrighted by Cambridge Broadband Ltd., © 2001-2003. | Software copyrighted by Sparta, Inc., © 2003-2004. | Software copyrighted by Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications, © 2004. | Software copyrighted by Simon Josefsson, © 2003. | Software copyrighted by Thomas Jacob, © 2003-2004. | Software copyrighted by Advanced Software Engineering Limited, © 2004. | Software copyrighted by Todd C. Miller, © 1998. | Software copyrighted by The Regents of the University of California, © 1990, 1993, with code derived from software contributed to Berkeley by Chris Torek.

COPYRIGHT

COPYRIGHT

Copyright © 2008 McAfee, Inc. All Rights Reserved.

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.

TRADEMARK ATTRIBUTIONS

TRADEMARK ATTRIBUTIONS

AVERT, EPO, EPOLICY ORCHESTRATOR, FLASHBOX, FOUNDSTONE, GROUPSHIELD, HERCULES, INTRUSHIELD, INTRUSION INTELLIGENCE, LINUXSHIELD, MANAGED MAIL PROTECTION, MAX (MCAFEE SECURITYALLIANCE EXCHANGE), MCAFEE, MCAFEE.COM, NETSHIELD, PORTALSHIELD, PREVENTSYS, PROTECTION-IN-DEPTH STRATEGY, PROTECTIONPILOT, SECURE MESSAGING SERVICE, SECURITYALLIANCE, SITEADVISOR, THREATSCAN, TOTAL PROTECTION, VIREX, VIRUSSCAN, WEBSHIELD are registered trademarks or trademarks of McAfee, Inc. and/or its affiliates in the US and/or other countries. McAfee Red in connection with security is distinctive of McAfee brand products. All other registered and unregistered trademarks herein are the sole property of their respective owners.

LICENSE INFORMATION

LICENSE INFORMATION

License Agreement

NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED, WHICH SETS FORTH THE GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANIES YOUR SOFTWARE PACKAGING OR THAT YOU HAVE RECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEB SITE FROM WHICH YOU DOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF APPLICABLE, YOU MAY RETURN THE PRODUCT TO MCAFEE OR THE PLACE OF PURCHASE FOR A FULL REFUND.