Splitting WIM images in MDT

Splitting images into 4GB chunks is quite useful if doing UEFI-based offline media deployments.

Note: There are hacks around the 4 GB limits, by using a third party NTFS EFI drivers (but that's not supported by Microsoft). Anyway, see the post below:

UEFI and NTFS – Friends to MDT 2013 at last
https://deploymentresearch.com/471/UEFI-and-NTFS-Friends-to-MDT-2013-at-last

Split image (WIM) support in MDT

In MDT 2013 Update 2 (and Update 1), the split image support is off by default. You enable it by doing the following:

1. In your deployment share, in the file system, navigate to the Control folder.

2. In the Settings.xml file, enable split image support by changing the SkipWimSplit value to False. Like this:

False

What if it doesn't work anyway?

Something I learned, the hard way I might add, is that the above setting may not work. It also requires that the Name (not filename) of your imported operating system actually contains the word .WIM (or .wim).

Note: This is a confirmed bug in MDT 2013. Fixed in the latest release.

image
The imported image with a ".wim" in the name.

image
The images in the offline media after splitting, now having the SWM extension.

About the author

Johan Arwidmark

5 1 vote
Article Rating
Subscribe
Notify of
guest
12 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
John Andre Schreuder
John Andre Schreuder
6 months ago

gracias =)

REDFOX
REDFOX
6 months ago

Johan,

I just had the same issue with WDT not splitting the files because I renamed the OS and removed .wim.

Thanks for you post, and for leaving it up.

Shemek
Shemek
6 months ago

One thing, though. It works for me regarding the image, but litetouchPE boot image remains bigger then 4GB, so I'm still unable to use FAT32 formatted USB media.

Shemek
Shemek
6 months ago

It's actually HP's new policy. Their touchpad laptops are now classified as system-class so had to add them to PE.

Shemek
Shemek
6 months ago

Hmm, your comment made me thinking and I figured out, it wasn't the system-class drivers making it so big. I messed up the selection profiles… After fixing, it's ~3.3GB now. Additionally, I discovered a problem with USB media not booting because of 'insufficient memory to create RAM-disk', so I'm about to check it changing boot image size fixes this one too. So far, thanks for your remark. I'll keep working.

Shemek
Shemek
6 months ago
Reply to  Shemek

I can now confirm, that newly generated media content works fine. Boot image stays way below 4GB (3.3GB mentioned) and PE booting problem gone. Also, I can now have USB-stick FAT32 formatted.
Big, big thank you again for bringing attention to fact that boot image huge as my previous one, is something that is not supposed to take place.

Last edited 6 months ago by Shemek
Sandreddu
Sandreddu
1 year ago

Hi Johan, thanks for the useful information. Could you be a bit more specific in how to change the "label" of the operating system? Do you mean the "Name" of the indexed OS in the WIM image? I don't seem to find any more info about this

Gammafilter
Gammafilter
1 year ago

Where is the label of the imported operating system defined?


>