How would one run a task sequence within a task sequence in SCCM 2012 SP1

Solution 1:

I realize this does not directly answer your question but I can't help but feel this might be a better way to accomplish your goal.

I'm assuming you are using this Task Sequence to either do a image build or capture or to deploy a previously capture image. I cannot think of a reason why you would have to install device drivers this way.

We just import the device drivers into the Drivers Catalog, roll them up in Packages and then use the Apply Device Drivers action during the image to handle each particular workstation.

Works just fine for us but maybe there is something in your scenario that I am missing.

Solution 2:

People call me crazy, but I do not create driver packages for different computer models. I only have one driver package that has every driver in it, and I obtain the driver from the device manufacturer's site (where available), and not from the computer maker.

Take Ethernet drivers as an example. We are (mostly) a Dell shop but we do have some Acers and Lenovos scattered here and there. But all of them use either an Intel, Broadcom, or Realtek chipset. Intel's ProSet driver covers every model they make. Broadcom and Realtek have two each. That's 5 ethernet drivers that cover all 4500 computers on our campus. I include that one driver package in my task sequences, and Windows does a good job of selecting the correct driver during deployment. The best part is that when a new model arrives, I rarely have to change anything. I only touch the driver repository maybe once or twice a year, and I haven't even touched my task sequences in over two years.

Video drivers are the same way. I have one ATI/AMD driver, one nVidia driver, and three Intel drivers that cover every computer we have. It does get a little dicey sometimes with audio drivers, and odd little chipset drivers every now and then. But usually, the Dell one works on Acers or vice versa.