Skip to content

Commit

Permalink
Merge pull request #9818 from MicrosoftDocs/frankroj-patch-1
Browse files Browse the repository at this point in the history
Clarify > 4GB WIM files
  • Loading branch information
prmerger-automator[bot] authored Feb 14, 2023
2 parents 27285fd + 001337f commit 6167325
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions memdocs/configmgr/osd/deploy-use/create-stand-alone-media.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ Your user account needs at least **Read** access rights to the content library o

If you're using a removable USB drive, connect it to the computer where you run the Create Task Sequence Media wizard. The USB drive must be detectable by Windows as a removal device. The wizard writes directly to the USB drive when it creates the media.

Stand-alone media uses a FAT32 file system. You can't create stand-alone media on a removable USB drive whose content contains a file over 4 GB in size.
Stand-alone media uses a FAT32 file system. You can't create stand-alone media on a removable USB drive whose content contains a file over 4 GB in size. This doesn't include WIM files since Configuration Manager will split WIM files over 4 GB so that they are under 4 GB and compatible with FAT32 files systems.

### Create an output folder

Expand All @@ -123,13 +123,16 @@ Before you run the Create Task Sequence Media Wizard to create media for a CD or
4. On the **Media Type** page, specify whether the media is a **Removable USB drive** or a **CD/DVD set**. Then configure the following options:

> [!IMPORTANT]
> Media uses a FAT32 file system. You can't create media on a USB drive whose content contains a file over 4 GB in size.
> Media uses a FAT32 file system. You can't create media on a USB drive whose content contains a file over 4 GB in size. This doesn't include WIM files since Configuration Manager will split WIM files over 4 GB so that they are under 4 GB and compatible with FAT32 files systems.
- If you select **Removable USB drive**, select the drive where you want to store the content.

- **Format removable USB drive (FAT32) and make bootable**: By default, let Configuration Manager prepare the USB drive. Many newer UEFI devices require a bootable FAT32 partition. However, this format also limits the size of files and overall capacity of the drive. If you've already formatted and configured the removable drive, disable this option.

- If you select **CD/DVD set**, specify the capacity of the media (**Media size**) and the name and path of the output file (**Media file**). The wizard writes the output files to this location. For example: `\\servername\folder\outputfile.iso`
> [!IMPORTANT]
> It is important when creating stand-alone media on a removable USB drive that the removable USB drive is created directly via the Configuration Manager console using the **Removable USB drive** option. Creating an ISO via the **CD/DVD set** option and then copying the contents of the mounted ISO to a removable USB drive formatted FAT32 may not work since WIM files over 4 GB may not be split when using the **CD/DVD set** option. FAT32 does not support files over 4 GB. Stand-alone media on removable USB drives need to be formatted FAT32 so that they are bootable on UEFI devices. UEFI devices will only boot from FAT32 volumes.
- If you select **CD/DVD set**, specify the capacity of the media (**Media size**) and the name and path of the output file (**Media file**). The wizard writes the output files to this location. For example: `\\servername\folder\outputfile.iso`

If the capacity of the media is too small to store the entire content, it creates multiple files. Then you need to store the content on multiple CDs or DVDs. When it requires multiple media files, Configuration Manager adds a sequence number to the name of each output file that it creates.

Expand Down

0 comments on commit 6167325

Please sign in to comment.