1 of 1 people found this helpful
I could explain but Jan/Mike do a much better job Download this ZIP file from DroppedPackets.
Review the HII-Winpe.PDF file section 5. This should help.
There is the following special consideration when editing startnet.cmd prior to 8.7 SP2:
when you edit startnet.cmd in the core server’s ldvpe1.img, the change will not be
propagated to the PXE reps because the PXE rep installation package puts in a new
startnet.cmd buried inside the MSI file. If you wanted to insert additional lines in
startnet.cmd, insert them in both PxeMenuStart.cmd and PxeStart.cmd instead. These
files are called by startnet.cmd.
Another good doc. Windows PreInstallation Environment (WinPE) Whitepaper
LVBoot.img = The DOS PXE Boot file use only during a Vboot. It
becomes a virtual partition and then is that virtual partition is made
the active partition, so the machine boots to this file. The first
thing it does once it boots to WinPE is change the partition table back
to normal. (You probably don't care about this file.)
LDVPE0.img = A partition image that contains the bootstrap files.
This is used only during a Vboot. It becomes a virtual partition and
then is that virtual partition is made the active partition, so the
machine boots to this file. The first thing it does once it boots to
WinPE is change the partition table back to normal. This is used to
boot up and then to load the LDVPE1.IMG
LDVPE1.IMG = A partition image that contains the WinPE partition that
will eventually be the RAM disk.
PEBoot.img = During the PXE Representative installation, the
LDVPE1.IMG file is copied to the PXE Representative and changes are made
to it. Once copied to the PXE Representative, a copy of LDVPE1.IMG is
placed in c:\program files\landesk\pxe\system\images directory and
renamed to PEBOOT.IMG. One of the main changes to this file is an
alternate STARTNET.CMD that is different than the original one used
during a Vboot with LDVPE1.IMG.
Hope that helps...
Thank you both for your help, I think that will help me with what I need to do. Thanks for the link info from droppedpackets. The way I'm trying to do imaging is pretty similar but what I'm looking to do is run a vbscrip I made to query WMI for the model number of the machine while in WinPE. Based on that model number it will download the appropriate drivers to my image in folders I already made before sysprep for various categories such as Video, NIC, Modem, etc.