I have several task sequences that I deploy to lab computers that we re-image 1 or 2 times a year. The task sequences run and install specific software for that lab after the base image deploys.
The base image is deployed using WDS without SCCM in the mix. It is a setup they we are using because of legacy business processes that just make this easier. Then after the machine boots up and gets its SCCM policies the task sequences start running to deploy the software.
The issue I am noticing is that I have no control over what runs first and sometimes Windows Updates that are deployed via SCCM run before or in between the task sequences that I have running. Some installs fail because of the pending Windows Update reboot, which I believe I have gotten around just by checking for it and rebooting before it installs the software. The issue is that the Windows update could and usually is one of those lovely updates that requires multiple reboots. The second reboot is killing my task sequence.
The issue is I need to somehow force this updates to run after my task sequences or make sure they run first. The only way I can think of this is by having priorities for the task sequences. I can't just add installing the updates to the task sequence, because the second reboot will kill my whole task sequence there too.
Anyone have any ideas on how to get around this issue? I want the machines to install the Windows updates so I can't just remove them from the collection.