4 Replies Latest reply on Dec 13, 2007 2:20 AM by twenden

    CMA 3.6 Patch 3 Release Notes

    twenden
      Common Management Agent 3.6.0 Patch 3 Release Notes


      Environment

      McAfee Common Management Agent 3.6.0
      Microsoft Windows


      Summary

      This Patch is build number:
      3.6.0.574

      Release date: November 28, 2007

      Patch 3 is currently in a phased roll out prior to posting to the McAfee ServicePortal. To obtain Patch 3 for CMA 3.6.0, contact McAfee Technical Support and reference this article number to have a case created and escalated.

      This release was developed for use with:

      *
      McAfee ePolicy Orchestrator 3.6.0
      *
      McAfee ePolicy Orchestrator 3.6.1
      *
      McAfee ePolicy Orchestrator 4.0
      *
      McAfee ProtectionPilot 1.5

      Make sure you have one of these versions installed before using this release.
      ==========================================================

      RESOLVED ISSUES

      1. ISSUE:
      When epoPGPsdk.dll.sig was removed from the Windows\system32 folder and epoPGPsdk.dll was
      not, the Common Management Agent installer failed and the message "Unable to decrypt the
      validation file" was entered in to the trace.log file.

      RESOLUTION:
      The Common Management Agent installer was modified to treat epoPGPsdk.dll.sig and
      epoPGPsdk.dll as a single unit, resulting in epoPGPsdk.dll.sig being removed only when
      epoPGPsdk.dll is successfully removed.

      2. ISSUE:
      The Common Management Agent attempted to get the IP address by connecting to the ePolicy
      Orchestrator server and recording the working socket’s IP address. When it couldn’t reach the
      ePO server, it searched the network adapter table and recorded the IP address of the first
      NIC returned. This resulted in the client’s loopback address being recorded instead of the
      correct IP address.

      RESOLUTION:
      Now when the ePO server cannot be reached, the Common Management Agent uses the IP address from
      the registry. The IP address stored in the registry is updated only after the Common
      Management Agent successfully connects to the ePO server. These rules apply to both property
      collection and SPIPE package creation.

      3. ISSUE:
      When UdaterUI.exe was not running on the Vista and Windows Server 2008 operating systems and
      AutoUpdate was started, the AutoUpdate dialog box was not invoked.

      RESOLUTION:
      The AutoUpdate dialog box is now invoked when UdaterUI.exe is started on the Vista and Windows
      Server 2008 operating systems.

      4. ISSUE:
      If specific files were not in use when a ForceInstall of the Common Management Agent was
      attempted, those files were marked for deletion on reboot and the installer stopped and
      requested a reboot. After the system was rebooted, the files were deleted but the
      installer did not resume. This effectively removed the Common Management Agent from the
      system.

      RESOLUTION:
      The installer now resumes installation once the system is rebooted.

      NOTE:
      When a system is restarted after a ForceInstall, the user account used to log on to that system
      must have administrator credentials. If the user account does not have administrator credentials,
      the installation does not resume.

      5. ISSUE:
      When attempting to deploy VirusScan Enterprise using ePolicy Orchestrator on the Windows Server
      2008 operating system, an error was generated: "VIRUSSCAN 8610 is not supported on this
      platform (WVST:6.0.1)".

      RESOLUTION:
      VirusScan Enterprise can now be deployed using ePolicy Orchestrator on the Windows Server 2008
      operating system.

      6. ISSUE:
      VirusScan Enterprise policy enforcement failed when it attempted to apply VirusScan Enterprise
      policies using ePolicy Orchestrator on the Windows Server 2008 operating system.

      RESOLUTION:
      VirusScan Enterprise policies can now be applied using ePolicy Orchestrator on the Windows Server
      2008 operating system.

      7. ISSUE:
      VirusScan Enterprise policy enforcement failed to deliver VirusScan Enterprise properties to
      ePolicy Orchestrator on the Windows Server 2008 operating system.

      RESOLUTION:
      VirusScan Enterprise properties are now delivered to ePolicy Orchestrator on the Windows
      Server 2008 operating system.

      8. ISSUE:
      When shutting down the Japanese version of Windows 2000 Service Pack 4, the McAfee Single
      Tray Icon process (Mctray.exe) caused Internet Explorer to crash.

      RESOLUTION:
      Mctray.exe no longer crashes Internet Explorer during shutdown on the Japanese version of
      Windows 2000 Service Pack 4.

      9. ISSUE:
      Structured exceptions were caught in CSiteList::SortUsingFindNearest() and
      CNetConnection::UploadFileResponse(), resulting in Common Management Agent communication
      failures.

      RESOLUTION:
      Structured exceptions no longer occur in CSiteList::SortUsingFindNearest() or
      CNetConnection::UploadFileResponse().

      10. ISSUE:
      When updating, the Common Management Agent failed and wrote the message "Update task will
      be re-tried in 3 minutes because update is still in progress" continually in the Agent.log when
      the file sitelist.xml was locked by another process.

      RESOLUTION:
      The sitelist.xml locking process was modified to better manage multiple lock requests.

      NOTE:
      The message "Update task will be re-tried in 3 minutes because update is still in progress" is
      still written in the Agent.log, but it does not appear repeatedly.

      11. ISSUE:
      The script engine inconsistently managed a set of buffers, causing an application error when
      one buffer contained more data than another could hold.

      RESOLUTION:
      The script engine now uses a consistent size for sizing its buffers.

      12. ISSUE:
      The Common Management Agent incorrectly installed managed products to Windows Vista
      systems.

      RESOLUTION:
      The Common Management Agent now correctly adheres to the supported platform IDs identified
      in the Package Catalog list (PkgCatalog.xml) for all supported operating systems.

      13. ISSUE:
      The Common Management Agent corrupted the server.xml and/or compiled.xml files when it
      compiled policies.

      RESOLUTION:
      The Common Management Agent now locks the server.xml and compiled.xml files as a single
      unit. This greatly decreases the likelihood of the policy compilation process corrupting these
      files.

      14. ISSUE:
      Processing of the ExtraDAT update occurred between the Engine and DAT updates, causing the
      ExtraDAT update to fail.

      RESOLUTION:
      Now the Engine and DAT updates occur first (in that order) and they are followed by any
      additional updates.

      15. ISSUE:
      If the Engine Component Package was checked in to any branch other than the Current branch, the
      Engine Component update failed.

      RESOLUTION:
      A branch selection configuration was added to the "ePO Agent Policy" tab, allowing the Engine
      Component Package to be checked in to a branch other than the Current branch.
        • 1. RE: CMA 3.6 Patch 3 Release Notes
          tonyb99
          Made sticky
          • 2. RE: CMA 3.6 Patch 3 Release Notes
            tonyb99
            Nice that they seem to have finally aknowledged this issue, but you'll still be stuffed most of the time happy :

            4. ISSUE:
            If specific files were not in use when a ForceInstall of the Common Management Agent was
            attempted, those files were marked for deletion on reboot and the installer stopped and
            requested a reboot. After the system was rebooted, the files were deleted but the
            installer did not resume. This effectively removed the Common Management Agent from the
            system.

            RESOLUTION:
            The installer now resumes installation once the system is rebooted.

            NOTE:
            When a system is restarted after a ForceInstall, the user account used to log on to that system
            must have administrator credentials. If the user account does not have administrator credentials,
            the installation does not resume.
            • 3. RE: CMA 3.6 Patch 3 Release Notes
              Could someone please let me know where to download patch 3 for the CMA 3.6.0
              It doesn't seem to appear under Security Updates for me.
              • 4. RE: CMA 3.6 Patch 3 Release Notes
                twenden


                This patch is not released for general download yet. When it is released, you will then find it under the following area:

                http://www.mcafee.com/us/medium/support/index.html

                1. Click on the link above and then under "Technical Support ServicePortal" click on "Service Portal".
                2. You will then be prompted for your email address and password. This is tied to your corporate support grant number.

                Note: These patches are only made available to people with valid grant numbers.