patch4.txt

基于低成本传感器的捷联惯导对准方案研究

 Release Notes for McAfee(R) VirusScan(R) Enterprise
                    Version 8.5i
                       Patch 4
           Copyright (C) 2007 McAfee, Inc.
                 All Rights Reserved


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

Patch Release:    October 16 2007

This release was developed and tested with:

- VirusScan Enterprise:8.5i
- DAT Version:         5126, September 24 2007
- Engine Version:      5.2.00

Make sure you have installed these versions, or
better, before using this release.

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


Thank you for using VirusScan(R) Enterprise
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

-   About This Release
   -   Purpose
   -   Patch 4 Resolved Issues
   -   Patch 3 Resolved Issues
   -   Patch 2 Resolved Issues
   -   Patch 1 Resolved Issues
   -   Known Issues
   -   Files Included With This Release
-   Installation
   -   Installation Requirements
   -   Installation Steps
   -   Installation Steps via ePolicy Orchestrator
   -   HotFix/Patch Reporting
   -   Verifying the Installation
   -   Removing the Patch
-   Contact Information
-   Copyright & Trademark Attributions
-   License Information


__________________________________________________________
ABOUT THIS RELEASE


PURPOSE

This release contains updated binaries in a single
Microsoft Patch installer to address all items
listed in "Resolved Issues" below.

For the most update-to-date copy of this Readme
information, refer to McAfee Support KnowledgeBase
article 613984.

__________________________________________________________
RESOLVED ISSUES

The resolved issues are divided into subsections per
patch, showing when each fix was added to the
compilation.

PATCH 4 RESOLVED ISSUES

1.  ISSUE:
    A crash can occur on some systems when the
    On-Demand Scan Task includes the "Memory for
    rootkits" scan item.

    RESOLUTION:
    The root kit detection driver has been updated
    to better handle different processor
    architectures.

2.  ISSUE:
    When a Quarantine Restore Task is run from
    ePolicy Orchestrator without specifying a
    restore item, the Scan32.exe process runs a full
    scan and does not exit properly, leaving the
    process orphaned.

    RESOLUTION:
    The VirusScan plug-in has been updated to check
    if a restore item is specified. If not, the
    restore task does not run.

3.  ISSUE:
    The VirusScan On-Demand Scanner has no option to
    disable cookie detection alerts in the user
    interface or registry.

    RESOLUTION:
    Alerts for On-Demand Scan cookie detections can
    now be disabled by setting the DWORD
    "bCookieAlerts" registry entry to 0.

    HKLM\SOFTWARE\McAfee\VSCore\Alert Client\VSE

4.  ISSUE:
    When a user is browsing the Internet, the
    On-Access Scanner sometimes logs entries "Not
    scanned (The file is encrypted)" on temporary
    files that are locked for use by the browser.

    RESOLUTION:
    The reporting for these types of detections can
    now be disabled by setting the registry DWORD
    value "DoNotReportSkippedFiles" to 1.

    HKLM\SOFTWARE\McAfee\VSCore\On Access
    Scanner\McShield\Configuration

    NOTE:
    If you previously installed VSE85HF328421, the
    registry entry "DoNotReportSkippedFiles" is
    already set to 1.

5.  ISSUE:
    In environments where the Lotus Notes data
    folder is in a non-standard location, the
    VirusScan Scanner for Lotus Notes installer
    might crash during installation of VirusScan.

    RESOLUTION:
    The VirusScan Scanner for Lotus Notes
    installation files have been updated so that the
    search behavior for notes.ini is more resilient
    to custom Lotus Notes client locations.

6.  ISSUE:
    A crash can occur, where the VirusScan Scanner
    for Lotus Notes failed to initialize properly if
    the first scanned attachment of a session was
    stored in a non-standard attachment format.

    RESOLUTION:
    The VirusScan Scanner for Lotus Notes library
    was changed so that the initialization code
    occurs before the attachment prefixed file name
    handling occurs.

7.  ISSUE:
    With Self Protection enabled, the ability to
    unblock a connection from a remote computer is
    grayed out, even though the logged-on user has
    administrator privileges.

    RESOLUTION:
    VirusScan Statistics has been updated to check
    the credentials of the logged-on user, rather
    then the access level of our services, to
    determine if the "Unblock All Connections Now"
    button should be available.

8.  ISSUE:
    Installation of this Patch enables the option
    "Enable on-access scanning at system startup" if
    it was previously disabled.

    RESOLUTION:
    The Patch installer has been corrected to
    properly preserve the setting.

9.  ISSUE:
    The Patch installer returns a success code, even
    if the Patch failed to install.

    RESOLUTION:
    The Patch installer has been corrected so that
    it only returns a success code if it is actually
    successful.

10. ISSUE:
    Installing the Patch on a system that had only
    one Unwanted Programs exclusion causes that
    exclusion to fail.

    RESOLUTION:
    The installer now corrects a problem where the
    DetectionExclusions registry value was being
    changed from REG_MULTI_SZ to REG_SZ if only one
    value existed.

11. ISSUE:
    On Windows Vista, the administrator cannot
    disable the On-Access Scanner via the VirusScan
    system tray icon.

    RESOLUTION:
    VirusScan Statistics has been updated to check
    the user's logged on credentials, rather then
    the service handle that was used to determine
    access to the McShield service in older
    operating systems.

12. ISSUE:
    A failed reinstallation of VirusScan or a failed
    Patch installation can delete the license,
    resulting in an inoperable product.

    RESOLUTION:
    The Patch installer has been updated to no
    longer cause this state in the event of a failed
    installation.

13. ISSUE:
    An incorrect rule file was packaged with the
    VirusScan NAP file included with Patch 3. This
    caused some of the Access Protection rule
    categories to not appear.

    RESOLUTION:
    A new VirusScan NAP file was created with a
    corrected rule file.

14. ISSUE:
    When Host IPS is installed with VirusScan
    Enterprise, and IPS is disabled, the interface
    for VirusScan Buffer Overflow Protection remains
    grayed out, even though it is active.

    RESOLUTION:
    The Buffer Overflow console plug-in was updated
    to check for the registry flag that is set by
    Host IPS, to tell VirusScan Enterprise that IPS
    is disabled.

15. ISSUE:
    When Self Protection is enabled on a remote
    machine and a user attempts open a remote
    console connection to that machine, the user
    receives an access denied message, and the
    remote console is not opened.

    RESOLUTION:
    The VirusScan Console was updated to make the
    connection to the remote console more robust.


PATCH 3 RESOLVED ISSUES

1.  ISSUE:
    A D1 bugcheck (blue screen) can occur with
    VirusScan Enterprise 8.5i when installed on
    heavily loaded servers.

    RESOLUTION:
    The Access Protection driver has been updated to
    resolve the issue.

2.  ISSUE:
    A D1 bugcheck (blue screen) can occur with
    VirusScan Enterprise 8.5i when installed on a
    Microsoft Exchange server.

    RESOLUTION:
    The Access Protection driver has been updated to
    resolve the issue.

3.  ISSUE:
    An 8E bugcheck (blue screen) was reported by
    customers and in Microsoft抯 Online Crash
    Analysis (OCA), showing a crash in an
    instruction that could not ordinarily fail.

    RESOLUTION:
    The Link Driver was revised to bring it into
    compliance with guidelines specified in Intel抯
    Core2 Errata AI33, to prevent such unusual
    behavior on affected processors.

4.  ISSUE:
    A 7E bugcheck (blue screen) can occur with
    certain low resource conditions.

    RESOLUTION:
    The Link Driver has been updated to better
    handle scenarios where the system is low on
    resources.

5.  ISSUE:
    On 64-bit systems, VirusScan Statistics causes
    an issue where the user cannot open more then
    one Microsoft Virtual PC image. Virtual PC
    reports insufficient memory.

    RESOLUTION:
    VirusScan Statistics has been updated to resolve
    a memory utilization problem on 64-bit systems.

6.  ISSUE:
    When integrated with the Checkpoint SecureClient
    software, VirusScan Enterprise uses incorrect
    registry values for DAT and Engine version
    information.

    RESOLUTION:
    The binaries for Checkpoint integration have
    been updated to use appropriate registry data.

7.  ISSUE:
    With Access Protections rules set to Maximum
    Security, during the installation, VirusScan
    Enterprise Checkpoint integration fails to query
    the On-Access Scanner service state.

    RESOLUTION:
    The binaries for Checkpoint integration have
    been updated to no longer request a certain
    level of access to the service, which would be
    denied by the higher level of Access Protection
    security.

8.  ISSUE:
    Custom VirusScan Enterprise 8.5i policies are
    lost after upgrading from ePolicy Orchestrator
    3.5 to 3.6.x.

    RESOLUTION:
    The VirusScan NAP file has been updated to
    include additional xml code for mapping policies
    between ePolicy Orchestrator 3.5 and 3.6.x.

    NOTE:
    To migrate the policies correctly, follow the
    instructions under "Installation Steps."


PATCH 2 RESOLVED ISSUES

1.  ISSUE:
    When an AutoUpdate task copies new DAT files
    into the engine folder, VirusScan services and
    Microsoft Outlook can spike CPU utilization in
    excess of one minute.

    RESOLUTION:
    The McTaskManager service has been enhanced so
    that it no longer issues multiple reload
    notifications to the scanners after a DAT
    update.

    NOTE:
    Users who saw a smaller spike after the original
    fix (HF320829) should see more improvement with
    this fix.

2.  ISSUE:
    The Quarantine path cannot be changed for the
    On-Access Scanner via ePolicy Orchestrator or
    Protection Pilot. A registry value was not being
    updated correctly.

    RESOLUTION:
    VirusScan抯 Management Plug-In has been updated