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

FOG Client Service Updater

Scheduled Pinned Locked Moved
Windows Problems
3
9
3.4k
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.
  • J
    Joe Gill
    last edited by Aug 30, 2016, 5:41 PM

    @Wayne-Workman

    FOG Client Tray Ver 0.1
    Released Under GPL Version 3

    Will this client automatically update to current if the MSI is uploaded to client service updater on the server?

    If so, how long does it take to update on the clients?

    I’m assuming this is the easiest solution to updating our legacy clients short of uninstalling and re-installing clients on each host.

    Thanks!

    Cheers!

    Joe

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Aug 30, 2016, 5:50 PM

      What? lol.
      Can you explain what you’re doing?

      The fog client on 1.3 RC automatically updates. Legacy clients will not auto-update to the new fog client. The best solution is to use a startup script via group policy - and use an msiexec command to uninstall the old legacy client by it’s GUID, and another line to install the new fog client from a network share.

      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/

      J 1 Reply Last reply Aug 30, 2016, 5:53 PM Reply Quote 0
      • J
        Joe Gill @Wayne Workman
        last edited by Aug 30, 2016, 5:53 PM

        @Wayne-Workman I have a lab that was having issues receiving pushed printers. I figured it was an issue with the Client. I was going to update the client up to current. So that’s where I"m at.

        1 Reply Last reply Reply Quote 0
        • W
          Wayne Workman
          last edited by Aug 30, 2016, 5:55 PM

          Do it via imaging, or via policy.

          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/

          J 1 Reply Last reply Aug 30, 2016, 5:56 PM Reply Quote 0
          • J
            Joe Gill @Wayne Workman
            last edited by Aug 30, 2016, 5:56 PM

            @Wayne-Workman I’m seeing that. LOL! Too bad my hands are still tied for doing GPO work… My colleague is too scared to mess with it and won’t give me privileges. I love my job. LOL!

            Looks like installing them the old fashioned way is what I’ll have to do.

            J 1 Reply Last reply Aug 30, 2016, 5:57 PM Reply Quote 0
            • J
              Joe Gill @Joe Gill
              last edited by Aug 30, 2016, 5:57 PM

              And I don’t have time to re-image!

              G 1 Reply Last reply Aug 30, 2016, 6:45 PM Reply Quote 0
              • G
                george1421 Moderator @Joe Gill
                last edited by Aug 30, 2016, 6:45 PM

                @Joe-Gill You can push out the client (or any msi or exe with an unattended installer) with PDQ Deploy. The free version will work for you. All that is required is the MSI and having/knowing the an account on the target computer that has admin rights. It will take you about 30 minutes to setup pdq deploy and create and deploy your first package. Its not a real big time sync. You can deploy to each machine you define, by machine OU or a custom list you can create. Its pretty flexible.

                I do have to say the paid for version is well worth the cost. With the paid for version you can download already created packages for common software as well as create multi step intelligent install scripts (ie switch installers based on target system bits x86 vs x64).

                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!

                1 Reply Last reply Reply Quote 1
                • W
                  Wayne Workman
                  last edited by Aug 30, 2016, 6:50 PM

                  If you go the PDQ route, be sure to include some way to first remove the legacy client. If it’s still there, the new client will not install.

                  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/

                  G 1 Reply Last reply Aug 30, 2016, 6:56 PM Reply Quote 0
                  • G
                    george1421 Moderator @Wayne Workman
                    last edited by Aug 30, 2016, 6:56 PM

                    @Wayne-Workman said in FOG Client Service Updater:

                    If you go the PDQ route, be sure to include some way to first remove the legacy client. If it’s still there, the new client will not install.

                    Following Wayne’s instructions then you should create a batch script and deploy that with PDQ Deploy.

                    In that batch script you will issue the FOG client uninstall command

                    @echo off
                    msiexe /X <guid of fog client>
                    
                    REM then install the new FOG client with 
                    msiexec /i fogclient.msi <what ever option switches>
                    

                    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!

                    1 Reply Last reply Reply Quote 1
                    • 1 / 1
                    1 / 1
                    • First post
                      8/9
                      Last post

                    157

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project