@Tom-Elliott aha, that explains it, I installed the stable branch and I’m on 1.5.10. Guess I need to upgrade then to working-1.6!

@george1421 No, they were in proper failover config and the options replicated between the scopes. But it’s all good now and that’s the important thing ❤

@Tom-Elliott latest pull resolved the issue. Appreciate your help on this!

@AlexisPHC The branches are separate from things so if someone removed it in dev-branch/stable/master and I didn’t know about it for working-1.6 it wouldn’t have been removed there.

I just updated to account for this that should help you out.

@Tom-Elliott Just wondering if I could have your input here.

I think I have the same problem and I want to be sure of exactly what I need to do (I don’t know if there is a step-by-step tutorial…).

I boot with a USB-C network adapter on an HP Elitebook. It finds FOG, I have the menu, I choose to deploy an image, and then I get this error message:

IMG_20251106_162705.jpg

Is this the problem in question?
If so, what exactly should I do? I see (link @FlorianLenz ) that I need to replace two files with the new ones, then run the .sh. But isn’t that dangerous for other network boots?

Thank you in advance for your help.

I tried reinstalling the Capone plugin, but that didn’t work.

I checked my other machines that show the fog.capone option and I manually added it in using the New iPXE Menu Entry option with the same values as my other machines. I haven’t tested if this is the solution yet. Here’s a screenshot of my values:
d4f5f292-a652-4796-ad66-2531d9920b01-image.png

Finally found out why I couldn’t auth over 636, I needed to add my domain’s CA cert to the FOG server’s root cert store. Once I did that I can now use my AD creds over 636 on the web UI and iPXE menu items.

@88fingerslukee Thank you, I promise I will try your project and leave a feedback.