the winpe file is the winpe.wim file, however, in the PM when you setup the image location you are going to specify the directory that the winpe.wim sits in after it gets generated (eg boot_2_0 or boot or whatever you specified when you created the image)
So to recap...when creating the entry in the boot images file tab within the PM/Tools/Configurations utility, the image file entry would be winpe.wim with the image path being the location of that file??
I read and re-read the documentation and the light just went on. We'll see how far I get.
I have had some success in getting WinPE to work. The server will startup Windows and launch wpeinit. I get the following message after a short period of time.
The command completed successfully
No buffer overflow
A message box appears stating:
The instruction at 0x004028ac referenced memory at 0x00000000. The memory could not be read
Click on OK to terminate the program.
I ran through each command in the init.bat. The command line that fails is the bmi.exe.
did you use the right bmi for the winpe architecture? (eg x86 or x64?)
what version of the 'provisioning files' are you using? you should be able to use newer versions of those files w/ earlier versions of bladelogic (eg a newer bmi)
I´ve seen this error when the needed network-card drivers are missing in the WinPe Image. Check the output of "ipconfig" in the command window to see if WinPE sees any network interfaces. If the drivers are correct, you should see your network-card with an DHCP-Assigned IP-Address. If not, rebuild your WinPE Image and include the correct network-card drivers.
I pretty sure I have been using the version provided with 7.4.1. How would I make sure this is the case? Is there a way to check the version without running it?
i don't know if we put a version tag in any of the scripts you run to build the winpe image. the only real change is the bmi executable, you could try rebuilding w/ a newer bmi from the product downloads (the bmc EPD site now), and check the network drivers as the other poster suggests. sometimes the drivers for winpe 2 are different than the drivers for 2003.