Group management AD settings get cleared with newly registered host.

[Jias94]

My school district made a big push to start using Active Directory again and to help with the enrollment process, I wanted to use FOG to help get client machines reimaged and enrolled into AD. However, I ran into a few things I consider bugs with the AD settings with groups.

Fog server version: 1.5.10.1815
Ubuntu version: 24.04.4 LTS

Issue #1, when the Group has no host associations, the AD settings do not get saved to the group.

Issue #2, when there are hosts associated to the group and AD settings are applied, newly registered hosts associated to the group clears the settings. However, the existing hosts in the group still have their settings applied. I have to input the information again in the Group management and update the changes for the settings to stick and re-applies the settings to all hosts in the group.

Issue #3, if a host was accidently registered to an incorrect group but AD settings were already applied, moving it to a different group with different AD OU settings clears the field. Similar to issue #2, manually inputting the information again and hitting update fixes this.

Issue #4, Fog doesn’t move a computer object from one OU to another OU. Is that by design?

Issue #5, If I try to clear the AD settings on a specific host and hit update, the settings don’t actually get cleared. When I go back to that host and go to the Active Directory tab, the settings are still applied regardless if the host is associated to a group or not.

We are working on some other solutions to combat this, but it would be extremely useful if FOG would move Objects around in AD according to where they land in Groups if the Groups have different settings applied. It would also be useful if the Groups AD settings would be saved and then apply those settings as New hosts are associated to the group or if existing hosts get moved from one group to another with different settings applied to the group.

Thanks for the help!

[Tom Elliott]

@Jias94 Issue 1, yes this is expected. 2, 3, yes, yes. 4. Yes. 5. Have you tried updating? 1815 likely had the issue of what you’re describing but i"m pretty sure this is corrected in the latest stable.

Groups are just “mass updaters for Hosts”

You might be more interested in “Persistent Groups Plugin”.

[Jias94]

@Tom-Elliott Thanks for the clarification! I’ll try upgrading to the latest stable version, I was planning on doing this anyway.

I’ll look into the Persistent Groups plugin and see how it works!