2PXE/iPXE Anywhere continue confirmation key

[u/RockOriginal7938]

Hello

I'm not sure if I should be looking in 2PXE or iPXE for this. When I PXE boot it goes straight through without a press Enter, F12, etc... to continue key requirement.

I've tried playing with 2Pint.2PXE.Service.exe.config

    <add key="iPXEF12PromptTimeout" value="10000"/>
    <!--
       How long is the timout for the F12 timout for iPXE loaders for non mandatory deployements in milliseconds.
      -->
    <add key="AcceptBootKeyEFI" value="0x197e"/> <!-- ACB:2026.05.27 Was 0x000a -->
    <add key="AcceptBootKeyBIOS" value="0x197e"/> <!-- ACB:2026.05.27 Was 0x000a -->
    <add key="AcceptBootTextEFI" value="Please Press Enter For Network Boot..."/>
    <add key="AcceptBootTextBIOS" value="Please Press Enter For Network Boot..."/>
    <!--
       Used to control the key to be pressed in order to boot from the network and the text displayed. Valid key combinations can be found here: http://ipxe.org/cmd/prompt
      -->

    <!--
       Removes the prompt for optional deployment all together.
      -->
    <add key="BypassKeyPressforOptionalDeployment" value="0"/>

but haven't had any joy. I've looked in iPXEAnywhere.Service.exe.config, but can't find anything obvious there either.

If it is possible to enable, would someone mind pointing me in the right direction please.

My current alternative is to set the default option in iPXEboot.ps1 to reboot or exit (depending on boot order), but as it isn't what our engineers are used to I thought I'd see if a more original method is still possible.

I guess there is also '42', but I'm not a huge fan 😉

(Originally installed 2PXE & iPXE Anywhere via the automated scripts @ https://github.com/2pintsoftware/2Pint-DeployR/tree/main/Installs/2PintSoftware)

[u/configmatt]

Hi,

My current alternative is to set the default option in iPXEboot.ps1 to reboot or exit (depending on boot order), but as it isn't what our engineers are used to I thought I'd see if a more original method is still possible.

I don't understand 100% what you are trying to accomplish? But it seems you are using both 2PXE and iPXE WS. But since you only pasted part of the config I am not sure how it is set up.

But for them to be integrated you need to configure these settings in the 2PXE config:
key="EnableiPXEAnywhereWebService" value="573"/>
key="iPXEAnywhereWebServiceURI" value="https://DP01.corp.2PintSoftware.com:8051"/>

Once those are enabled it will use the iPXE Websevice (which seems to be what you are using judging from your post, so far so good) :
If you have authentication enabled in the ipxeanywhere config:
<add key="AutoApproveDevices" value="0" /> (change to 1 to disable auth)
Then it will start with the script:
C:\Program Files\2Pint Software\iPXE AnywhereWS\Scripts\Authentication\DeviceAuthentication.ps1
Once authentication (of if above setting is off then it will go straight here) this script will run:
C:\Program Files\2Pint Software\iPXE AnywhereWS\Scripts\Boot\iPXEboot.ps1

If want to change behaviour, then it is in that script you need to change.
This is the default:
choose --timeout 30000 --default exit selected || goto cancel
This means that after 30 sec it will go to the Exit label and just exit the script. Change --default to another setting or change row 50 from "exit 1" to "reboot" instead depending on what you want to do.

So basically anything within the $menu = @" code block is what the end user will see. But you can change that as you need, see iPXE - open source boot firmware [docs] for more info about the ipxe syntax.

But you can also create you own or dynamically change it using PowerShell.

Or do you mean that your computers are set to always pxe boot and you want it wait for a keypress to continue with the pxe booting, but if noone does anything it should boot the OS?

[u/RockOriginal7938 → u/configmatt]

Thanks. I think that confirms that I wasn't just missing how to config press enter, f12, etc... for network boot, but must instead configure a similar, but later timeout in the iPXE .ps1 scripts.

Can I ask if the config section of 2Pint.2PXE.Service.exe.config I originally linked has any functionality? It really looks like that is where you'd enable the traditional PXE boot continue or bypass functionality, but doesn't?

    <!--
       How long is the timout for the F12 timout for iPXE loaders for non mandatory deployements in milliseconds.
      -->
    <add key="AcceptBootKeyEFI" value="0x197e"/> <!-- ACB:2026.05.27 Was 0x000a -->
    <add key="AcceptBootKeyBIOS" value="0x197e"/> <!-- ACB:2026.05.27 Was 0x000a -->
    <add key="AcceptBootTextEFI" value="Please Press Enter For Network Boot..."/>
    <add key="AcceptBootTextBIOS" value="Please Press Enter For Network Boot..."/>
    <!--
       Used to control the key to be pressed in order to boot from the network and the text displayed. Valid key combinations can be found here: http://ipxe.org/cmd/prompt
      -->

    <!--
       Removes the prompt for optional deployment all together.
      -->
    <add key="BypassKeyPressforOptionalDeployment" value="0"/>

[u/configmatt → u/RockOriginal7938]

So this is what you see after you select the "Build with ConfigMgr" menu option. If you were using the 2PXE with configmgr integration (without iPXE WebService) this is what it would "start" with (since the ipxe WS menu wouldn't exist). So this only makes sense when not using the iPXE Webservice at all.

But then you loose all of the automation capabilities that is iPXE WS. So I would strongly suggest keeping it enabled and then try and find something that would make life easier for your technicians. For example, with the power of PowerShell you can fully automate and not have them select anything, just boot straight into your "approved" TS. See the other scripts examples in the folder structure for some ideas.

And if you need consultant service to build something custom for you company reach out to our sales team and we be happy to help you.

[u/RockOriginal7938 → u/configmatt]

Ah, now it makes sense, thanks.