WinPE partition after installation

[SisterOfMercy]

I finally had to start with preparing windows 7 for deployment. This is because of a few laptops with a broken bios (yay, asus ) and the possibility the security updates for XP x64 will end in 2014 and not in 2015, like other NT5.2 operating systems.

Well, I'm well underway with my customisation package and beating it into submission. A lot of the settings have not changed since XP, so a lot of the XP x64 customisation package can be reused. I find myself deploying more and more SSDs, in my not so humble opinion windows 7 without an SSD is a very bad idea. So anyway, harddisk space is limited.

Is there any reason not to extend the windows partition to include the space reserved for the WinPE partition? I was planning on using this:

Code: Alles auswählen

"%SystemRoot%\system32\diskpart.exe" /s "%ScriptPath%\files\extendscript.txt"

where extendscript.txt contains this:

Code: Alles auswählen

select disk 0
select partition 1
extend

Or can I safely set the WinPE partition to 0 MB in configed, because it is only used for special situations?

[Fochlac]

Hei,

This partition usually contains the boot manager and is used to support the BitLocker encryption system and is generally only created, if there is no other partition on the drive. Removing it after the installation or shrinking it is generally a bad idea as it can cause a number of problems later on. However, if you partition the disk before installing Windows you can avoid it being created.

More detail here.

All the best,
Fochlac

[SisterOfMercy]

This is not the 100 MB boot manager partition. This is the WinPE partition, made by OPSI.

[wolfbardo]

Is there any reason not to extend the windows partition to include the space reserved for the WinPE partition?

The Winpe-partition should be removed after the os-install by a opsi-postinstscript created from the setup.py. If not, there is something broken from your changes to the unattend.xml.

Have a look at the getting started about the unattend.xml

Take in a first step the template from opsi and then change carefully the custom unattend.xml

Otherwise the opsi-postinst-scripts, opsi-client-agent-install, partitions-settings ... might be broken

regards,

bardo wolf

[SisterOfMercy]

The Winpe-partition should be removed after the os-install by a opsi-postinstscript created from the setup.py. If not, there is something broken from your changes to the unattend.xml.

Yes, blame me

Well, if I look at the 80_repartition.cmd in the opsi/postinst.d/ directory, it looks like it executes diskpart with this script (diskpart.txt), but that doesn't seem to do much:

Code: Alles auswählen

LIST DISK
LIST VOLUME
SEL DIS 0
LIST PARTITION
EXIT

[wolfbardo]

ok,

The Winpe-partition should be removed after the os-install by a opsi-postinstscript created from the setup.py. If not, there is something broken from your changes to the unattend.xml.

is to sloppy.

Look at the setup.py (The Winpe-partition should be removed after the os-install by a opsi-postinstscript which uses the diskpart.txt which is patched from the setup.py. )

regards,
bardo wolf

[SisterOfMercy]

from setup.py

Code: Alles auswählen

	# Create diskpart.txt
	logger.notice(u"Creating diskpart.txt")
	f = open(target + '/opsi/diskpart.txt', 'w')
	print >> f, "list disk\r"
	print >> f, "select disk 0\r"
	print >> f, "list partition\r"
	print >> f, "list volume\r"
	print >> f, "select partition %d\r" % winpePartitionNumber
	print >> f, "delete partition noerr override\r"
	if dataPartitionCreate:
		print >> f, "select partition %d\r" % (winpePartitionNumber - 1)
		print >> f, "extend\r"
	if bootPartitionNumber and bootPartitionHidden:
		print >> f, "select volume %s\r" % bootPartitionLetter
		print >> f, "remove letter=%s\r" % bootPartitionLetter
	print >> f, "exit\r"
	f.close()

Ah, I'm not using a data partition, that's probably why the partition did not get extended, right?

[d.oertel]

Hi,

hmm - looks like a bug - I will think about it and opened therefore an internal ticket ...

regards

d.oertel