Can I set a priority in SCCM 2012 for advertisements or any other ideas to fix my Task sequences?

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.
Who is Participating?
Mike TLeading EngineerCommented:

Creating a full OSD is a better plan long term. You will then have full control over everything in the OS. Note to get updates to work inside a the OSD you may well need several "Update" steps. We had to add two, one after the other but you could place them anywhere in the full OS stage that does not upset your apps installs.

I mis-read the bit about 2nd reboots. I can see why that would fail. An alternative solution is do offline patching, at least to get the bulk of the updates injected into the OS and then re-import the new OS into SCCM.

Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Disable software updates from TS and try.

Are you using symantec by any chance?
Mike TLeading EngineerCommented:

It's not clear whether you are using Software Updates Point (SUP) or just WSUS. If using SUP then you can use maintenance windows for the updates and set the TS deployment to ignore maintenance windows.

The other option is to add the updates into TS. This will handle reboots fine. I use it all the time. The TS will resume exactly where it left off after the reboot.

gacusAuthor Commented:
There are no updates to disable in the TS.  They are deployed using SUP and get in the way of the TS.

@Mike.  The updates that require multiple reboots do not work with a TS.  It is a known issue.

I am just creating a TS for the entire deployment including the imaging so the updates will be forced to run after the imaging process.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.