1 2 Previous Next 12 Replies Latest reply on Nov 9, 2007 9:11 AM by twenden

    CMA 3.6 patch 2 Released To Web

    tonyb99
      CMA 3.6 patch 2 Released To Web
      This is available to download from the service portal downloads section

      main zip
      standalone version
      readme.txt

      (although it is referenced in the readme at this time (9.15 GMT 051107) there is no NAP package on the site)

      NEW resolved issues in this release:

      RESOLVED ISSUES
      1. ISSUE:
      When installed in ProtectionPilot and ePolicy
      Orchestrator 3.5.0 environments, 7023 and 7034
      events were recorded in the system event log and
      the application’s main service was restarted.
      RESOLUTION:
      The Common Management Agent was modified to
      compress and encrypt events before uploading
      them to the ePO server.
      2. ISSUE:
      When installed in 64-bit environments, 7022
      events were being recorded in the system event
      log and the Common Management Agent was slow to
      start.
      RESOLUTION:
      The Common Management Agent was modified to
      remove the delay in startup, which keeps the
      7022 events from being recorded in the system
      event log.
      3. ISSUE:
      Select Common Management Agent files could be
      locked by McAfee managed products, preventing
      the Common Management Agent from being upgraded
      to a newer version and preventing a HotFix from
      being installed.
      RESOLUTION:
      The Common Management Agent was modified,
      renaming the following files:
      Existing Name New Name
      naCmnLib71.dll naCmnLib2_71.dll
      nailog.dll nailog2.dll
      naxlm71.dll naxml2_71.dll
      naisign.dll naisign2.dll
      nailog64.dll nailog2_64.dll
      naxml64.dll naxml2_64.dll
      naCmnLib64.dll naCmnLib2_64.dll
      Additionally, file dependencies were removed to
      prevent the renamed files from being locked by
      McAfee managed products. The files under the
      previous names are deleted immediately when not
      locked. When locked they remain until the next
      Common Management Agent installation.
      NOTE:
      When performing a Force Install to a new folder,
      locked files in the original folder are not
      deleted, nor marked for deletion on reboot.
      Files in this state remain in the original
      folder.
      When performing a downgrade after installing
      Patch 2, if any of the renamed files are locked
      the downgrade fails and leaves the machine
      without a functioning Common Management Agent.
      To avoid this problem, a client reboot should be
      performed before performing a downgrade.


      Enjoy
        1 2 Previous Next