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

    [git 5736] Snap-in installation failes when using sfx files

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    4
    7
    2.5k
    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.
    • B
      Brian David
      last edited by

      All my sfx snap-ins that previously worked will no longer install. These snap-ins are set to execute an installation script after the files have been extracted. FOG successfully downloads the sfx file and runs it, but nothing happens; the installation script never runs and no files are installed. I can see the sfx file in the fog/tmp folder, and I can find the process in Task manager, but it never finishes installing. I have to restart the computer to get the process to clear out of Task manager.

      These sfx files work correctly if they are run manually on the client computers, and FOG had been installing them correctly up until recently (although I couldn’t tell you exactly at what revision they stopped working). So I think it may have something to do with the FOG client. Also, any snap-in that uses a standard exe/msi still works fine.

      1 Reply Last reply Reply Quote 0
      • B
        Brian David
        last edited by

        This also turned out to be due to our anti-virus settings. So let this be a lesson to us all; check your anti-virus first! 🙂

        This can be marked as fixed.

        Wayne WorkmanW H 2 Replies Last reply Reply Quote 1
        • Wayne WorkmanW
          Wayne Workman @Brian David
          last edited by

          @Brian-David Don’t feel bad. I raise false alerts sometimes too. The important thing is that you come back here and own up to it. Again, I’ve done this a few times.

          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!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          1 Reply Last reply Reply Quote 0
          • H
            Hanz @Brian David
            last edited by

            @Brian-David What was it exactly that was stopping the sfx, but not regular exe 's

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

              @Hanz the best guess I can give is the way sfx files are created. Exes request the permission as needed but snapins run from the system account. So because the sfx was running to get an elevated account even though it was already running as an elevated account the antivirus was blocking the snapin to prevent unauthorized access. I hope that makes sense.

              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
              • B
                Brian David @Hanz
                last edited by

                @Hanz To be honest, I couldn’t tell you. In the past, Avast has let these snap-ins run after an initial ‘deep-scan’. At this point, it just seem so be cutting them off without any sort of warning or indication. I’ve had to set an exclusion for the FOG directory on all our workstations in order to guarantee that the snap-ins run. There have been some recent updates to Avast, so perhaps the way it treats these files has changed.

                Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                • Wayne WorkmanW
                  Wayne Workman @Brian David
                  last edited by

                  @Brian-David we have Avast enterprise deployed at work. Although I’ve not been able to test the new client with it yet - I’m having issues just uploading a snapin: https://forums.fogproject.org/topic/6339/failed-to-add-snapin-unable-to-locate-snapin-directory

                  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!
                  Daily Clean Installation Results:
                  https://fogtesting.fogproject.us/
                  FOG Reporting:
                  https://fog-external-reporting-results.fogproject.us/

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

                  233

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project