Software Managed Deliver (MD) Policy shown as compliant after remediation, even if compliance rule will always return 'not detected'
search cancel

Software Managed Deliver (MD) Policy shown as compliant after remediation, even if compliance rule will always return 'not detected'

book

Article ID: 261986

calendar_today

Updated On:

Products

IT Management Suite Software Management Solution

Issue/Introduction

For example, a custom compliance rule is added to a MD Policy which will always fail on Windows client computers:

Manually starting MD Policy and as a result, MD (Software Managed Delivery) is compliant after completing remediation action, although the status is "Not Detected"

 

This is how it works (in 8.6 RU3)

Environment

ITMS 8.7

Cause

Known Issue

Resolution

This issue has been reported to the Broadcom Development team. A fix has been added to our next release: ITMS 8.7 RU1.

A point fix is available for those with ITMS 8.7 RTM release. See KB 261271 to obtain the point fix.

After installing the point fix, now Compliance or Applicability checks show the correct statutes.

Note:
After this point fix installation, on the next policy refresh, all previously enabled and executed MD Policies status will be reset to "Unknown not started"

Therefore, on the next schedule, Managed Delivery policy compliance check will be executed and sent the correct status to SMP Server.