If a task sequence runs an Install Package step during OSD, once it is complete and in Configmgr will it run that same again (using software distribution/application) program if it is deployed to a collection which the client belongs to? Or does it maintain a "memory" of the fact that it already ran that program in a task sequence?

It depends on the "re-run" settings and the schedule(s) of the deployment. Execution history will be kept, so the client is aware that it already ran during the TS.

If you are using an application and you have configure the discovery method properly. SCCM will know that the client is install and not run it. You will see that the software is already present. in the monitoring section.

• Edited by Frederick Dicaire 18 hours 43 minutes ago

Thanks Torsten. So if I have it set to "Rerun only if failed" and it succeeded during the TS it won't rerun after the task sequence as a standalone package/program? So it's no different whether it originally ran in a task sequence or as a standalone software distribution in terms of rerun behavior? Most of the schedules have deadlines in the past.

If you are using an application and you have configure the discovery method properly. SCCM will know that the client is install and not run it. You will see that the software is already present. in the monitoring section.

• Edited by Frederick Dicaire Thursday, August 27, 2015 1:07 PM
• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator 23 hours 48 minutes ago

Hi,

>>So if I have it set to "Rerun only if failed" and it succeeded during the TS it won't rerun after the task sequence as a standalone package/program?

Yes.

>>So it's no different whether it originally ran in a task sequence or as a standalone software distribution in terms of rerun behavior?

Yes.