Users may use the Microsoft System Preparation Tool (Sysprep) to prepare an image for deployment. One rule for the use of Sysprep has been that the size of the destination computer’s hard disk must be at least the same size as the hard disk of the master installation. If the destination computer has a larger hard disk, the difference is not included in the primary partition. However, the "ExtendOemPartition" entry in the Sysprep.inf file can be used to extend the primary partition on the destination computer if it was formatted to use the NTFS or FAT32 file system by using the following values.
Modify the Sysprep.inf file to use the "ExtendOemPartition" key in the [Unattended] section to extend the partition to the full size of the target disk or the extra size (in megabytes) that you want. Values:
The "ExtendOemPartition=1" entry has been known to cause a blue screen when used in combination with a 512e/4K Advanced Format hard drive. The problem arises when a Windows XP image is using Sysprep and has the entry "ExtendOemPartion=1" in the sysprep.inf file. That invokes XP's version of Diskpart to extend the XP partition (NTFS or FAT32) to use any unutilized disk space on the hard drive. When that happens, it extends the drive during sysprep and ends that partition extension on a boundary that is not aligned and compatible with the partition boundary that was set to be compatible with 512e/4k Advanced Format hard drives. This process creates a partition that is of an unrecognizable size and may result in a blue screen during the imaging process. To resolve this issue, please remove the "ExtendOemPartion=1" line in Sysprep.
Article ID: SLN82460
Last Date Modified: 01/07/2015 12:12 PM
Thank you for your feedback.