/build/static/layout/Breadcrumb_cap_w.png

SMS 2003 clients get adv 2nd time for ITMU immediately after successful application 1st time complet

Scenario:

mandatory assignment of ITMU patch job - advertisement "SMS12345"
machine runs it successfully
machine rebooted by package - or not. Sometimes no reboot is configured.
mandatory assignment of ITMU patch job - same advertisement "SMS12345" AGAIN immediately after installation success
instance of SoftDistProgramHasRunBeforeWithoutFailing

This has happened on up to 80% of all ITMU deployments, and I assure you, nobody is fiddling with the assignment times. Sometimes it doesn't happen on an ITMU job, but usually it does.

The issue occurs sometimes even if the machines are not rebooted.

Why is this happening? It gets it pushed precisely twice, and always immediately after the first one. Anybody know?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: williamp 12 years ago
Orange Belt
0
OK, so I'll reply to myself, just in case anyone ever reads this board.

The reason this is happening, is that the ITMU program in this instance, is configured to run a verification scan immediately after the job is complete. (Doing this is required to ensure that the results as entered into the data base are "verified" as soon as possible as opposed to "unverified").

SMS cannot actually run this verification unles the advertisement mandatory assignment schedule is set to recur. It is irrelevant what the recurring period is (I use 12 months on an advertisement that expires within 30 days)

The recurrance allows SMS to re-run the program on machines where it has been successful, and configuring it this way yields proper results.


ORIGINAL: williamp

Scenario:

mandatory assignment of ITMU patch job - advertisement "SMS12345"
machine runs it successfully
machine rebooted by package - or not. Sometimes no reboot is configured.
mandatory assignment of ITMU patch job - same advertisement "SMS12345" AGAIN immediately after installation success
instance of SoftDistProgramHasRunBeforeWithoutFailing

This has happened on up to 80% of all ITMU deployments, and I assure you, nobody is fiddling with the assignment times. Sometimes it doesn't happen on an ITMU job, but usually it does.

The issue occurs sometimes even if the machines are not rebooted.

Why is this happening? It gets it pushed precisely twice, and always immediately after the first one. Anybody know?


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ