 Release Notes for McAfee(R) ePolicy Orchestrator(R)
                    Version 3.6.1
           Copyright (C) 2006 McAfee, Inc.
                 All Rights Reserved


Thank you for using ePolicy Orchestrator(R)
software. This file contains important information
regarding this release. We strongly recommend that
you read the entire document.



    IMPORTANT:
    McAfee strongly recommends that you use any
    pre-release software (beta or release candidate)
    in a test environment only. Pre-release software
    should not be installed in a production
    environment.

    McAfee does not support automatic upgrading of a
    pre-release version of the software. To upgrade
    to a later beta release, a release candidate, or
    a production release of the software, you must
    first uninstall the existing version of the
    software.


__________________________________________________________
WHAT'S IN THIS FILE

-   Whats Included in this Release
-   Installation & System Requirements
-   Resolved Issues
-   Previously Resolved Issues
-   Known Issues
-   Documentation
-   Participating in the McAfee Beta Program
-   Contact Information
-   Copyright & Trademark Attributions
-   License {& Patent }Information


__________________________________________________________
WHATS INCLUDED IN THIS RELEASE


-   Support for Microsoft SQL 2005 with or without
    Service Pack 1 with SQL 2000 emulation mode
    enabled. (SQL 2005 Express Edition is not
    supported.)

-   Support for Microsoft NT LAN Manager (NTLM)
    version 2.0.

-   Support for 5000 engine reporting.

-   JDK version 1.4.2_10.

-   ePolicy Orchestrator agent version 3.5.5 Patch
    2, NAP version 123 This agent version is a
    rollup of the agent version 3.5 and its
    patches.

-   Java-based notification of point-product
    check-in (for McAfee(R) Policy Enforcer).

-   Previous ePolicy Orchestrator 3.6 patches.

-   Support for server and console remote
    installation through Terminal Services.

-   Support for Microsoft Windows 2003 R2.


__________________________________________________________
INSTALLATION AND SYSTEM REQUIREMENTS

Please see product documentation for complete
information on installation and system
requirements.

__________________________________________________________
RESOLVED ISSUES

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

1.  ISSUE:
    Installation fails when the SQL server name
    contains the name of the ePolicy Orchestrator
    server.

    RESOLUTION:
    Installation no longer fails when the SQL server
    name contains the name of the ePolicy
    Orchestrator server.
2.  ISSUE:
    Customers with remote SQL servers could not
    block UDP port 1434 because the port was
    required for ePolicy Orchestrator to communicate
    with a remote SQL server.
    RESOLUTION:
    UDP port 1434 is no longer required for such
    communication.

3.  ISSUE:
    When upgrading from version 3.5 to version 3.6,
    all policies on all systems were set to
    "Enforce."

    RESOLUTION:
    When upgrading from supported versions to
    version 3.6.1, policy enforcement settings are
    preserved.

4.  ISSUE:
    When logged in with a reviewer or site
    administrator account in ePolicy Orchestrator
    version 3.6 patch 2a, clicking on repository
    packages resulted in errors.

    RESOLUTION:
    You can click on repository packages without
    receiving errors when logged into ePolicy
    Orchestrator with any account type.

5.  ISSUE:
    When using NT authentication, a user who is
    logged onto the network as a local administrator
    could not edit policy or check in packages when
    logged onto a remote console in ePolicy
    Orchestrator.

    RESOLUTION:
    Users with such a configuration can now edit
    policy and check in packages when logged onto a
    remote console.

6.  ISSUE:
    The Active Directory Computer Discovery task
    would delete systems from the ePO Directory if
    the DNS record is deleted because the system is
    shut down.

    RESOLUTION:
    The filter used by this task has been modified
    so that such systems are not deleted from the
    Directory when the task runs.

7.  ISSUE:
    Global updating of DAT files would fail if the
    "Move the existing package to the previous
    branch" option was selected.

    RESOLUTION:
    Global updating of DAT files no longer fails if
    the "Move the existing package to the previous
    branch" option is selected.

8.  ISSUE:
    Replication would fail to a UNC distributed
    repository if the password used for replication
    credentials began with a space as the first
    character.

    RESOLUTION:
    Replication no longer fails to any distributed
    repositories if the password used for
    replication credentials begins with a space as
    the first character.

9.  ISSUE:
    Deleting events from the EventDayResolution
    table using the "Removal" tab was unsuccessful.
    Therefore, reports were innaccurate.

    RESOLUTION:
    Deleting events from the EventDayResolution
    table using the "Removal" tab is successful.

10. ISSUE:
    Console would crash during an IP Sorting task
    (when the IP address is reported as NA.

    RESOLUTION:
    Console no longer crashes during an IP Sorting
    task.

11. ISSUE:
    Authentication would fail in the middle of a
    pull task, causing the console to become
    unresponsive, if the proxy did not return
    "Basic" as the first authentication mechanism.
    This caused NAINET.DLL to become unresponsive
    while attempting to match available
    authentication methods with the list supplied by
    proxy. This results in 100% CPU utilization.

    RESOLUTION:
    A proxy not returning "Basic" as the first
    authentication method during a pull task no
    longer causes the console to become
    unresponsive.

12. ISSUE:
    Rogue system sensor deployment wizard reported
    an "Internal server error" when a subnet
    contained any systems with more than 2GB RAM.
    This was because the value was passed as an
    integer (and therefore couldnt exceed 2).

    RESOLUTION:
    This value is no longer passed as an integer.
    The error no longer occurs.

13. ISSUE:
    Running a pull task for the McAfee FTP update
    site in PASV mode would not time out, resulting
    in the console becoming unresponsive.

    RESOLUTION:
    A timeout has been added for the PASV data
    socket.

14. ISSUE:
    After applying ePolicy Orchestrator 3.6 Patch
    2a, the update task would attempt to redeploy
    the rogue system sensor and plugin .DLL file on
    systems hosting the rogue system sensor.

    RESOLUTION:
    The update task no longer attempts to do this.

15. ISSUE:
    After applying ePolicy Orchestrator 3.6 Patch
    2a, trying to remove NAP files fails and
    resulted in the "This product does not support
    named policy objects,
    and cannot be added to the ePO repository"
    error.

    RESOLUTION:
    Removing NAP files no longer fails or results in
    this error.

16. ISSUE:
    Having a large number of tasks could result in
    the Apache service to fail and HTTP connections
    to become unresponsive due to a bottleneck in
    the server logic when large amounts of task
    settings get stored in the cache.

    RESOLUTION:
    The bottleneck in the server logic has been
    fixed. Having a large number of tasks set up no
    longer causes such an issue.

17. ISSUE:
    The "Top 10 Infected Machines" report counts
    were not accurate.

    RESOLUTION:
    The "Top 10 Infected Machines" report counts are
    now accurate.

18. ISSUE:
    In versions 3.5 and 3.6, you could not sort
    computers alphabetically by the "friendly" name
    in Rogue System Detection.

    RESOLUTION:
    You can now sort computers alphabetically in
    Rogue System Detection.

19. ISSUE:
    Count of unprotected systems in the "Product
    Protection Summary" report does not match the
    actual number of systems returned.

    RESOLUTION:
    Count of unprotected systems in the "Product
    Protection Summary" report now matches the
    actual number of systems returned.

20. ISSUE:
    The "Purge Events" task failed to remove events
    from the "RMD_SensorEvents" table in the
    database.

    RESOLTUION:
    The "Purge Events" task successfully removes
    events from the "RMD_SensorEvents" table in the
    database.

21. ISSUE:
    The "Top 10 Infected Users" report count does
    not reflect the actual number of events.

    RESOLUTION:
    The "Top 10 Infected Users" report count now
    reflects the actual number of events.

22. ISSUE:
    New managed systems were not receiving the On
    Demand Scan client tasks until it was disabled
    and re-enabled at the Directory.

    RESOLUTION:
    New managed systems receive all tasks and their
    settings after the first agent-server
    communication.

23. ISSUE:
    The "DAT/Engine Coverage" report would show the
    engine version as N./A due to the format of the
    engine 5000 version number.

    RESOLUTION:
    The "DAT/Engine Coverage" report accurately
    reflects the engine version.

24. ISSUE:
    Replication tasks would fail occassionally and
    cause an exception error when the REPLICA.LOG
    file is accessed by ePolicy Orchestrator.

    RESOLUTION:
    Replication tasks no longer fail or cause
    exception errors when the REPLICA.LOG file is
    accessed by ePolicy Orchestrator.

25. ISSUE:
    Replication tasks would fail occassionally and
    cause a System 2 error.

    RESOLUTION:
    Replication tasks no longer fail and cause
    System 2 errors.

26. ISSUE:
    If the Purge Events task did not commit the
    transactions until the end of task, resulting in
    large transaction logs, long task-execution
    time, and no events being deleted if the task is
    interrupted.

    RESOLUTION:
    With this version, transactions are committed at
    the beginning of the Purge Events task.

27. ISSUE:
    After upgrading to version 3.6, upgraded
    policies could not be duplicated due to slashes
    in their names.

    RESOLUTION:
    After upgrading to version 3.6.1, upgraded
    policies can be duplicated.

28. ISSUE:
    The "Top 10 Infected Users" report count does
    not reflect the actual number of events.

    RESOLUTION:
    The "Top 10 Infected Users" report count now
    reflects the actual number of events.

29. ISSUE:
    If you were upgrading ePolicy Orchestrator and
    had changed the location of the database since
    the original installation, the upgrade would
    fail if you had not updated the location of the
    database in the uninstall key, which was created
    during the previous installation.

    RESOLUTION:
    Upgrading to this version of ePO does not fail
    if you had changed the location of your database
    since the last installation but had not updated
    the install key.



__________________________________________________________
PREVIOUSLY RESOLVED ISSUES

The following list describes issues fixed in
previous patch releases that are included in this
release of the software product.

1.  ISSUE:
    Symantec AntiVirus events are not sent to the
    ePolicy Orchestrator server because the location
    of the event files has been changed.

    RESOLUTION:
    The Symantec AntiVirus 9.0 NAP file and plug-in
    recognize the new location of the Symantec
    AntiVirus events, and the events are uploaded to
    the ePolicy Orchestrator server.

2.  ISSUE:
    The Count of All Connecting Computers query
    includes nodes that are marked for deletion.

    RESOLUTION:
    The Count of All Connecting Computers query no
    longer includes the nodes marked for deletion.

3.  ISSUE:
    Notification events fail when sent to a mail
    server that produces more than one line of 220
    welcome banners.

    RESOLUTION:
    An error no longer occurs when a multi-line
    banner (compliant with RFC 821) from an SMTP
    server is received during an attempt to send
    mail to that server by Notifications or Rogue
    System Detection.

4.  ISSUE:
    When a Directory Search is performed on the
    ePolicy Orchestrator Directory and you attempt
    to move a computer from within the Search window
    to a newly created group, the new group does not
    appear.

    RESOLUTION:
    The display of the ePolicy Orchestrator
    Directory tree in the Directory Search feature
    of the console is now refreshed whenever the
    Directory Search is launched.

5.  ISSUE:
    If a Top 10 infection report is run with a data
    filter set, it may display events with a virus
    name of "---", which represents virus events
    that contain no virus name information.

    RESOLUTION:
    The Top 10 infection reports, when run with a
    data filter, no longer include virus events that
    do not include virus names.

6.  ISSUE:
    Site administrators are able to edit existing IP
    filters at the site level.

    RESOLUTION:
    The user role component of IP filtering has been
    adjusted to match the intended use.

7.  ISSUE:
    The ePolicy Orchestrator console may exit when
    an IP sort is performed and the option "Ignore
    machines with no IP address" is not selected.

    RESOLUTION:
    The ePolicy Orchestrator console no longer exits
    when an IP sort is performed and there are
    client systems that have reported empty IP
    values.

8.  ISSUE:
    When the message, "There were no nodes found
    that met the given search criteria" is returned
    from the Search window, you receive the same
    message when a Send Agent Install is performed
    from the console.

    RESOLUTION:
    The search algorithm has been changed so that it
    only performs searches when the Search dialog
    box is displayed.  This fixes a problem where an
    unintentional search is performed when pressing
    the "Enter" key.

9.  ISSUE:
    When trying to reset inheritance on the Updates
    tab of the ePolicy Orchestrator 3.5.0 agent
    policies configuration page, the checkbox for
    Inherit does not stay selected, even when "Apply
    All" is selected before closing the page.

    RESOLUTION:
    The inherit flag on the Updates policy tab now
    works properly.

10. ISSUE:
    An existing ePolicy Orchestrator Authentication
    user cannot be changed to an NT Authentication
    user.

    RESOLUTION:
    When modifying an existing ePolicy Orchestrator
    user, the NT Authentication radio button is no
    longer grayed out, allowing an existing ePolicy
    Orchestrator Authentication user to be changed
    to an NT Authentication user.

11. ISSUE:
    When logged in as a user that is not a local
    administrator (i.e., a Power User), you may
    experience issues accessing components of the
    console, such as Repository and the ePO Agent
    Update Task.

    RESOLUTION:
    The console has been changed so that it does not
    require local administrative privileges.

12. ISSUE:
    Policy migration during an upgrade from ePolicy
    Orchestrator 3.5 will not handle new products
    released after ePolicy Orchestrator 3.6.

    RESOLUTION:
    If a managed product NAP is installed on ePolicy
    Orchestrator 3.5, and ePolicy Orchestrator is
    upgraded to version 3.6, Patch 2 or later must
    be installed prior to any policy changes or NAP
    check-ins to properly migrate 3.5 policies. This
    applies to product NAP files that ship after
    ePolicy Orchestrator 3.6 was released.

       NOTE:
       The patch installer has been updated so that
       the only policies migrated are those that
       have not already been migrated to the policy
       format for ePolicy Orchestrator 3.6.


13. ISSUE:
    The ePolicy Orchestrator 3.6 Patch 1
    installation overwrites the current checked-in
    Common Management Agent (CMA) NAP file and
    replaces it with the CMA 3.5.0 NAP file.

    RESOLUTION:
    The patch installer no longer overwrites a
    higher version of the CMA NAP file.

14. ISSUE:
    Pull Task fails if the "Use Logged On Account"
    checkbox is selected for the Source Repository.

    RESOLUTION:
    The option "Use Logged On Account" is not
    available after applying Patch 2. For
    pre-existing UNC Source Repositories that use
    this option, the checkbox is still selected but
    the functionality is unavailable. A user must
    supply credentials and deselect "Use logged on
    user" to successfully pull from the UNC Source
    Repository. Deselecting the "Use Logged On
    Account" checkbox permanently grays out this
    checkbox.

15. ISSUE:
    Policies upgraded from ePolicy Orchestrator 3.5
    to 3.6 cannot be exported because their names
    contain slashes.

    RESOLUTION:
    Slashes in the policy object name are replaced
    with underscores in the default export name.

16. ISSUE:
    A pull from a UNC site with an impersonated user
    may cause 401 errors.

    RESOLUTION:
    The ePolicy Orchestrator server removed the
    option to specify "Use Logged On Account" from
    the Source Repository configuration page.

17. ISSUE:
    After renaming or moving a site or group,
    Directory Search may fail to show location, and
    policy enforcement may fail for systems.

    RESOLUTION:
    Directory Search and policy enforcement no
    longer fail after renaming or moving a site or
    group.

18. ISSUE:
    Multiple computers report the same MAC address
    when connecting via VPN, causing computer node
    information to be overwritten in the database.

    RESOLUTION:
    Some dial-up and VPN adapters do not return
    unique MAC addresses. When the ePolicy
    Orchestrator server receives agent properties
    that contain MAC addresses matching these vendor
    codes, the MAC addresses are not used to
    uniquely identify the computer.

19. ISSUE:
    The error: "Failed to process XML file" is
    logged in EVENTPARSER.LOG, even when the event
    is eventually processed.

    RESOLUTION:
    The log message is now changed to a more
    informational message: "Failed to process XML
    file, PKG file will be reprocessed for embedded
    XML."

20. ISSUE:
    Client systems may try to update from the wrong
    repository branch when changing the agents back
    to the current branch from the previous or
    evaluation branch.

    RESOLUTION:
    Client systems update from the correct branch,
    as explicitly defined by the update policy.

21. ISSUE:
    On the Updates tab of the ePolicy Orchestrator
    Agent policy configuration page, the Repository
    Branch Update Selection policy does not reset
    when reset policy inheritance is selected.

    RESOLUTION:
    Repository Branch Update Selection policy now
    resets properly when reset policy inheritance is
    selected.

22. ISSUE:
    In the Update History Subreport, any product
    update events that result from an update task
    launched by a managed product are listed by the
    Event IDs instead of meaningful event
    descriptions.

    RESOLUTION:
    In the Update History Subreport, these types of
    product update events are now listed by
    meaningful event descriptions.

23. ISSUE:
    For any client system with 4GB RAM or more,
    ePolicy Orchestrator reported an incorrect
    amount of total physical memory.

    RESOLUTION:
    ePolicy Orchestrator now reports the correct
    amount of total physical memory on client
    systems.

24. ISSUE:
    Large events forwarded from System Compliance
    Profiler are processed too slowly by Event
    Parser, causing a backlog of events waiting to
    be processed.

    RESOLUTION:
    Changes have been made to significantly improve
    the performance of System Compliance Profiler
    event processing.

25. ISSUE:
    Properties containing localized strings might
    cause the ePolicy Orchestrator server to fail to
    process the properties, and as a result no
    policies are sent to the agent.

    RESOLUTION:
    Properties containing localized strings are now
    processed properly.

26. ISSUE:
    When two or more replications are run
    concurrently, one or more of the replications
    may fail with the following error in the
    EPOAPSVR.LOG: "Failed to save sitelist file
    C:\WINNT\TEMP\SiteList.xml, hr = 0x80070020."

    RESOLUTION:
    Separate temporary folders are now used for each
    replication task, which prevents a race
    condition from occurring, effectively resolving
    this issue.

27. ISSUE:
    When upgrading from ePolicy Orchestrator 3.5,
    the pull now and scheduled pull tasks use the
    NAIFtp site by default.

    RESOLUTION:
    The pull now and scheduled pull tasks now use
    the NAIHttp site by default.

28. ISSUE:
    If the Common Management Agent requests policy
    from the ePolicy Orchestrator (ePO) server and
    fails to download the policy, the ePO server may
    not send a future policy for missed items until
    they have been modified on the server. This
    results in a policy compilation error on the
    client system.

    RESOLUTION:
    When requesting policy, Common Management Agent
    now sends its current policy list to the ePO
    server.  This allows the server to send any
    missing policy.

       NOTE:
       This fix requires Common Management Agent
       3.5.5, which is due to be released in Q1
       2006.

29. ISSUE:
    Event Parser leaks memory when it processes
    server events.

    RESOLUTION:
    Server events no longer cause a memory leak when
    processed by the Event Parser.

30. ISSUE:
    Tomcat leaks memory when running server tasks
    that require web actions, such as pull tasks.

    RESOLUTION:
    Identified memory leaks have been fixed so that
    Tomcat no longer leaks memory when it runs
    server tasks.

31. ISSUE:
    The name of a Registered Executable in the
    External Commands option for Rogue System
    Detection and Notifications cannot be edited.

    RESOLUTION:
    The name of a Registered Executable in the
    External Commands option can now be edited.

32. ISSUE:
    When new content updates for System Compliance
    Profiler are checked into the repository, the
    latest Microsoft patches do not appear in the
    rules configuration screen.

    RESOLUTION:
    The latest Microsoft patches now appear in the
    rules configuration screen after new System
    Compliance Profiler content is checked into the
    repository.

33. ISSUE:
    When a response is set up in Rogue System
    Detection to push the ePO agent with a custom
    installation path, once the response is saved,
    the path reverts back to the default
    installation path for the agent.

    RESOLUTION:
    When the installation path for the ePO agent
    push from the Rogue System Detection interface
    is changed from the default, the path is now
    saved properly.

34. ISSUE:
    When configuring proxy settings, both the
    repository wizard and the edit proxy dialog box
    in the Repository interface do not allow special
    characters, such as the "@" symbol or a period.

    RESOLUTION:
    The HTTP and FTP proxy authentication dialog
    boxes now accept special characters such as the
    "@" symbol and the period.

35. ISSUE:
    From a remote console, if you try to copy a
    package to the current branch from the
    evaluation branch, the progress bar indicates
    that the package was copied successfully, but
    the package is not actually copied to the
    current branch.

    RESOLUTION:
    A remote console can now properly copy a package
    from the evaluation branch to the current
    branch.

36. ISSUE:
    Common Management Agent (CMA) compiles policy
    after each agent-to-server communication due to
    the ePolicy Orchestrator server sending
    unchanged agent meta policy.

    RESOLUTION:
    ePolicy Orchestrator server no longer sends
    unnecessary policy data during every
    agent-to-server communication, preventing the
    need for CMA to compile policy for every
    agent-to-server communication.

37. ISSUE:
    The 3DES algorithm implemented in NAISIGN, which
    is used by SPIPE4 to encrypt and decrypt, has
    poor performance.

    RESOLUTION:
    The code has been revised and encryption and
    decryption performance is substantially
    improved.
38. ISSUE:
    Users are unable to schedule a task for any
    interval less than one hour.

    RESOLUTION:
    Users are now able to enter decimal values, thus
    allowing tasks to be scheduled for intervals
    smaller than one hour.

39. ISSUE:
    Policy settings that contain foreign characters
    are not properly saved in the ePolicy
    Orchestrator database.

    RESOLUTION:
    Policy settings that contain foreign characters
    are now saved properly in the database.

40. ISSUE:
    When non-English characters are entered in
    password fields within ePolicy Orchestrator, the
    passwords may become corrupted during the
    encryption/decryption process.

    RESOLUTION:
    ePolicy Orchestrator now has better support for
    special characters in passwords.

41. ISSUE:
    Property files are not saved to disk in ePolicy
    Orchestrator 3.6, making it difficult to
    troubleshoot failures in processing properties.

    RESOLUTION:
    Debug functionality has been added to
    NAIMSERV.DLL for additional logging and for
    saving defective properties files to the
    DB\Debug directory.

    To enable the additional debug functionality of
    saving malformed agent properties to a debug
    folder, follow these steps:

    1. Open regedit on the ePolicy Orchestrator
    server.

    2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Network
    Associates\ePolicy Orchestrator.

    3. Create a new DWORD value called
    SaveAgentProps and set that DWORD value to 1.

    4. Restart the McAfee ePolicy Orchestrator 3.6.0
    Server (Apache) service.

    The malformed properties files will be saved to
    the ePO\3.6.0\DB\Debug directory in the
    following format:
    <Computer_Name>_<Timestamp>_Props.xml.

       NOTE:
       Only enable this debug functionality for
       troubleshooting purposes because this
       directory will grow without limit. When not
       troubleshooting, set the DWORD value for
       SaveAgentProps to O and restart the McAfee
       ePolicy Orchestrator 3.6.0 Server (Apache)
       service.




__________________________________________________________
KNOWN ISSUES


1.  When upgrading from ePolicy Orchestrator version
    3.6 to version 3.6.1 on a system running the
    McAfee Host Intrusion Prevention 6.0 or later
    client software, the McAfee Host Intrusion
    Prevention Firewall must be set to "Adaptive"
    mode, or disabled during the upgrade process.
    Otherwise, the upgrade fails because DBinit
    traffic is blocked.

2.  When installing or upgrading to ePolicy
    Orchestrator 3.6.1 on a system running a
    firewall product, you must disable the firewall
    before installing or upgrading ePolicy
    Orchestrator. Otherwise, the installation or
    upgrade fails. After completing the installation
    or upgrade, re-enable the firewall and allow
    each of the ePO services in the firewall
    software.

3.  Installing ePolicy Orchestrator from a folder
    with a path or name containing extended or
    double-byte characters fails.

4.  Installing ePolicy Orchestrator on a system with
    a name containing an underscore (_) character
    results in the policy information pages
    appearing blank.

5.  When upgrading to version 3.6.1 from version
    3.5, you must reconfigure your ePolicy
    Orchestrator password if it contains extended
    characters.

6.  In some instances, the Event Parser stops
    functioning when processing System Compliance
    Profiler events. When this happens, close out of
    ePolicy Orchestrator then stop and restart the
    ePolicy Orchestrator services.

7.  When using ePolicy Orchestrator in a clustered
    environment, be sure to make any and all changes
    on the active server. Making changes directly on
    the inactive servers could have unknown
    results.

8.  Currently, ePolicy Orchestrator and servers and
    consoles are not supported on systems running
    Internet Explorer 7 (IE7). McAfee is
    investigating the impact of the IE7 upgrade and
    will be issue a for this release.

    McAfee recommends that customers do not install
    IE7 on any systems running ePolicy Orchestrator
    3.6.1 servers and consoles. The following
    settings for Window OS Automatic Updates feature
    will prevent IE7 from being installed
    automatically.

    Microsoft Windows XP:
    Configure Automatic Updates with either of the
    following options:
   -   Download updates for me, but let me choose
       when to install them. OR
   -   Notify me but don't automatically download or
       install them.

    Microsoft Windows 2003:
    Configure Automatic Updates with either of the
    following options:
   -   Notify me before downloading any updates and
       notify me again before installing them on my
       computer. OR
   -   Download the updates automatically and notify
       me when they are ready to be installed.

    If you have installed IE 7 on such a system, you
    can roll back to IE 6 by going to the
    "Add/Remove Programs" in the "Control Panel" and
    removing "Microsoft Internet Explorer 7."

9.  If you install this version of 3.6.1 on a system
    with a local ePO database, and then change to a
    remote database post-installation (using
    CFGNAIMS.EXE), you must also change two registry
    keys on the ePO server or the local ePO service
    dependencies are not removed. In such a
    situation in a clustered environment, please

    Go to the following registry keys and remove the
    "MSSQL$xxxxx" (where xxxxx is the instance name)
    or "MSSQLSERVER"
    entries from them using RegEdit.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RSDSERVER361
    DependOnService

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EVENTPARSER361
    DependOnService

10. During the installation, you may get a message
    stating that any of the ePO services failed to
    start and asking you to manually start the
    service, when in fact the service is already
    started, please restart the indicated service.

11. Installation may fail if your database has too
    many network protocols enabled on your SQL
    server. McAfee recommends enabling no more than
    "TCP/IP"(required)  and "Named
    Pipes"(recommended) at time of installation or
    upgrade.


__________________________________________________________
NOTE ABOUT THIS RELEASE

The Setup/Plugins/EPOAGENT3000META directory and its
contents were created in preparation for
enhancements to future versions of ePolicy
Orchestrator.

__________________________________________________________
DOCUMENTATION

Documentation is included on the product CD and/or
is available with a valid grant number from the
McAfee download site:

       https://secure.nai.com/us/forms/downloads/upgrades/login.asp

    NOTE:
    Unless otherwise noted, product documentation
    comes as Adobe Acrobat .PDF files. The product
    CD includes the latest version of Acrobat
    Reader, or you can download any version from the
    Adobe web site:

       http://www.adobe.com/products/acrobat/readstep2.html



STANDARD DOCUMENTATION

This product includes the following documentation
set:

-   Installation Guide
    System requirements and instructions for
    installing and starting the software.

-   Product Guide
    Introduction to the product and its features;
    detailed instructions for configuring the
    software; information on deployment, recurring
    tasks, and operating procedures.

-   Help
    High-level and detailed information accessed
    from the software application: Help menu and/or
    Help button for page-level help; right-click
    option for Whats This? help.

-   Release Notes (this ReadMe file)

-   LICENSE Agreement
    The McAfee License Agreement booklet that
    includes all of the license types you can
    purchase for your product. The License Agreement
    presents general terms and conditions for use of
    the licensed product.



ADDITIONAL DOCUMENTATION

-   Getting Started Guide
    An overview of a product solution that describes
    individual products, their installation
    requirements, and a recommended sequence for
    installing multiple products.

-   Evaluation Guide
    Procedures for getting your McAfee product set
    up quickly in a test environment. Includes
    installing, configuring and using your McAfee
    product.

-   Quick Reference Card
    A handy card with information on basic product
    features, routine tasks that you perform often,
    and critical tasks that you perform
    occasionally. A printed card accompanies the
    product CD.


__________________________________________________________
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 AND 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.

PATENTS
Protected by US Patents 6,470,384; 6,493,756;
6,496,875; 6,553,377; 6,553,378.

DBN-001-<EN>

V3.1.4


