                  Release Notes for
        McAfee(R) Common Management Agent(TM)
                Version 3.5.5 Patch 2
           Copyright (C) 2006 McAfee, Inc.
                 All Rights Reserved


==========================================================

Patch Release:8-16-2006

Patch Package:
3.5.5.580

This release was developed for use with:

- McAfee ePolicy Orchestrator 3.5
- McAfee ePolicy Orchestrator 3.6
- McAfee ProtectionPilot 1.1.0
- McAfee ProtectionPilot 1.1.1

Make sure you have installed this version before
using this release.

==========================================================


Thank you for using Common Management Agent(TM)
software. This file contains important information
regarding this release. We strongly recommend that
you read the entire document.


The attached files are provided as is, and with no
warranty either expressed or implied as to their
suitability for any particular use or purpose.
McAfee, Inc. assumes no liability for damages
incurred either directly or indirectly as a result
of the use of these files, including but not limited
to the loss or damage of data or systems, loss of
business or revenue, or incidental damages arising
from their use. Patch files should be applied only
on the advice of McAfee Technical Support, and only
when you are actually experiencing the issue being
addressed by the Patch. Patch files should not be
proactively applied in order to prevent potential
product issues. You are responsible for reading and
following all instructions for preparation,
configuration, and installation of Patch files.
Patch files are not a substitute or replacement for
product Service Packs which may be released by
McAfee, Inc. It is a violation of your software
license agreement to distribute or share these files
with any other person or entity without written
permission from McAfee, Inc. Further, posting of
McAfee Patch files to publicly available Internet
sites is prohibited. McAfee, Inc. reserves the right
to refuse distribution of Patch files to any company
or person guilty of unlawful distribution of McAfee
software products. Questions or issues with McAfee
Patch files should be directed to McAfee Technical
Support.


__________________________________________________________
WHAT'S IN THIS FILE

-   Purpose
-   Resolved Issues
-   Installation
   -   Installation Requirements
   -   Installation Steps
-   Contact Information
-   Copyright & Trademark Attributions
-   License & Patent Information


__________________________________________________________
PURPOSE

This release of the Common Management Agent includes
product enhancements, which improve the robustness
and error checking of the application.


__________________________________________________________
RESOLVED ISSUES

The following list describes the issue from the
previous release of this software product that has
been resolved with this current release.

1.  ISSUE:

    After an upgrade to Common Management Agent
    3.5.5, file not found errors are generated for
    MSCVR71.DLL and MSVCP71.DLL. MSCVR71.DLL and
    MSVCP71.DLL are not found in the path

    RESOLUTION:
    The installer for the Common Management Agent
    now adds the MSCVP71.DLL and MSCVR71.DLL files
    to the Windows system32 directory.



PREVIOUSLY RESOLVED ISSUES for CMA 3.5.5 Patch 1
(3.5.5.568)


1.  ISSUE:
    When the Common Management Agent is upgraded, a
    default policy set is applied to the system
    until it is able to contact the ePolicy
    Orchestrator server and performs another policy
    enforcement.

    RESOLUTION:
    When the Common Management Agent is upgraded via
    the ePolicy Orchestrator deployment task, the
    McAfee Framework Service no longer applies a
    default policy, but retains the existing
    policy.

2.  ISSUE:
    The McAfee Framework Service may fail to stop a
    task when it times out. Future tasks do not run
    because the original task has not stopped. The
    process MCSCRIPT_INUSE.EXE can be seen in the
    Windows Task Manager when a task fails to stop.

    RESOLUTION:
    The McAfee Framework Service can now
    successfully stop a task when it times out.

3.  ISSUE:
    If the McAfee Framework Service is shut down
    after receiving the global updating wakeup call
    and before the updating actually starts,
    updating will fail after restarting the McAfee
    Framework Service.

    RESOLUTION:
    Updating now succeeds, even if the McAfee
    Framework Service is shut down after receiving
    the global updating wakeup call and before the
    updating actually starts.

4.  ISSUE:
    A Common Management Agent (CMA) 3.5.5
    installation package with embedded credentials,
    that was created on ePolicy Orchetrator 3.0.x,
    fails to install.

    RESOLUTION:
    A CMA 3.5.5 installation package with embedded
    credentials, that was created on ePolicy
    Orchetrator 3.0.x, now installs successfully.

5.  ISSUE:
    Downloading from FTP repositories may fail if
    the name of the top directory of the FTP
    repository is shorter than 4 characters.

    RESOLUTION:
    Downloading from FTP repositories now succeeds,
    even if the name of the top directory of the FTP
    repository is shorter than 4 characters.

6.  ISSUE:
    The McAfee Framework Service leaves zip files
    open after downloading and extracting them
    during software installation.

    RESOLUTION:
    The McAfee Framework Service now closes and
    deletes the zip files after downloading and
    extraction.

7.  ISSUE:
    The McAfee Framework Service fails to start
    because of incorrect data written to
    FrameworkManifest.xml.

    RESOLUTION:
    The McAfee Framework Service no longer writes
    incorrect data to FrameworkManifest.xml.

8.  ISSUE:
    VirusScan Enterprise 7.1.0 events are not sent
    to the ePolicy Orchestrator server after
    upgrading the Common Management Agent to 3.5.5.

    RESOLUTION:
    VirusScan Enterprise 7.1.0 events are now sent
    to the ePolicy Orchestrator server.

9.  ISSUE:
    On the ePolicy Orchestrator console, grouping
    clients by IP subnet mask/IP range does not work
    properly if the client has multiple network
    interface cards installed.

    RESOLUTION:
    Grouping clients by IP subnet mask/IP range now
    works properly, even if the client has multiple
    network interface cards installed.

10. ISSUE:
    Downloading from a UNC or local repository fails
    if the "Use Logged On Account" option is
    selected in the repository settings.

    RESOLUTION:
    Downloading from a UNC or local repository no
    longer fails if the "Use Logged On Account"
    option is selected in the repository settings.

11. ISSUE:
    The McAfee Framework Service unnecessarily tries
    to resolve the IP address of SuperAgent
    repositories when subnet value is used to select
    the repositories.

    RESOLUTION:
    The McAfee Framework Service no longer tries to
    resolve the IP address of SuperAgent
    repositories if subnet value is used to select
    repositories.

12. ISSUE:
    McScript_InUse.exe returns an application error,
    "The memory could not be read," if approximately
    15 or more managed products are checked into the
    ePolicy Orchestrator repository.

    RESOLUTION:
    McScript_InUse.exe no longer returns the error
    during updating, even if a large number of
    managed products is checked into the ePolicy
    Orchestrator repository.

13. ISSUE:
    The McAfee Framework Service on a managed
    computer does not attempt to connect to the
    ePolicy Orchestrator server using the DNS name
    or the NetBIOS name after the connection using
    the IP address is actively refused.

    RESOLUTION:
    The McAfee Framework Service on a managed
    computer now tries to connect to the ePolicy
    Orchestrator server using the DNS name and the
    NetBIOS name after the connection using the IP
    address is actively refused.

14. ISSUE:
    The McAfee Framework Service might not install
    Patches, because it wrongly determines that the
    existing version of the product is newer than
    the Patch being applied.

    RESOLUTION:
    The McAfee Framework Service now installs the
    latest version of the product if it is newer
    than the existing version.

15. ISSUE:
    The McAfee Framework Service does not log off
    from the UNC repository after downloading files
    from the repository.

    RESOLUTION:
    The McAfee Framework Service now successfully
    logs off from the UNC repository after
    downloading files.


__________________________________________________________
INSTALLATION

INSTALLATION REQUIREMENTS

To use this release, you must have ePolicy
Orchestrator 3.5, ePolicy Orchestrator 3.6,
ProtectionPilot 1.1.0, or ProtectionPilot 1.1.1
installed on the computer you intend to update with
this release.


INSTALLATION STEPS

1.  Create a temporary folder on the hard drive of
    the ePolicy Orchestrator server.

16. Extract the CMA3552.ZIP file to the temporary
    folder that you created in Step 1.


INSTALLATION STEPS FOR EPOLICY ORCHESTRATOR 3.5 &
3.6

Checking The Agent Package Into The Master
Repository

    NOTE
    You cannot check in packages while pull or
    replication tasks are executing.

1.  Log on to the desired ePolicy Orchestrator
    server using a global administrator user
    account.

2.  In the console tree under "ePolicy Orchestrator"
    | <SERVER>, select "Repository."

3.  In the details pane under "AutoUpdate Tasks,"
    click "Check in package." The "Check in package"
    wizard appears.

4.  Click "Next" to open the package type dialog
    box.

5.  Select "Products or updates," then click "Next."
    The catalog file dialog box appears.

6.  Select the package catalog (PKGCATALOG.Z) file
    from the temporary folder you created in Step 1
    of "Installation Steps." You can type the path
    to this file, or click "Browse" to select it,
    then click "Next." The summary dialog box
    appears.

7.  Click "Finish" to check in the package.

8.  Click "Close" after the package has been checked
    in.

The new agent package is automatically created.


Replicating The Agent Package To Distributed
Repositories

    NOTE
    Since local distributed repositories can only be
    accessed from client computers, replication
    tasks do not copy packages from the master
    repository to local distributed repositories;
    you must manually update local distributed
    repositories with the desired packages.

1.  Log on to the desired ePolicy Orchestrator
    server using a global administrator user
    account.

2.  In the console tree under "ePolicy Orchestrator"
    | <SERVER>, select "Repository."

3.  In the details pane under "AutoUpdate Tasks,"
    click "Replicate now." The "Replicate Now"
    wizard appears.

4.  Click "Next" to open the distributed
    repositories dialog box.

5.  Click "Select All" to select all global and
    SuperAgent distributed repositories, then click
    "Next." The replication type dialog box
    appears.

6.  Select "Incremental replication," then click
    "Finish" to run the task.

7.  Click "Close" after the task has completed.


Deploying The Agent To Client Computers

Although there are numerous methods you can use to
install the agent on computers you want to manage
via ePolicy Orchestrator, we recommend using the
"Deployment" client task. For a list of other
methods and instructions for each, see "Agent
deployment" in the ePolicy Orchestrator Product
Guide.

1.  Log on to the desired ePolicy Orchestrator
    server.

2.  In the console tree under "ePolicy Orchestrator"
    | <SERVER>, right-click "Directory," <SITE>,
    <GROUP>, or <COMPUTER>. The "Policies,"
    "Properties," and "Tasks" tabs appear in the
    details pane.

3.  Click the "Tasks" tab.

4.  Right-click the "Deployment" task, then select
    "Edit Task." The "ePolicy Orchestrator
    Scheduler" dialog box appears.

5.  On the "Task" tab, click "Settings." The "Task
    Settings" dialog box appears.

6.  Deselect "Inherit."

7.  Next to "Agent 3.5.5," select "Install" in
    "Action."

8.  Next to those products that you do not want to
    deploy, select "Ignore" in "Action."

9.  To specify command-line options used when
    installing the agent, click the "..." button
    next to "Agent 3.5.5." For instructions, see
    "Agent installation command-line options" in the
    ePolicy Orchestrator Product Guide.

10. If you want this task to also be enforced during
    the policy enforcement interval, select "Run
    this task at every policy enforcement
    interval."

11. Schedule the task. For instructions, see
    "Scheduling client tasks" in the ePolicy
    Orchestrator Product Guide.

12. Click "OK" to save the current entries.


Monitoring Agent Deployment

You can use the Agent Versions or the Compliance
Issues reports to monitor the deployment of the
agent. For instructions and information, see
"Running reports" and "Agent Versions report
template" or "Compliance Issues report template" in
the ePolicy Orchestrator Product Guide.

The new agent version number is
3.5.5.580


INSTALLATION STEPS FOR PROTECTIONPILOT 1.1.0 &
1.1.1

1.  In ProtectionPilot from the "Server" section,
    click the "Repository" tab. The "Manage
    AutoUpdate Repositories" page appears.

2.  Click "Check In Package" under "Management
    Tasks."

3.  Select "Products and updates," then click
    "Next."

4.  Click "Browse" to locate the file you
    downloaded, and select the package
    (PKGCATALOG.Z) file for the product.

5.  Click "Finish," then "OK." Stop and restart the
    ProtectionPilot server service.

The agent upgrade begins immediately.


__________________________________________________________
CONTACT INFORMATION

THREAT CENTER:  McAfee Avert(R) Labs
    Homepage
       http://www.mcafee.com/us/threat_center/default.asp

    Avert Labs Threat Library
       http://vil.nai.com/

    Avert Labs WebImmune & Submit a Sample (Logon
    credentials required)
       https://www.webimmune.net/default.asp

    Avert Labs DAT Notification Service
       http://vil.nai.com/vil/signup_DAT_notification.aspx

DOWNLOAD SITE
    Homepage
       http://www.mcafee.com/us/downloads/

   -   Product Upgrades (Valid grant number
       required)
   -   Security Updates (DATs, engine)
   -   HotFix and Patch Releases
       -   For Security Vulnerabilities (Available
           to the public)
       -   For Products (ServicePortal account and
           valid grant number required)
   -   Product Evaluation
   -   McAfee Beta Program

TECHNICAL SUPPORT
    Homepage
       http://www.mcafee.com/us/support

    KnowledgeBase Search
       http://knowledge.mcafee.com/

    McAfee Technical Support ServicePortal (Logon
    credentials required)
       https://mysupport.mcafee.com/eservice_enu/start.swe

CUSTOMER SERVICE
   Web:       http://www.mcafee.com/us/support/index.html
              http://www.mcafee.com/us/about/contact/index.html

   Phone:     +1-888-VIRUS NO or +1-888-847-8766
              Monday-Friday, 8 a.m.-8 p.m., Central
              Time
              US, Canada, and Latin America
              toll-free

PROFESSIONAL SERVICES
   -   Enterprise:
       http://www.mcafee.com/us/enterprise/services/index.html

   -   Small & Medium Business:
       http://www.mcafee.com/us/smb/services/index.html


_____________________________________________________
COPYRIGHT & TRADEMARK ATTRIBUTIONS

Copyright (C) 2006 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
orbyany means without the written permission of
McAfee, Inc., or its suppliers or affiliate
companies.


TRADEMARKS

ACTIVE FIREWALL, ACTIVE SECURITY, ACTIVESECURITY
(AND IN KATAKANA), ACTIVESHIELD, CLEAN-UP, DESIGN
(STYLIZED E), DESIGN (STYLIZED N), ENTERCEPT,
EPOLICY ORCHESTRATOR, FIRST AID, FOUNDSTONE,
GROUPSHIELD, GROUPSHIELD (AND IN KATAKANA),
INTRUSHIELD, INTRUSION PREVENTION THROUGH
INNOVATION, MCAFEE, MCAFEE (AND IN KATAKANA), MCAFEE
AND DESIGN, MCAFEE.COM, MCAFEE VIRUSSCAN, NET TOOLS,
NET TOOLS (AND IN KATAKANA), NETSCAN, NETSHIELD,
NUTS & BOLTS, OIL CHANGE, PRIMESUPPORT, SPAMKILLER,
THREATSCAN, TOTAL VIRUS DEFENSE, VIREX, VIRUS FORUM,
VIRUSCAN, VIRUSSCAN, VIRUSSCAN (AND IN KATAKANA),
WEBSCAN, WEBSHIELD, WEBSHIELD (AND IN KATAKANA) are
registered trademarks or trademarks of McAfee, Inc.
and/or its affiliates in the US and/or other
countries. The color 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 & PATENT 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 WEBSITE 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.


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 (C) 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 (C)1995-2002 International Business
Machines Corporation and others. *Software
developed by CrystalClear Software, Inc., Copyright
(C)2000 CrystalClear Software, Inc. *FEAD(R)
Optimizer(R) technology, Copyright Netopsystems AG,
Berlin, Germany. *Outside In(R) Viewer Technology
(C)1992-2001 Stellent Chicago, Inc. and/or Outside
In(R) HTML Export, (C) 2001 Stellent Chicago, Inc.
*Software copyrighted by Thai Open Source Software
Center Ltd. and Clark Cooper, (C) 1998, 1999, 2000.
*Software copyrighted by Expat maintainers.
*Software copyrighted by The Regents of the
University of California, (C) 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., (C)
2003. *Software copyrighted by Gisle Aas. (C)
1995-2003. *Software copyrighted by Michael A.
Chase, (C) 1999-2000. *Software copyrighted by Neil
Winton, (C)1995-1996. *Software copyrighted by RSA
Data Security, Inc., (C) 1990-1992. *Software
copyrighted by Sean M. Burke, (C) 1999, 2000.
*Software copyrighted by Martijn Koster, (C) 1995.
*Software copyrighted by Brad Appleton, (C)
1996-1999.  *Software copyrighted by Michael G.
Schwern, (C)2001. *Software copyrighted by Graham
Barr, (C) 1998. *Software copyrighted by Larry Wall
and Clark Cooper, (C) 1998-2000. *Software
copyrighted by Frodo Looijaard, (C) 1997. *Software
copyrighted by the Python Software Foundation,
Copyright (C) 2001, 2002, 2003. A copy of the
license agreement for this software can be found at
www.python.org. *Software copyrighted by Beman
Dawes, (C) 1994-1999, 2002. *Software written by
Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek (C)
1997-2000 University of Notre Dame. *Software
copyrighted by Simone Bordet & Marco Cravero, (C)
2002. *Software copyrighted by Stephen Purcell, (C)
2001. *Software developed by the Indiana University
Extreme! Lab (http://www.extreme.indiana.edu/).
*Software copyrighted by International Business
Machines Corporation and others, (C) 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, (C) 2000-2002. *Software copyrighted
by Peter Dimov and Multi Media Ltd. (C) 2001, 2002.
*Software copyrighted by David Abrahams, (C) 2001,
2002. See http://www.boost.org/libs/bind/bind.html
for documentation. *Software copyrighted by Steve
Cleary, Beman Dawes, Howard Hinnant & John Maddock,
(C) 2000. *Software copyrighted by Boost.org, (C)
1999-2002. *Software copyrighted by Nicolai M.
Josuttis, (C) 1999. *Software copyrighted by Jeremy
Siek, (C) 1999-2001. *Software copyrighted by
Daryle Walker, (C) 2001. *Software copyrighted by
Chuck Allison and Jeremy Siek, (C) 2001, 2002.
*Software copyrighted by Samuel Krempp, (C) 2001.
See http://www.boost.org for updates, documentation,
and revision history. *Software copyrighted by Doug
Gregor (gregod@cs.rpi.edu), (C) 2001, 2002.
*Software copyrighted by Cadenza New Zealand Ltd.,
(C) 2000. *Software copyrighted by Jens Maurer,
(C)2000, 2001. *Software copyrighted by Jaakko
Jrvi (jaakko.jarvi@cs.utu.fi), (C)1999, 2000.
*Software copyrighted by Ronald Garcia, (C) 2002.
*Software copyrighted by David Abrahams, Jeremy
Siek, and Daryle Walker, (C)1999-2001. *Software
copyrighted by Stephen Cleary (shammah@voyager.net),
(C)2000. *Software copyrighted by Housemarque Oy
<http://www.housemarque.com>, (C) 2001. *Software
copyrighted by Paul Moore, (C) 1999. *Software
copyrighted by Dr. John Maddock, (C) 1998-2002.
*Software copyrighted by Greg Colvin and Beman
Dawes, (C) 1998, 1999. *Software copyrighted by
Peter Dimov, (C) 2001, 2002. *Software copyrighted
by Jeremy Siek and John R. Bandela, (C) 2001.
*Software copyrighted by Joerg Walter and Mathias
Koch, (C) 2000-2002. *Software copyrighted by
Carnegie Mellon University (C) 1989, 1991, 1992.
*Software copyrighted by Cambridge Broadband Ltd.,
(C) 2001-2003. *Software copyrighted by Sparta,
Inc., (C) 2003-2004. *Software copyrighted by
Cisco, Inc and Information Network Center of Beijing
University of Posts and Telecommunications, (C)
2004. *Software copyrighted by Simon Josefsson, (C)
2003. *Software copyrighted by Thomas Jacob, (C)
2003-2004. *Software copyrighted by Advanced
Software Engineering Limited, (C) 2004. *Software
copyrighted by Todd C. Miller, (C) 1998. *Software
copyrighted by The Regents of the University of
California, (C) 1990, 1993, with code derived from
software contributed to Berkeley by Chris Torek.


V3.1.4
