Default PXE boot order oddity.

Hi.

ZCM 24.2. Several different machines (and vms too) configured to boot into PXE by default, so they get processed through the imaging work-to-do logic.

Now on *some* machines, after a new image has been laid out, when they reboot, and should start subsequently windows from the hard disk, instead they are being stuck in a PXE boot loop (which does *not* put down the image again).

The only way out of this, and here is why I believe this is a ZCM issue, is to either change the boot order so that the disk is first instead of PXE (which of course beats the purpose), *or* actually hit "ESC" to cancel the PXE boot. When hitting ESC, the machine will boot windows from the HD next, but when I wait and let it process the "no work to do" by ZCM, it will simply reboot into PXE again, and get stuck in a loop.

One affected model with this behaviour is a DELL 3510 Notebook (tried several, all behave the same). A Lenono Yoga 13 does *not* show the same behaviour, neither a VM inside VMWare Workstation 17 (aka, those properly boot windows when ZCM determines there's no imaging work). But its not limited to Dell, I lso have a Fujitsu Notebook behaving the same as the Dells.

Anybody else?