User unable to run Managed Delivery Policies when "User can run when maintenance window is inactive" is not selected

Products

• IT Management Suite
• Software Management Solution

Issue/Introduction

Managed Delivery policy remediation doesn't run at maintenance window opening if its compliance check was run outside of maintenance window.

Steps to reproduce:

1. Create Managed Delivery Policy (MDP) with specific compliance schedule to run at exact time (before maintenance window (MW))
2. Set remediation to run At next maintenance window
3. Configure Maintenance window to happen in some time in future

At compliance time MDP runs pre-download detection check and reschedules execution to next maintenance window.

"nextJobIndex" changes to 9 and user no longer able to trigger policy execution.

Environment

ITMS 8.7.3

Cause

Known issue. We needed to restore the functionality that was in ITMS 8.7.2 and 8.7.3 GA (no Pointfixes) .

Meaning that if policy has started up, but the current policy task is in "Not started" state ("no download/execution/rule check /client task" at the moment), then external trigger of the policy (user or COM API) may RE-RUN the policy from the beginning.

If there is some "running" task like above, then user WILL NOT be able to kick-off the policy as there is no sense to interrupt something that is already running. 

Resolution

This issue has been fixed with our ITMS 8.8 Release.

Now MD policy remediation executes after compliance check step when:

• Maintenance window policy becomes active
• Maintenance window policy is already active during MD policy compliance check
  Verified that requested MD policy from SW Portal immediately performs remediation after compliance check if MW policy active or not yet active on client computer.

 

For those with ITMS 8.7.3 release, refer to the pointfix available at: CUMULATIVE POST ITMS 8.7.3 POINT FIXES: