I have "inherited" an SCCM-envirronment where all packages are advertised with the unscheduled "as soon as possible".

This doenst work well when updating virtual apps and trying to re-run the advertisements (of course it doesnt work with msi-packages either). Change the mandatory assignement to a schedule and it works. Fine.

But what I cant figure out is the difference between the "run as soon as possible" and the schedule with no recurrence.
To me it seems pretty much the same except you get the option to re-run the advertisement with a scheduled mandatory assignement. From what I have seen (and it isnt much really [;)] ) the packages with a schedule seems to run "as soon as possible" after the date and time set by the schedule. And if you set it to no recurrence, well what's the point of the unscheduled "run as soon as possible"?
0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity