In SCCM 2007 if you advertise multiple OSD task sequences to a collection, we can select the required task sequences in Win PE boot mode. This helps us to select required windows version when installing (Ex -Windows 7 32bit or 64bit).
But in SCCM 2012 R2 this is rather different. We have to do few changes and these changes are really make some sense. Good thinking by Microsoft.
- Create the Task Sequence
This can be built in task sequence or custom task sequence.
- Deploy the Task Sequence, when deploying select available in purpose.
- When client start the network boot, you are required to press F12. If F12 is not pressed Client computer will go to the next boot device and boot. This make sense because this Task sequence is deployed as available not required. so when windows PE boots, the multiple task sequences will be desplyed and you can select the required task sequence.
These new changes are really valuable, using these we can deploy the OS upgrade or OS deployments to every computer, and because the F12 press requirement to deploy the task sequence, normal Client boot up will not be interrupted. Also we can deploy multiple task sequences to different Operating system versions.
These are small things but might give high impact on automation.
Hope this post is helpful.