[FONT=Tahoma][COLOR=#141414]My apologies to anyone trying to read this thread without having seen it first on the [URL=‘http://sourceforge.net/projects/freeghost/forums/forum/716418/topic/4719993’][COLOR=#555555]sourceforge forum[/COLOR][/URL], I was not aware how much the formatting was messed up.[/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414] [/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414]My first thought was something like “Great! Deeper AD integration will remove the hassle of setting everything up the first time, and might even be able to maintain things in an orderly fashion!” but I have a hard time believing anything like that would be easy to implement or work as smoothly as I would like.[/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414] [/COLOR][/FONT]
[FONT=Tahoma][COLOR=#141414]Some initial questions for this approach:[/COLOR][/FONT]
[LIST]
[]Would FOG do a scheduled pull from AD or would a manual import be simpler to maintain?
[]Would these groups be locked down in some way, or would users be able to add or remove hosts from a group built by AD?
[*]How would this play out in a host swap scenario since the new host wouldn’t be in the correct OU until it’s finished imaging?
[/LIST]
I remember seeing that field and wondering why it wasn’t actually called anywhere… but my main focus was getting usernames listed under the Active Tasks page, and it seemed less terrible to just slap the currentUser onto the task name than to write a function to call a single field.
[FONT=Tahoma][COLOR=#141414]FOG does not create or maintain a list of the software installed on the hosts. There are other open source projects out there that can do this (such as open-audit.org), and plenty of companies that sell software that will scan your hosts and provide inventory reports.[/COLOR][/FONT]