<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[FOG 1.6 – Dependencies between Software Management and Snapins?]]></title><description><![CDATA[<p dir="auto">Hi.</p>
<p dir="auto">I’m using FOG 1.6 with the new FOG Agent and both the Software Management (Chocolatey) and Snapin modules.</p>
<p dir="auto">My problem is that there doesn’t seem to be a shared execution order or dependency system between Software and Snapins.</p>
<p dir="auto">Example:</p>
<p dir="auto">Software Management installs several applications via Chocolatey.</p>
<p dir="auto">Snapins perform additional configurations.</p>
<p dir="auto">My final Snapin runs Sysprep and shuts down Windows for image capture.</p>
<p dir="auto">Unfortunately, the Sysprep Snapin sometimes runs before all software packages have finished installing, resulting in an incomplete image.</p>
<p dir="auto">My question:</p>
<p dir="auto">Is there a way to make a Snapin wait until all assigned software packages and other Snapins have successfully completed?</p>
<p dir="auto">Ideally, I would like to configure dependencies across both modules or ensure Sysprep always runs last.</p>
<p dir="auto">Thanks!</p>
]]></description><link>http://forums.fogproject.org/topic/18322/fog-1-6-dependencies-between-software-management-and-snapins</link><generator>RSS for Node</generator><lastBuildDate>Thu, 19 Nov 2026 15:32:22 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/18322.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 19 Nov 2026 14:15:43 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to FOG 1.6 – Dependencies between Software Management and Snapins? on Thu, 19 Nov 2026 15:09:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/49787">@Yuuki</a> FOG Agent <strong>v0.1.26</strong> is released. It always runs software before snapins, whatever FOG server version you have. So your Sysprep snapin no longer starts before Chocolatey has finished.</p>
<p dir="auto">Agents update themselves when <strong>FOG Configuration → FOG Agent → update mode</strong> is <strong>Latest</strong>, which is the default from 1.6.0.158. Updates go out in rings (default <code>0,3,7</code> days), and a host with no ring uses the last one. So your PCs pick up v0.1.26 on their own within about a week.</p>
<p dir="auto">To get it on your build machines now, do one of these on each host:</p>
<ul>
<li>Set <strong>Agent Update Ring</strong> to <code>0</code>.</li>
<li>Or set <strong>Desired Agent Version</strong> to <code>0.1.26</code>.</li>
</ul>
<p dir="auto">If the update mode shows <strong>Off</strong>, set it to <strong>Latest</strong>, or use the per-host Desired Agent Version above.</p>
<p dir="auto">The server half, the <strong>Stop snapins if this fails</strong> option on a software entry, is going into dev-branch now. It reaches stable with the next monthly release, on December 11. Until then, the agent gives you the right order, but a failed package does not hold the snapins. So check the host’s <strong>Software Status</strong> tab before you capture.</p>
]]></description><link>http://forums.fogproject.org/post/159095</link><guid isPermaLink="true">http://forums.fogproject.org/post/159095</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Thu, 19 Nov 2026 15:09:44 GMT</pubDate></item><item><title><![CDATA[Reply to FOG 1.6 – Dependencies between Software Management and Snapins? on Thu, 19 Nov 2026 14:56:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/49787">@Yuuki</a> You found a real ordering problem. The FOG Agent runs its modules one at a time, in the order the server sends them, and on 1.6 that order puts snapins before software. So on any check-in that carries both, your Sysprep snapin runs before Chocolatey starts.</p>
<p dir="auto">The fix is in progress:</p>
<ul>
<li>Software will always run before snapins. This is fixed in both the server and the agent, so updating either one gets you the order.</li>
<li>Each software entry gets a new option, <strong>Stop snapins if this fails</strong> (off by default). With it on, a failed install holds the host’s snapins. At the next check-in the agent tries the software again, and it runs the snapins only after the install succeeds.</li>
<li>Snapins already have <strong>Abort snapin sequence on failure</strong> on the snapin task. Turn it on when you queue the snapins, so Sysprep does not run after a failed configuration snapin.</li>
</ul>
<p dir="auto">Until the fix reaches you, there are two workarounds:</p>
<ul>
<li>Assign the software first. Wait until the host’s <strong>Software Status</strong> tab shows every entry as <code>installed</code> or <code>converged</code>. Then queue the snapins.</li>
<li>Or install those packages with the Chocolatey snapin templates instead of Software Management. Snapins run in their queue order, so put Sysprep last.</li>
</ul>
<p dir="auto">I will post here when it is in a release.</p>
]]></description><link>http://forums.fogproject.org/post/159094</link><guid isPermaLink="true">http://forums.fogproject.org/post/159094</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Thu, 19 Nov 2026 14:56:18 GMT</pubDate></item></channel></rss>