Coming from WDS, there was an ability to respond to all devices, known or unknown, with different PXE boot policies:

Require users interaction pressing F12
ALWAYS CONTINUE PXE BOOT
Continue to PXE unless user presses ESC
Never PXE boot

I could then limit the response to a specific subnet/IP range. And because of it's rather reasonable price, I could easily spin up different WDS servers in different networks. I would really like to see the same with the K2.

In my own environment, when unboxing new equipment, we have a designated VLAN for staging and imaging devices. It would be very beneficial to have the K2 respond differently based on IP address range or even the K2 system NIC the request is coming from:

IP range 10.1.X.X Boot menu
IP range 10.5.X.X Setting defined KBE or system image installation
Traffic on K2 NIC 2 Image with System Image defined in settings

So many possibilities that would make imaging new machines possible without interaction and safely restricted from production networks (if configured properly).

I know there is hesitation to do something like this because, if not configured properly, it could cause serious problems by unintentionally imaging computers on the network. But this is a user configuration problem, not a KACE tool problem. By not offering this capability at all, it punishes and hinders everyone that is willing to configure it properly.