did you create those scope options in your dhcp server? and the optionm 60 since i'm assuming the pxe and dhcp are running on the same box.
I had been doing my own digging on this, and it looks like I'm going to have to change my environment. My DHCP server has been, up to this point, my wireless router. I looked around on there, and there is no where to set anything with regards to scope options.
My plan of attack from here is to remove the DHCP server from my wireless router and put a DHCP server on my PXE server. From there, hopefully, I'll see settings regarding this and be able to clear this problem up.
are you running this inside vmware? you can setup a separate network in vmware and keep it all internal to that.
I am stuck at a similar stage provisioning windows via a WIM image.
I believe this is where it should show the bl-server and bl-port options but that does not happen. The sequence is stuck at this stage.
bl-options set to the appserver listening on 9831
nothing in appserver.log or pxe.log or tftpsvr.log
there would not be anything in the pxe or tftp logs at this point because we are done w/ both of those here.
have you verfied the scope options in the dhcp server?
The options are where I believe the problem was as well and we thought we had found the source.
They were pointing to the development environment (we have more than one environment)
The client uses QIP and the template for this MAC address was corrected but no change at all in the prov process.
Do you know if it attempts to communicate to the appserver on 9831 at this stage bill? We are in a firewall rich environment and it would be good to understand what is occuring in the background at this stage.
If you have more than 1 NIC enabled on the target server which is booting in WinPE, you may face this issue where it hangs at "reading DHCPack response". This was fixed in 8.1 SP2 and 8.0 SP10.
Fix: The read request for DHCP response is now added with the timout to unblock the read request.
Rupali - thanks I think you are on to something there because these VM's have multiple NIC's. It works in another environment with SP1 but for some reason that environment always loads the NIC's in a different order which I can see during the boot sequence. Sadly an upgrade is difficult due to time issues.
The SPprovisioning-files.zip for PXE only contain the bmiwin and bmilinux files. If we replace these files in pxestore is that all thats required to get around the issue above?
In other words, once we have upgraded to SP2 P5 do I need to re-create the boot image from WAIK from scratch?
There’s a bmi.exe in the winpe directory from that zip that gets placed in the winpe image when you generate it. that will be updated w/ newer versions of blade and I’m assuming that’s what needs to be updated in your case, so you probably need to re-generate your winpe image w/ the new bmi.
Yes that right, you will just need to rebuild the boot image using 8.1 SP2 bmi.exe file, since bmi.exe code has the fix. You may not even need to upgrade entire build to SP2 for this particular fix.
I've run into the exact same issue, and I was able to resolve it by rebuilding the WinPE image after modifying the init.bat and init2k3.bat, specifying the BL_AS and BL_AP, as this KA explains:
When multiple NICs are installed, the installer will probe all NICs to find the Application Server.
This workaround will help either when provisioning a box with multiple NIC as well as provisioning without having a DHCP Server.
Hi Mauro et all,
We are running into the exact same issue while PXE provisioning a physical machine with Windows Server 2012.
Do you know if the explained workaround from the KA is still valid or if there is already a fix implemented in the current BSA build?
I'm asking because I really don't like the fact that we have to hardcode the BSA App servers IP address into the WinPE image. We have 5 different environments which means we need to recreate the image in every environment.
Which verison of BSA (build) are you using?
If you are already using BSA 8.1 SP2 or later, the fix is already available with you.
Though, as mentioned above, you need to "rebuild" your WinPE boot image using the "bmi.exe" from the 8.1 SP2 or later builds to fix this problem.
Thanks and Regards,