Sysprep takes a long time to finish when the "Build Mass Storage" section option is set to "Yes"
Last Updated April 20, 2006
Creating a Sysprep image takes a long time to finish, and the initial Sysprep process before the image capture can take over an hour.
This is not an issue with Deployment Solution.
This is caused when the BuildMassStorageSection is set to yes, causing Syprep to generate the entires for the [SysprepMassStorage] section which is required in order to deploy your image to computers with different SATA or SCSI Controllers than the source computer has.
You have two options to improve the speed of your imaging tasks.
If you do not need to deploy your image to different SATA or SCSI Controllers, edit your Sysprep.inf file and set BuildMassStorageSection to no.
Otherwise, you can run sysprep with the BuildMassStorageSection set to yes and a blank [SysprepMassStorage] section in your Sysprep.inf. Sysprep will generate the Mass Storage Section. You will then have a Sysprep.inf file with a pre-generated [SysprepMassStorage] section so that that section will not need to be regenerated in future Create Disk Image tasks. (See KB Article 21224, page 9 for details)
Applies To Deployment Solution, capturing an image of a computer prepared with Sysprep.
Imported Document ID: TECH13585
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe