• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    FOG 1.6 – Dependencies between Software Management and Snapins?

    Scheduled Pinned Locked Moved Unsolved FOG Problems
    3 Posts 2 Posters 7 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Y
      Yuuki
      last edited by

      Hi.

      I’m using FOG 1.6 with the new FOG Agent and both the Software Management (Chocolatey) and Snapin modules.

      My problem is that there doesn’t seem to be a shared execution order or dependency system between Software and Snapins.

      Example:

      Software Management installs several applications via Chocolatey.

      Snapins perform additional configurations.

      My final Snapin runs Sysprep and shuts down Windows for image capture.

      Unfortunately, the Sysprep Snapin sometimes runs before all software packages have finished installing, resulting in an incomplete image.

      My question:

      Is there a way to make a Snapin wait until all assigned software packages and other Snapins have successfully completed?

      Ideally, I would like to configure dependencies across both modules or ensure Sysprep always runs last.

      Thanks!

      Tom ElliottT 2 Replies Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @Yuuki
        last edited by

        @Yuuki 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.

        The fix is in progress:

        • Software will always run before snapins. This is fixed in both the server and the agent, so updating either one gets you the order.
        • Each software entry gets a new option, Stop snapins if this fails (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.
        • Snapins already have Abort snapin sequence on failure on the snapin task. Turn it on when you queue the snapins, so Sysprep does not run after a failed configuration snapin.

        Until the fix reaches you, there are two workarounds:

        • Assign the software first. Wait until the host’s Software Status tab shows every entry as installed or converged. Then queue the snapins.
        • Or install those packages with the Chocolatey snapin templates instead of Software Management. Snapins run in their queue order, so put Sysprep last.

        I will post here when it is in a release.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott @Yuuki
          last edited by

          @Yuuki FOG Agent v0.1.26 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.

          Agents update themselves when FOG Configuration → FOG Agent → update mode is Latest, which is the default from 1.6.0.158. Updates go out in rings (default 0,3,7 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.

          To get it on your build machines now, do one of these on each host:

          • Set Agent Update Ring to 0.
          • Or set Desired Agent Version to 0.1.26.

          If the update mode shows Off, set it to Latest, or use the per-host Desired Agent Version above.

          The server half, the Stop snapins if this fails 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 Software Status tab before you capture.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          51

          Online

          12.8k

          Users

          17.7k

          Topics

          157.5k

          Posts
          Copyright © 2012-2026 FOG Project