MDT2013 making an offline USB flash drive to support UEFI

In the enterprise environment for system deployment usually set up the MDT environment for network push, but in some of the need to make an offline USB flash drive for the deployment of the system installation, then we build the MDT environment will often be done before the template machine is packaged and captured system image to generate a WIM file. Wim files tend to be large, at least more than 4G, and is a single file, then in the production of offline USB flash drive, you must use the NTFS-formatted file system to match. But another awkward place, if you want to push the system down by UEFI, you need a USB drive file system format of FAT32.

Early encounter this problem when the idea of the WIM file is split, but the use of tools to split the file suffix has changed to SWM, think can go directly offline USB drive folder (Content\deploy\control\2\unattend.xml) To change the XML to implement, but the discovery will error.

650) this.width=650; "title=" clipboard "style=" Border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clipboard "Src=" Http://s3.51cto.com/wyfs02/M00/8C/6D/wKiom1hsXsLB2P41AACHZtocSy0755.png "height=" 415 "/>

Later read Abroad blog has found that MDT support SWM files, that is, MDT can do their own WIM file splitting.

Let's go straight to the dry goods and share with you how to operate.

Open the Deploymentshare directory of the MDT server and locate the settings under the control folder.

<SkipWimSplit>False</SkipWimSplit> This option and change it to False to save.

650) this.width=650; "title=" clipboard[1] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clipboard [1] "src=" Http://s3.51cto.com/wyfs02/M01/8C/6D/wKiom1hsXtPzG16DAACROJx_TmY572.png "height=" 518 "/>

After the save is complete, there is no effect on the MDT server deploying the system over the network, only one more step of the WIM file split when generating the offline USB drive

650) this.width=650; "title=" clipboard[2] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clipboard [2] "src=" http://s3.51cto.com/wyfs02/M01/8C/6D/wKiom1hsXtTSsSwCAABXLTg-58U335.png "height=" 573 "/>

At the time of the split we can look at the System Image folder under the Deploymentshare directory and find that the system is being split and a new SWM file is generated.

650) this.width=650; "title=" clipboard[3] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clipboard [3] "src=" http://s3.51cto.com/wyfs02/M01/8C/6A/wKioL1hsXtijtobMAABJPOvmoxQ271.png "height=" 232 "/>

In fact, MDT by calling ImageX to split the WIM file, after splitting up the SWM file to the offline USB drive output folder, and the offline USB drive after the completion of the Deploymentshare folder file will be restored to the WIM format. Isn't that fun?

This article is from the "Dream Eisenia foetida Heart" blog, please be sure to keep this source http://zmczx.blog.51cto.com/7689019/1888805

MDT2013 making an offline USB flash drive to support UEFI