OSD pxe boot restrict auto boot

aditya.vaje 2021-02-14 12:34:13 UTC #1

We have added following values on dhcp server Option 66
Relay server IP and Option 67 Rembo-x64UEFI, but some systems auto booting to osd profile, which is dangerous, we want to restrict how can we do control to go in profile manual mode only.

sergio_tarchi 2021-02-18 10:30:39 UTC #2

Hello,
what do you mean for auto booting to osd profile? Do they start a network boot and display the binding menu with the list of bare metal profiles available?
If no selection is done (unless you have a bare metal profile with autodeploy timeout or you are using targeting rules for deployments including that target) the menu will stay and will not do any modification on the computer.
Eventually a password can be added to each of the bare metal profile distributed to the bare metal server that, after selecting the profile, it must be entered or the deployment will not start.
Does this solve the concern?
Thanks.

aditya.vaje 2021-02-18 10:57:30 UTC #3

Sir In a last weak sudden power failure, and all system was network 1st boot sequence, and it directly opens BigFix PXE boot Profile screen, is there option we can do F12 or select manual option to BigFix PXE boot else it will boot to hdd, On windows Server thier is OSD Feature and it having the option for manual interaction option “Require user to press F12 ket to continue to PXE boot”

sergio_tarchi 2021-02-18 11:43:30 UTC #4

A possible solution is to move the network after the local disk in the boot list or there’s some option in the bare metal server to define the behavior of a target computer when it boots against the PXE server. I suggest to handle it together with the support team to select the best one that can apply to your case.

JasonWalker 2021-02-18 21:21:22 UTC #5

Yes, in the Bare Metal Server there is an option, I think in the Boot Profile area, for “boot to disk if idle”.

DHCP Option 43 has, I believe, a slightly better option in that it can display a boot menu and include the local disk as an option (or set that as default option with a timeout).

Changing the systems’ BIOS options to boot the hard drive is still far preferable to either of these. If the Bare Metal Server is offline but is attempted by the client, the client can still get stuck on a “TFTP Failed” message at startup.

With the clients’ BIOS / UEFI set to boot the hard drive first, you’d need to manually interrupt the boot sequence with F12 in order to select a PXE boot. For reimaging existing clients, we have a task in the OS Deployment and Bare Metal Imaging site for “Force network boot” that performs a one-time reboot to PXE, so you can still reimage existing clients without having to visit them to hit the F12 prompt.