Quick Inventory Group
-
i agree that being able to specify groups during registration would be useful. for example, last week i had student workers registering 3 labs of computers in fog that should all be grouped differently, and they would have been able to add them to the appropriate groups instead of having to sort them out later. though, i would put it in as part of “full” registration instead of quick.
-
I agree with Junkhacker. I am nearing a massive registration project, and group specification would be… nice.
-
[quote=“Junkhacker, post: 27856, member: 21583”]though, i would put it in as part of “full” registration instead of quick.[/quote]
The only reason I ask for quick registration is because my current proccess for new machines is to simply plug them in and do a quick inventory which also images the machine. That is where i would like it to end. However currently i would have to then, after quick inventory, log into fog, move it to the group which AD’s and possibly re-image it as it seems before it gets added to the domain.
It would be great to be able to give quick inventory a default group so that once it images it just adds to the domain and is just done there and then.
-
[quote=“tlawson, post: 27983, member: 24197”]The only reason I ask for quick registration is because my current proccess for new machines is to simply plug them in and do a quick inventory which also images the machine. That is where i would like it to end. However currently i would have to then, after quick inventory, log into fog, move it to the group which AD’s and possibly re-image it as it seems before it gets added to the domain.
It would be great to be able to give quick inventory a default group so that once it images it just adds to the domain and is just done there and then.[/quote]
I plan to add a feature where the init registration asks if you want to add it to a group, but not for Quick Inventory. The reason? Because quick registration/inventory is designed to be just that. Quick, if we start asking questions about what you want for both Full AND Quick registration processes, it defeats the purpose. I may, for this purpose, add a field to the QUICKREG_AUTOPOP that allows you to assign a default group to assign the Device though. Hopefully this would achieve the results you’re looking for?
-
[quote=“Tom Elliott, post: 28012, member: 7271”]I plan to add a feature where the init registration asks if you want to add it to a group, but not for Quick Inventory. The reason? Because quick registration/inventory is designed to be just that. Quick, if we start asking questions about what you want for both Full AND Quick registration processes, it defeats the purpose. I may, for this purpose, add a field to the QUICKREG_AUTOPOP that allows you to assign a default group to assign the Device though. Hopefully this would achieve the results you’re looking for?[/quote]
Sorry if i was not clear, i did not intend this to be a question inside the PXE boot part, i meant as an option in the webui where i can set other settings for quick reg such as image id. I by no means wish to break the quick part of quick registration and inventory.
-
I think that’s what I had already thought about doing
-
This is now added and functional in SVN 1731
-
[quote=“Tom Elliott, post: 28179, member: 7271”]This is now added and functional in SVN 1731[/quote]
Love your work, thanks mate.
-
I am a little daft. It seems i missed a crucial part of the FOG AD wiki ([url]http://www.fogproject.org/wiki/index.php/Active_Directory_-_FOG_Setting#Groups[/url]) where it states
[QUOTE][B]Note:[/B] This is a applied in a batch for each host in the group when saved. These settings are not stored in the group settings permanently, nor applied to future hosts automatically when added to the group.[/QUOTE]So this still does not solve my problem of wanting to auto add new machines to AD without intervention. Thanks anyways though.
-
This is because, from the group, if you’ve added new hosts, you can simply reapply and will apply to all hosts again.
I’m very sorry that this was not as you expected, but it does have a purpose. If a host belonging to a group of systems is automatically added to the domain, it’d become rather more tedious to actually remove that host from the group simply so you can keep it from joining the AD. We’d see a lot more flak for that than the current method. Using the groups is relatively straight-forward anyway and hope you understand why we can’t have “group” add to domain.
