MDT2010新功能（7）――对引导镜像创建进行优化

原帖地址：http://blogs.technet.com/mniehaus/archive/2009/06/27/mdt-2010-new-feature-7-boot-image-creation-optimized.aspx

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”.  This action’s purpose is to generate the Windows PE boot images and ISOs needed to perform a deployment.  It will figure out what actions need to be performed to get the images updated and will only perform those actions.  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.

在MDT2008里，制作引导镜像有两个命令：Update和Update（files only）。在MDT2010里，就只剩下一个“Update Deployment Share”。这个命令用于建立PE的引导镜像ISO。程序会根据需要进行判断所需要进行的实际操作。例如你第一次执行此操作时，会花些时间生成相关PE镜像，而立即再执行一次时，则会马上完成结束。

We also modified the configuration for these boot images.  There are now separate settings for x86 and x64 boot images.  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 nVidia drivers that you want to inject into Windows Vista), etc.

我们也修改了引导镜像的相关配置。对于X86和X64则进行分别设置。你可以指定ISO文件名、镜像的说明（这在将wim文件导入WDS时很有用），RAMdisk的scratch空间大小（这在导入例如Nvidia驱动这种很大的程序时十分有用）





When you perform the “Update Deployment Share” process, Deployment Workbench will compare the current boot image configuration against the previous configuration.  If there are only minor changes, it will copy the WIM locally, make the necessary updates (e.g. injecting new drivers, updating the Bootstrap.ini, adding new components), save the updated WIM, and (optionally) generate a new ISO file.  If there are major changes, the boot image will be recreated from scratch.  You can force a full update in the “Update Deployment Share” wizard by selecting “Completely regenerate the boot images”:
当你执行“Update Deployment Share”，工作台会将现有的引导镜像配置与原有配置进行对比。如果仅仅只有小改变的话，那么仅会拷贝wim，做出必要的升级。例如添加驱动、修改bootstraop，然后保存并更新wim，有必要时会重新生成iso。如果有大的改变，则引导镜像将完全重新生成。你可以选择“Completely regenerate the boot images”来强制重新从头生成。

Because adding and removing drivers, components, patches, etc. can slowly cause the size of the Windows PE boot WIMs to increase, you can also choose to compress the boot image, which will export the WIM contents to a new WIM to get the size back to the smallest possible.

由于添加驱动、组件、补丁等会增加引导镜像的大小，你还可以选择使用压缩来导出一个新的wim，获得尽可能小的wim文件。

With MDT 2008, Deployment Workbench would always use the “winpe.wim” files from the Windows Automated Installation Kit as the source for all boot images that it would generate.  With MDT 2010, Deployment Workbench will look for a “boot.wim” file from one of the imported operating systems that has the same build number as Windows AIK (e.g. “boot.wim” from a Windows 7 RC, build 7100, operating system to go with the Windows AIK for Windows 7 RC).  If it finds a match, it will use that WIM instead.  Why do we do this?  Because the “boot.wim” contains the Windows Recovery Environment (Windows RE), a component that isn’t available in Windows AIK.

在MDT2008里，程序总是选择使用WAIK里的winpe.wim来制作引导镜像。2010中，程序会寻找被导入到工作台的操作系统的boot.wim，如果版本和WAIK相同，就会使用这个PE作为替代。为什么要这么做？因为Boot.wim里含有WAIK所没有的Windows RE。

Another enhancement in this process:  you can now abort the “Update Deployment Share” process at any point, so if you decide you would rather do the update later you can.  It might take a while for the process to clean up after itself (e.g. unmount any mounted WIMs) so the machine is left in a good state, so be patient.

其他加强的地方包括：在“Update Deployment Share”时可以任意中止，不过有时中止过程需要一定的时间，这需要耐心