SetupComplete.cmd and diskpart?

[ahmadj]

Hi all,

I am using sysprep to prepare Windows 7 images for deployment. My sysprep images are built in a (VirtualBox) VM.

I have recently added a SetupComplete.cmd file to my image, at C:\Windows\Setup\SetupComplete.cmd. It reads:

diskpart /S ntfsextend.txt

And ntfsextend.txt, also in the same directory, reads:

select volume 2
extend
exit

However, having cloned the sysprepped image to a larger disk, the diskpart script does not seem to be run during setup. The SetupComplete.cmd and ntfsextend.txt files are still there, and when run manually after setup, will correctly expand the partition.

Is this a privileges issue or something else?

[Tripredacus]

How are you deploying this image? There shouldn't be a reason to extend the disk... since you'd run diskpart prior to imaging to set up the partition.

[ahmadj]

I'm deploying the image using Clonezilla, from an NFS share. It has the ability to extend NTFS partitions during the clone, but it seems to trigger a CHKDSK on first boot, so I feel (a little) safer doing it from within Windows.

[iamtheky]

if you put anything in setupcomplete.cmd does it fire (or is it just this specifically that is failing)?

If no:

is there something in winpeshl.ini?

If yes:

Does it work from runonce?