@myles - All that said, if we can do a start-up script so the boot order changes back to OS drive being at the top of list after a re-image then we might be in luck. Seems like we have a lot to think about here but might just be possible.

Thanks for the quick reply @george1421

I’m going to do further tests to confirm if waiting long enough boots into windows. I believe this might be an issue for our clients though. They’re bound to complain about their reboots taking minutes instead of the usual 15 seconds. The time it takes for PXE boot to fail might be something we can get away with, but for them to watch an undesired PXE boot to happen will almost certainly trigger complaints, especially those clients who are up against it with deadlines and have rebooted because of a crash or some other issue already grating on them. I’ll need to do lots of tests and bring down the boot to windows time as low as possible.

Again, thanks in advance for your reply.

Hi All,

We’ve completed the installation of Fog Server in our company and plan to use it as our image deployment solution for the 500 HP workstations we have across 5 different building sites (all networked together).

Currently in the testing phase, we’ve hit a snag whereby unfortunately we’ve found that HP do not offer a “one time PXE boot” solution like the one offered by Dell. Instead, with HP all you can do is use their BIOS Configuration Utility to modify the boot order within Windows10 CMD. Sadly, once changing the boot order to put NICs to the top of the list it stays that way until the next time you log into the OS so you can change it back. What a shame!

The issue we’re having is once the NICs go to the top of the list on our test workstation we find it always boots into the Fog server interface, never proceeding into Windows 10.

Is there a way to configure it so Fog only accepts DHCP UEFI requests if the mac address attempting to PXE boot has an active fog task associated with it? This would solve the problem we’re having with the HP workstations because we can then put all our machines to network boot by default, and watch them time out and proceed to Windows 10 as they are unable to perform handshake with Fog. If that makes sense?

Hope all is well in the community and thanks in advance for any replies.