0 Replies Latest reply on Jan 9, 2008 5:12 AM by xfavorettx

    Patch Release: McAfee System Compliance Profiler (SCP) 1.1 Patch 2 is Now Available!

      > Hello,
      >
      > McAfee System Compliance Profiler (SCP) 1.1 Patch 2 is now available for download
      to licensed customers from McAfee ServicePortal:
      > https://mysupport.mcafee.com/eservice_enu/default.htm
      >
      > __________________________________________________________
      > ABOUT THIS RELEASE
      >
      >
      > PURPOSE
      >
      > This Patch replaces files in System Compliance
      > Profiler to resolve the issues listed below.
      >
      > RESOLVED ISSUES
      >
      > 1. ISSUE:
      > The System Compliance Profiler Plugin reported
      > the version property as "version" when it should
      > report it as "Product Version."
      >
      > RESOLUTION:
      > The System Compliance Profiler Plugin now
      > reports its version property as "Product
      > Version" once the first full property collection
      > has been completed.
      >
      > 2. ISSUE:
      > When the System Compliance Profiler Scan Engine
      > encountered a registry key without a value, it
      > incorrectly reported the node as compliant.
      >
      > RESOLUTION:
      > The System Compliance Profiler Scan Engine has
      > been changed to correctly report a "Registry
      > value does not exist" constraint.
      >
      > 3. ISSUE:
      > The "Non-Compliance Summary By Rule Group"
      > report incorrectly displayed the header
      > "Non-Compliance By Computer Name."
      >
      > RESOLUTION:
      > The "Non-Compliance Summary By Rule Group"
      > report has been changed to display the correct
      > header.
      >
      > 4. ISSUE:
      > When the Group and/or Rule names were changed on
      > a policy, the original names continued to be
      > displayed on ePO reports along with the new
      > names.
      >
      > RESOLUTION:
      > Now when Group and Rule names are changed, only
      > the new names are displayed in the ePO reports.
      >
      > 5. ISSUE:
      > When viewing System Compliance Profiler reports
      > localized for Japanese, unrecognizable
      > characters were displayed in place of the
      > localized content.
      >
      > RESOLUTION:
      > The System Compliance Profiler reports now
      > correctly display localized Japanese content.
      >
      > 6. ISSUE:
      > An error message was displayed when attempting
      > to view the System Compliance and Non-Compliance
      > Summary report.
      >
      > RESOLUTION:
      > The System Compliance and Non-Compliance Summary
      > report now displays correctly.
      >
      > 7. ISSUE:
      > The System Compliance and Non-Compliance Summary
      > report did not apply directory filter requests.
      >
      > RESOLUTION:
      > The System Compliance and Non-Compliance Summary
      > report now includes directory filter requests.
      >
      > 8. ISSUE:
      > The System Compliance Profiler property Template
      > File Date incorrectly displayed the date System
      > Compliance Profiler was installed on the node,
      > rather than the current template file date.
      >
      > RESOLUTION:
      > The System Compliance Profiler property Template
      > File Date now reports the correct date.
      >
      > 9. ISSUE:
      > The phrase "service doesn't exist" was
      > incorrectly translated in German on the System
      > Compliance Profiler Rule Configuration dialog
      > box.
      >
      > RESOLUTION:
      > The System Compliance Profiler Rule
      > Configuration dialog now correctly displays the
      > German translation for "service doesn't exist."
      >
      > 10. ISSUE:
      > When ePolicy Orchestrator user level database
      > permissions were used, System Compliance
      > Profiler report requests resulted in an error
      > message.
      >
      > RESOLUTION:
      > System Compliance Profiler reports now display
      > correctly when ePolicy Orchestrator user level
      > database permissions are used.
      >
      > 11. ISSUE:
      > During the unload process the System Compliance
      > Profiler Plugin did not release all of its
      > associated resources resulting in the error
      > "Failed to run or get the task status, because
      > of Product Manager unavailable."
      >
      > RESOLUTION:
      > The System Compliance Profiler Plugin unload
      > process now releases all of its associated>
      > resources.
      >
      >
      > Please review the most up to date Readme for McAfee System Compliance Profiler
      (SCP) 1.1 Patch 2 via the McAfee KnowledgeBase for additional, important
      information.
      >
      > McAfee KB 613643 - Release notes for System Compliance Profiler 1.1 patch 2:
      > https://knowledge.mcafee.com/SupportSite/search.do?cmd=displayKC&docType=kc&exte rnalId=613643
      >
      >
      Regards,