@george1421 Bizarrely, came in this morning and it was working happily! not the foggiest what was wrong, but does seem to have sorted itself out somehow!

@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!

@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