Optimize the boot image updating process completely regenerate the boot

19 Mar

To learn more about customizing Windows PE, see the Windows Preinstallation Environment User's Guide for Windows 7 in the Windows AIK.

Updating a deployment share causes Deployment Workbench to update its configuration files, source files, and Windows PE images.

With MDT 2008, there were two actions in Deployment Workbench: “Update” and “Update (files only)”.

With MDT 2010, there is now only one called “Update Deployment Share”.

The Windows AIK 2.0 comes with Windows PE 3.0, so no additional files are necessary to create Windows PE boot images for MDT 2010.

When you update your deployment share in the Deployment Workbench, MDT 2010 automatically generates the following custom Windows PE images (here platform is x86 or x64): You don't need to manually customize Windows PE to add network interface card (NIC) device drivers to it.

You can also specify ISO file names, image descriptions (useful if you are importing the Lite Touch WIMs into WDS), RAMdisk scratch space size (useful for those pesky huge n Vidia drivers that you want to inject into Windows Vista), etc.This article walks you through the recommended process to deploy Windows 10 to Surface devices with Microsoft deployment technologies.The process described in this article yields a complete Windows 10 environment including updated firmware and drivers for your Surface device along with applications like Microsoft Office 365 and the Surface app.So generally the first time you run “Update Deployment Share” it will take a while to generate the boot image; the next time it will see that nothing needs to be done and quickly finish.We also modified the configuration for these boot images.