Plugin Persistent Group add new snapin
im using the ‘persistent group plugin’ in fog version 1.5.9 dev branch, and its working like a charm!
My little question is:
If i add a new snapin in my TemplateHost, the members of the group are not updated with the new snapin.
this work if i move out the members of the group and add again.
this is now a ptoblem because i have more than 20 machines in my group and he grow up every month. i miss something ?
best regards yannick
@george1421 Thanks Guyz !!
Ok, thanks for responses, rolduz youre right, in fact i can change my W10 key like say george in my fake machine, those are installed with hte last key are upto date dant need to be reinstalled in fact. All new machine ad in group take the new key. so its fine. i have found a trick for dont have to touch my snapins. i made a snapin group Base with the very best of essential. and made some extra group for office soft with licences, opensource, special group for researcher equip etc… i have tested with a machine and she take 2 group with differents snapins in each group if that works i think there is no problem to add a machine to 4 groups.
this is solved my worry.
thanks and keept this module a live !! its so usefull !!
george1421 Moderator last edited by
@rodluz is correct. The persistent group plugin only fires when a new host is added. This was created as a hack (by me) because the groups in FOG work a bit differently than one might think.
When we are talking about the native group function in FOG, think about it as a set group not a persistent group like you might find in Active directory.
@yannickF If you have hosts you want to update after they have been created previously then use FOG’s built in Group function. This will then set a group of hosts with the new value you want to define. For example, lets say you want to update the windows license key for 100 hosts that you created last year. This is where you would use the FOG built in Group (set) function.
If you want to change the windows license key for every newly created host then you would use the persistent host function. The database triggers is used this way to allow the FOG Admin to reset values of persistent group created hosts otherwise the values would always be reset back to what the template host had, limiting the function (IMO) of FOG to create one off host settings.
@yannickF I may be wrong, but the Persistent Group plugin runs the SQL trigger only when a host gets added to the group. That means that the behavior you are seeing is normal.