Client Management Suite

Hi all,

I am experiencing a strange issue regarding managed delivery policies. ITMS 7.1 SP2.

When scheduling a managed software delivery policy on a client, I can trigger it to execute on the client (agent GUI) and it will execute fine and install the software. Once this has occured, I cannot trigger it again. The link (below application tasks) is visible, but when clicking it, it does not start running the detection check for the managed delivery policy.

The same behaviour occurs with a schedule. The first time the client receives the policy, it will execute on its schedule fine and installs the software (or displays 'detected'). When the next compliance check is supposed to run (re-occuring schedule) it does not start. After this second time has passed, the managed delivery displays 'not scheduled' in the 'Next Run' column on the client and never executes again, although the policy is configured with a re-occuring schedule (window, every two hours). In the logs, the policy states 'policy x has no valid future scheduled run time'.

If I reboot the machine, I can trigger the policy once again just fine, but only once. The same with the schedule.

Does anyone has ever came across this issue?

I already tried:

Recreating the policies, with/without schedules, different software to deliver, reinstalling the agent, checked the policy XML's which seem fine (schedules present), ...

Many thanks for any clues on this one.

kr, dawi_x 

Hi Dawi_x,

Do you have any updates/hotfixes/rollups installed on the  ITMS 7.1 SP2?

Regards,

Dmitri

Hi Dimitri,

Yes, we have installed the v3 rollup fix to address AD Import issues.

regards,

dawi_x

Hi Dmitri,

Yes I did. Agent rollout is performed after rollup installation. Agent versions are 7.1.15310.8310.

Hi dawi_x,

May I ask you to share your Managed delivery policy schedule settings? 

I can't reproduce your problem(no triggering of the second run for Compliance check) but I see next: If I set next settings,  I get  'not scheduled' status in the 'Next Run' column for policy in Agent UI:

Schedule Window for Compliance with "no repeat" option(if you want to repeat the compliance check "no repeat" setting should be changed), with "During window, check for every 2 hours" setting and schedule Remediation for time less than current time.

or If I set End date in Advances schedule settings which is equal or less than current date.

Also I see that change of the Last status for Detection check is changed very fast. I Can see that it was changed only by Last Run date or in the task history (which can be opened from "Task Status" tab in agent UI)

Regards,

Dmitri

Hi Dmitri,

I already tried a lot of different settings. Momentarily I have a scheduled window with re-occurence set at 2 hours which repeats daily. The start date is set in the past and the end date is not set. Remediation is set to 'immediately'.

It are all rather default and common settings. I have been implementing these at a lot of customers and I cannot reproduce this neither in my demo or test environments with the same SP and rollup fixes installed, neither can I reproduce this issue at other customers.

If I look at the policy xml's received by the agents, these are all fine, It seems it is just a mather of the client itself not handling it right. I also tested this at different clients at the specific customer.

The strange thing is that this only occurs with managed delivery policies. For instance the 'windows assessment scan' policy for patch management executes fine on its schedule and can be triggered manually..

I think this one will have to be escalated to support or maybe I am missing something crucial here?

kr, dawi_x

Hi dawi_x,

Yes, if the issue is not reproducible - escalation to support is the most correct solution.

Regards,

Dmitri 

Support has told me "never use the schedule window" as the results are unpredictable. 

What happens when you change the window to specific times?

Hi Hightower,

This results in the same errorous behaviour.

kr,

dawi_x

Do you have a screenshot of the task?

The most common cause is checking "Run Once ASAP."  If it has ever run before, that is "Once," so it will never run again.

Hi Mclemson,

I cannot provode a screenshot of the policy because I am not at this customer until a few weeks, but since it is a managed software delivery in 7.1 SP, the option 'run once asap' is not available.

I also already tried different schedule types.

The policy seems to re-occur, but when the next timeslot is there to execute, it just does nothing and the scheduled time on the agent changes to 'not scheduled'. After a reboot the same scenario occurs again: one execute and then never again.

Also, the link to trigger the policy on the agent is available, but when clicked does nothing.

I also reviewed the policy xml's and the schedules defined in there are ok.

It seems its a matter of the agent not able to handle or correctly execute these policy schedules..

kr, dawi_x

I'd have to see logs to offer a guess.  Do you have any logs from a problem computer?

Sorry to chime in here.  Not sure if you have resolved your issue or not.  If you are still having issues have you checked on your Schedule the "No Repeat" option under the Schedule window?  Mine was set to not repeat so it would not work the next day.  After changing it my managed deliveries began to work correctly

Hi All,

kinda lost this one out of my sight.

After rollup v4 implementation, a few other hotfixes and so an upgrade of the client agents, everything started working as expected. no settings were changed.

I still have to guess what went wrong here..

Tnx for the responses,

kr, dawi_x