Snapin group
-
FOG 1.5.9
Hello, i’ve got a litle problem with group and snapins.
When i assign a snapin to a group if i look again on this group the snapin i just assigned before is not selected.
Am’i wrong with this way to do ?
Thanks for your help -
@plegrand Groups do not track what snapins are associated to them. It’s just too complex to get right and extremely error prone. Even the things that do track it’s extremely tedious.
Why you ask?
Well, let’s just use some medium numbers to show what I mean.
Let’s say you have a group with 500 hosts in it.
You originally setup the group so all hosts had the same snapins. (Easy to do, just update the group accordingly.)
Now you go to one of the hosts directly, and you remove the snapin from that host. Now you go back to the group, and the group now doesn’t know anything about the snapin on all 500 hosts.
Remember, groups in FOG are not a persistent thing. This is because you can associate a host to multiple groups. Groups, in FOG case, is basically a mechanism to mass update hosts.
For example:
One group to set machines up for specific snapins, but another group that you want to set machines printers, (the machine sets are different, but you might want to cross machiens.)
-
thanks Tom for the explanation.
We just ran into this issue too, and were confused about Fog not storing the change even after reporting “group updated” after <Add selected snapins>.In our case, we wanted to make sure that a plugin is sent to a newly deployed host of a specific image. As the image cannot be associated with a snapin, we consequently tried the group assigment.
So at least, my suggestion would be to make that choice unavailable, to enhance usability.
tx & regards, Thomas -
@snmdla I don’t know what you mean, make it unavailable?
You mean you’re suggesting not being able to use groups to set all the hosts in the group with a specific set of snapins?
-
@Tom-Elliott
yes, it appears to have no effect, as no plugin task is created as far as I have seen.
Please correct me if I’m wrong. -
@snmdla said in Snapin group:
@Tom-Elliott
yes, it appears to have no effect, as no plugin task is created as far as I have seen.
Please correct me if I’m wrong.ah, I think I now understood. The dialogue will associate all group members with the snapin, which will only be fired when, for the individual client “All Snapins” task will be run.
So, to correct my usability suggestion, it would have helped to read “all group members updated” instead of “group updated”.
