@Tom-Elliott What’s the difference between the full and quick registration processes then? because AD join exists in full, but not in quick…

Could we add another flag to the quickreg process to allow for AD settings to be applied also please? While we can associate with a group, group settings aren’t persistent and require them to be refreshed onto all members. Full reg asks if you want to do an AD join and enables the expected options (Both for the AD Join settings, and their enforcement).

@Tom-Elliott Cheers, works as expected now!

@Tom-Elliott You can test - assign a group to a host, ensure the host does not have enforce turned on. Go to the group, enable the option under client settings, hit update. Verify the option is not carried down to the host itself!

As per the subject, this setting doesn’t seem to deploy it’s settings to the associated members when we click update.

@Tom-Elliott latest message is “Done, with Imaging” and proceeds to boot round to deploy the image!

@Tom-Elliott right-o. On it.

I’ve also got an oddity where it won’t join these quick registered machines to AD - they should inherit those settings from the group they are placed in right? Even after I deploy the image again, the AD stuff doesn’t happen. Works fine for a full registered host.

@Tom-Elliott from working-1.6 ?

Next issue lol!

When doing a quick registration, I have my settings set to deploy an image;

This was working in stable iirc, but now we get “Done, without imaging: Invalid login”

Ok, nevermind, did the git thing, got it working, cheers

@Tom-Elliott I didn’t install from GIT, but from the ZIP (as that was the same way I’d installed the stable build) - does the ZIP auto-update?

@Tom-Elliott can confirm, this does now appear to work in 1.6 - huzzah! @george1421 looks like your hard work has paid off and it will eventually be in the stable branch!

In stable, when I went to the fog settings option in the fog configuration page, I was able to edit the settings from that page.

However in working-1.6 I am unable to edit these settings, and in a way it is worse to navigate. they were handily grouped previously, although the search in 1.6 does appear to be better.

Double clicking/right clicking doesn’t appear to make any difference.

@Tom-Elliott cheers - looks like someone changed working branch in 2019 to add hdbios, and it’s not something that’s in the dev branch either!

Hi All,

Just some feedback here, once I upgraded to working-1.6 everything worked fine for me (save having to kill my cookies to get back into the GUI) apart from the PC’s stopped at boot and displayed this message;

This seems to relate to the scanfor line in the refind.conf. In stable this line reads;

scanfor netboot,internal

But in working-1.6 it is;

scanfor netboot,internal,hdbios

My brand new Dell Pro Micro QCM1250’s didn’t like the hdbios part of this, removing that from /var/www/fog/service/ipxe/refind.conf solved my issue.

Was this a deliberate change to add hdbios in there for a particular reason, or has this crept in from that project?

@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 I’ll give that guide a whirl, {SYSSERIAL} doesn’t seem to work - this is what happened when I tried it!

@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