[quote=“timcough, post: 11851, member: 40”]I have suggested the following in a different thread to allow a single snapin to be sent to multiple computers:
Add the following lines to the groups section of tasks.advanced.include.php:
<td class=“c”><a href="?node=tasks&type=group&direction=onesnap&noconfirm=<?php print $groupid; ?>"><img src="./images/snap.png" /><p><?php print _(‘Deploy Single Snapin’); ?></p></a></td>
<td><p><?php print _(‘This option allows you to send one of the snapins to the group without imaging the computers. (Requires FOG Service to be installed on client)’); ?></p></td>
Thank you SO MUCH for this code. It has made snap-in deployment much easier. Has anyone figured out a way to make snap-in groups? It would be terrific to be able to put a number of snapins into a group for deployment to certain machines. ie. all 32 bit machines get a certain group of snapins, while 64 bit get a different group, etc.
I can confirm that this doesn’t work on Windows 7 as written. Since I’m unfamiliar with the unix tools, I just destroyed my reference workstation. I managed to work with the 100Mb Win7 boot partition, but destroyed the partition containing the drive… lol
Add the caveat now to Fedora 19, being that they changed the database (mysql) to mariadb. All works, but requires minor changes in the script. I’ve already created a thread pointing out the issue with Fedora 19 and a fixed tarball for it based on FOG 0.33b, though the same changes could just be made in 0.32.