I believe this is the 'local data store' option. You burn a CD/DVD and drop it into the target system.
No, it is not the use of the local datastore.
My request is different.
It is the step before, just avoid the needs to call a DHCP/PXE server.
At the end of the boot sequence, the boot WINPE image should be able to request its installation instructions from the Provisioning server.
For provisioning from a local data store, you can use either:
ISO or UFD image files for booting the target server from a WinPE image mounted
on media local to the server, without using the PXE server (local boot).
A local boot can be done from the same media that you use for the local data store
or from different supported media. For example, you can keep operating system
installation files on a DVD and boot the WinPE image from an iLO.
I did not read correctly the documentation or understand it.
Thanks for your answer.
You are definitively the master...
I have a doc somewhere that describes how to make an ISO image out of the winpe.wim. I think it's on the internal wiki too. it won't ask you for an ip, you have to hardcode it or use dhcp. But you can hardcode the BL_AP and BL_AS settings (the 211 and 212 dhcp options)
I tried to find it on the Wiki, but I did not find anything.
Could you send please send this doc to me ?
I just tested the BMI callback program (bmi.exe) in a WinPE and it is possible to set the ENV-variables BL_AS and BL_AP before calling the bmi.exe. This means it works exactly as the Linux counterpart.
Here the command line output from within the WinPE:
HOST: xxx.xxx.207.144 PORT:9831
MACADDR : 00-16-35-59-D8-E0
You should be able to set those in the winpeinit.bat or one of the other files that bladelogic created w/ the winpe generation process. I'd look at modifying the source files so you can generate winpe files w/ the right entries.