@AUTH-IT-Center I do believe snponly would be the recommended, rather than iPXE’s driver.

The developers at iPXE wrote the driver on their own (of course using documentation and stuff, but for all intents/purposes it is still a handrolled driver) so anything is possible.

We shipped the native iPXE 2.0.0 mainly because of the feature it allows with actual Secureboot capabilities and instead of embedding everyfile with a custom script, a more dynamic approach for when iPXE releases new version we can upgrade more easily.

For what it’s worth, I would almost want more people to default to snponly.efi (or secureboot/snponly-shimx64.efi if using/wanting secureboot after enrolling your machines of course) because this is supposed to be using the generic driver for EFI boot protocols on the NIC rather then attempting to discover the NIC using a driver loaded.

@Tom-Elliott no stress, with so many posts it’s normal to miss some 😉

@AUTH-IT-Center Subree is updated to be properly listed as Subtree

@AUTH-IT-Center fog has some hooks and events capable but those are relatively new and not quite as granular as I’d like to see them, though I suppose with the effort of 1.6 it may be worth while to try to find all the possible hooks/events (they can be either and/or both technically) as will as the attributes available for each one. That may help with the event notifications. I warn it does not exist currently.

@AUTH-IT-Center with the dev-branch the created folder after the image capture has the correct permissions.

83223c8f-3d3a-46ab-af0b-c3634e6768ce-image.png

will wait for the update on stable branch to deploy to the production server.

Thank you!