just to chime in, we have HP Elitepads with UEFI and I have not been able to successfuly boot into PXE via winpe 3.1 or 4.0. Always time out.
I had an issue PXE booting Lenovo Thinkcentre M92's, they'd do the ">>Start PXE over IPv4" and hang there without giving any form of PXE error message. There is an option in the startup section of the BIOS for CSM that needs to be enabled. The help message for this option states "Compatibility Support Module. Permit the loading of traditional operating systems. Enable: to suppoort Non-UEFI operation system. Disable: to support Win8 64-bit and later UEFI aware operation system."
This may not be the issue that some have reported, but I hope it does help someone out.
All thanks for the feedback. Still waiting on UEFI PXE support call but in the mean time I have been able to get the process working by creating a USB Boot media from the remote console. Creates a WinPE3.0 64 bit UEFI bootable stick. I also created a provisioning template with the cmds / steps I desire. A couple of gotchas....
1. Some 64 bit Nic driver may want a reboot before becoming effective in PE (LANDesk inject on the fly).
My solution was to mount the boot_x64.wim and injected the needed NIC driver.
2. If you try to use DISM to apply the image the version is again still 6.1.7601 and does not support /ApplyImage option, copy 6.2.xxxx (64 bit) and all associated files to your share and point your DISM.exe to that mapped location.
Hope this help and will let everyone how UEFI PXE over IPv4 goes.
1 of 1 people found this helpful
Latest Update on UEFI PXE over IPv4.....
So the scoop is as follows...
1. You can not use PE Menu or a schedule OSD scipt. Has to be a scheduled Provisioning task.
2. LDMS9.5 only supports UEFI PXE V2.1, havea question into Dell as to the version on my devices.
Side note, the UEFI USB stick and Provisioning task worked on my Dell Latitude E6430, but the Latitude 10 tablet will not UEFI boot to winpe 3.0
We have HP Elitepad 900 devices. Using Landesk 9.5 but unable to get past the Start PXE over IPv4 Screen. I have scheduled a provisioning template for this machine but no luck.
Yes per LANDesk Support there is an issue with UEFI PXE Rep response. This is suppose to be corrected with SP1 due out June timeframe.
If you are using HP elitepads you will need either the HP Elitepad patch that is available on community (
http://community.landesk.com/support/docs/DOC-27531) or the Base 0228a patch that is only available from support. This is due to a change in WinPE support for 32-bit UEFI which requires WinPE 4.0 (support added by the patch). As Laszlo noted, UEFI requires a scheduled provisioning task for the network boot. You will not get a menu when you network boot UEFI.
As far as the issue with UEFI that is fixed in sp1, that issue affects some hardware and is an issue with the windows 7 boot manager. It will be resolved in sp1, but again, only affects some hardware.
Thanks for the reply Eric and Laszlo,
I updated the server with the Elitepad Patch.
I have redeployed the PXE rep, I have created a provisioning template and have scheduled the machine to boot to this template. (Imported the machine via ldscan) but the screen is stuck on ">>>Start PXE over IPv4, Press [ESC] to EXIT..."
No Other screen displays then after timeout I get "Network Not Found"
I'm trying to boot via the HP Elitepad Dock Station.. Unfortunately I don't have a network attachment so I can try without the Docking Station
I tested our current Lenovo Machines (These run on Legacy BIOS, X201, T410, M58 etc..) and these boot to PXE and Image correctly with the new 4.0 WinPE.
Has anyone else had success with HP Elitepads?
I tried creating boot media as a workaround to image the machines but the boot media it creates are bootx64.efi while the elitepad 900 are EFI 32 bit
I also have a Dell Latitude 10 Tablet that is EFI 32 Bit. To image this device I had to create a WinPE 4.0 32 Bit USB Stick, and manually image the device with Win8 Pro 32 Bit.
You indicated that you scheduled the machine to the template. Did you start the template? As you start it, it will go to active, then to pending again. Then you should be able to network book.
Yep I had started the Task and the machine is now back at Pending
I have created a 32 Bit Win PE 4.0 Image. Just need the NIC drivers to get it onto the network. Did you need to add any landesk software to the WinPE image or once it was on the network you could see it via the console and push out the provisioning task required?
I have logged it with support but these are the steps I am performing for PXE boot let me know if a step is missing
1. Retrieve the MAC address of the machine I would like to image
2. Import the machine to Bare Metal Servers with the MAC Address or Import it into devices via ldscan with a CSV file
3. I have some provisioning tasks that are used for Windows 7 but I'll schedule them just to test PXE booting for the UEFI device
4. I schedule one of the templates and move the new imported machine from devices to the task
5. I run the task and wait until it returns back to "Pending"
6. I plug in a UEFI device to the network and start it up and then force it to boot via IPv4 PXE
7. Device displays screen >>Start PXE over IPv4... Waits for around 60 Seconds and times out
I let it log back into Windows and verify that it can get an IP Address on the network and can ping servers etc.. So Network is definitely working
I've tested with a 32 Bit UEFI (HP Elitepad) and 64 Bit UEFI (Lenovo Helix) and I am unable to get any to boot.
No LANDesk Software added to WinPE 4.0, this was stictly a custom imaging process. Believe LDMS 9.5 SP1 will be WinPE 4.0, but that is just a guess.