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

A custom compliance rule is added to a Software Managed Delivery (MD) Policy which will always fail on Windows client computers as seen here:


Manually starting the MD Policy and as a result it is "Compliant" after completing the remediation action, although the status is "Not Detected" as seen below:

 

This is how it looks in 8.6 RU3:

Environment

ITMS 8.7

Cause

Known Issue

Resolution

A fix has been added to ITMS 8.7 RU1.

A point fix is available for those with ITMS 8.7 RTM release and is found in KB 261271 CUMULATIVE POST ITMS 8.7 RTM POINT FIXES.

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

Note: After the 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, the Managed Delivery policy compliance check will be executed and sent the correct status to SMP Server.