QuickReg - Apply AD Settings

[AlexisPHC]

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]

@AlexisPHC I’m hesitant to add such a feature.

While I can definitely see the appeal, I almost think this would be better as a plugin rather than an OOB nature of FOG as we’ve been around doing Quick Reg for quite a long time.

Now could this have been requested in the past and just missed? Absolutely.

I still think I would envision this type of thing more as a plugin (maybe even separating Quick registration as a whole) as a plugin.

Why?

All the features FOG does provide out of the box is quite extensive and difficult to manage at the best of times.

Now as to why quick reg, in it’s current state, is included in the baseline FOG? Because it’s more than just the UI interactions but also the FOS side of the house.

So the way Quick reg exists today in the FOS/UI would likely remain as is. As for adding new features? I think this is the part where it can be incorporated completely separate from the UI/FOS side as a plugin.

I have to think about how it could be done, but just wanted to give a base line thought process I have going on.

(Seeing at least what you’re requesting is more about the PHP side of things and managing them - including beign able to more generalize what kind of key flags could be used to name the device - more than just SYSSERIAL for example.)

Sorry for the bit of ramble, just the thoughts as I see them.

[rodluz]

@Tom-Elliott Just thinking out loud here… Like you said, the UI interaction would probably be best as a plugin. For the FOS side, I would think that this could be done as a post init script modifying the fog.auto.reg, right?

[AlexisPHC]

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