Implement the ability to disable the writing of the PXE-Flag
If the local hard disk is the first in the client boot order, there is no need to write the PXEFlag. In fact it is a problem: If the boot image download fails because of a TFTP error, the client can not boot from network again. An administrator must be called to "Clear the required PXE flag".
Just implement a switch to allow or disallow the writing of the PXE-Flag to the database.
Updating status to Declined.
We appreciate the feedback, the PXE flag is needed in many instances.
and it may be not needed in other environments. there should be the choice to use it or not.
seb cerazy commented
If you do not need the PXE flag then you do not even need to boot from SCCM TFTP. You can use ie iPXE with wimboot to have really fast deployment, as per:
Because it might be dangerous in some scenarios this should be implemented as a switch. Only people how know what the risk is should turn the switch.
This suggestion is dangerous in many environments. The PXE flag is a fail-safe to prevent computers from being accidently re-imaged when they shouldn't. I'd rather have the extra step for the few times a boot image fails to download than deal with the huge potential for data loss if a PC gets re-imaged.
Vincent P. commented
Thank you, this is so annoying!