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?
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)
Please log in to answer
Posted by:
williamp
16 years ago
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.
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.