SCCM Software Update Compliance reporting not accurate.

  • SCCM Software Update Compliance reporting not accurate.

    Posted by Roddy Gelberty on 21 July 2020 at 11:51 am

    There often is a difference between what the native SCCM Console shows for report values and what is shown in a report for the same deployment, making it difficult to know which is accurate. Is there a right or wrong way of creating SCCM software update compliance reports.

    Roddy Gelberty replied 3 years, 11 months ago 3 Members · 3 Replies
  • 3 Replies
  • Roddy Gelberty

    21 July 2020 at 12:01 pm

    Hey Jessica, We use baseline based compliance reporting internally at osd365. We run 12 baselines dedicated to each month per year. The baseline is based on pre-approved updates.
    The baseline will include both Windows 10 and Office365 updates. Reporting compliance this way is more accurate because the result is Binary (1 or 0) 1 – Compliance and 0 – Non_Compliant.
    I’ll need approval to make the report publicly available. So watch this space.

  • Roddy Gelberty

    31 July 2020 at 9:33 am

    Hey Luna, When do you think you’ll post the SCCM compliance report that you spoke about in your previous comment. We are struggling to get our compliance percentages up. It would be nice to identify the gaps.

    • Roddy Gelberty

      31 July 2020 at 10:54 am

      Its a work in progress. It has to get cleared by security before it gets published online. Covid19 has introduced a delay in all our processes. What reports do you folks use within you organization at the moment? I’ve got a teaser for you. 🙂

Log in to reply.

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.