I recently had an issue where I was testing the creation of prestaged media using SCCM 2012 SP1, and after the WIM had deployed and I restarted the computer – the targeted computer would not boot into Windows PE. Instead, it would boot into the operating system image I had deployed. For me this was pretty useless as the WIM image I had deployed would start its OOBE setup process, and not pick up the task sequence I had targeted to it.
If you’re familiar with prestaged media in SCCM 2007, the new options and features in SCCM 2012 SP1 may catch you out. I won’t go into how to create pre-staged media or a task sequence in this post; so I’m going to assume you’ve already done all the steps to deploy your prestaged WIM. If you’ve found this post because you are trying to create pre-staged media for your OS deployment, here are some links you might find useful.
Anyway, back to my problem. It turns out my issue was a fairly simple mistake, and one that’s easy to make if you’re not totally familiar with SCCM 2012 Task Sequences and Prestaged Media. Typically, the SCCM task sequence to deploy your prestaged WIM would look something like this
1. Format Disk
2. Deploy WIM Image
What caught me out, was for Step 2, I had the task “Apply Operating System Image”, when it should have been “Apply Data Image”.
This is what your task sequence should look like for it to work properly…
The “Apply Data Image” step is found here…
Use that to deploy your WIM, and when you reboot, it will load into Windows PE – and then you can continue your advertised task sequence.