With the release of ConfigMgr 1610 came the ability to transition from MBR (legacy) to UEFI in a single task sequence. This is an awesome feature and it is outlined nicely here. And, it works great. 🙂
Let’s dig into each of these steps:
Significantly reduce the time needed to create usable boot media and remove one of the bigger barriers to updating the ADK you are using. Adding the network and storage drivers you need to newly created boot media.
With the new “Current Branch” model of ConfigMgr and Windows 10 we can expect a faster release cycle of the ADK, which means new boot images pretty regularly! Creating new boot media is really simple. However, reimporting all of your required drivers into that boot image can be a real chore. Here is a script that that identifies the drivers in a source boot image and imports them into a destination image. Give it a spin and give me some feedback.
The script can be found here
Deploying an updated Office installation has always been an annoyance of mine. It is ideal to be able to deploy a fully updated Office installation so you don’t have to run a software update scan and then wait for all the office patches to download and install. Having to install less software updates can reduce your deployment or build and capture times significantly.