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

Client install issues - Legacy uninstall

Scheduled Pinned Locked Moved Solved
FOG Problems
8
32
12.3k
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.
  • W
    Wayne Workman
    last edited by Oct 13, 2016, 3:58 AM

    Added to the wiki here:
    https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Legacy_Client_Removal

    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
    • T
      Tim M @Wayne Workman
      last edited by Feb 16, 2017, 4:15 PM

      @Wayne-Workman I am having the same issue. I modified and used your script from the other thread to uninstall the old client and install the new client. It worked fine in most cases. However, when it doesn’t work, it doesn’t install the new client, and I can’t install it manually because the installer keeps detecting the old client even though I can’t find any sign of it anywhere. I looked for the registry key that Tom mentioned, but it isn’t there. Any insight would be great. I am in the process of migrating about 1,000 machines from a server running 0.32 to one running the latest trunk.

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer
        last edited by Joe Schmitt Feb 16, 2017, 10:27 AM Feb 16, 2017, 4:21 PM

        @Tim-M youll need to look under the Wow6432Node for the key mentioned before, assuming your machine is 64 bit.

        If you can wait a day or so, I’m finishing up a snapin that you can deploy to legacy clients, and it’ll auto upgrade them to the new one (assuming everything works properly), or it can be deployed via GPO.

        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.

        T 1 Reply Last reply Feb 16, 2017, 4:32 PM Reply Quote 0
        • T
          Tim M @Joe Schmitt
          last edited by Feb 16, 2017, 4:32 PM

          @Joe-Schmitt That worked. Thank you so much. You guys totally rock! When I first introduced the idea of moving to FOG from a paid imaging platform a few years ago, my boss was concerned about support. I have to tell you that the support that all of you and the community provides is far better than anything I have witnessed from companies that we pay.

          1 Reply Last reply Reply Quote 3
          • J
            jbrabhamMSD
            last edited by Mar 2, 2017, 6:52 PM

            I’m having the same issue. I just updated the server 10 1.3.4 last night. I tried to update the client and it said that I need to uninstall the old version. I uninstalled from add/remove programs. Now it continues to say that I need to uninstall the old version. It is a 64 bit machine that I am working on, so I looked under HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall and HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall but didn’t find {91C5D423-B6AB-4EAB-8F17-2BB3AE162CA1}. I also did a search from the root of the registry for that key.

            1 Reply Last reply Reply Quote 0
            • J
              Joe Schmitt Senior Developer
              last edited by Mar 2, 2017, 7:37 PM

              @jbrabhamMSD to be clear here, you just upgraded from 1.2.0 to 1.3.4? And it was the legacy client installed on the problematic computer and not an old version of the new client?

              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.

              J 1 Reply Last reply Apr 15, 2017, 12:12 AM Reply Quote 0
              • J
                jbrabhamMSD @Joe Schmitt
                last edited by Apr 15, 2017, 12:12 AM

                @Joe-Schmitt Well I feel silly. I’d forgotten that I had posted this and had moved on to new things. And I came back around, looking for the solution again and lo and behold, I see that I had posted the question and there was a reply to it.

                Anyways, yes, we upgraded from 1.2.0 to 1.3.4. We have the legacy client (from 1.2.0) on most of our systems and if I uninstall and try to install the smartinstaller.exe or the new msi, I get the message saying that I need to uninstall the old version.

                1 Reply Last reply Reply Quote 0
                • J
                  Joe Schmitt Senior Developer
                  last edited by Apr 15, 2017, 12:20 AM

                  @jbrabhamMSD I’d need to remote into a problematic machine to identify why the new client still thinks the legacy is present. Send me a PM and we can work out some time that works for both of us sometime next week if it’s alright with you.

                  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.

                  1 Reply Last reply Reply Quote 1
                  • J
                    Joe Schmitt Senior Developer
                    last edited by May 9, 2017, 4:50 PM

                    For anyone still having this issue, you can run this tool as Administrator and it will clean up leftovers from the legacy client (only run after you have uninstalled the legacy client): https://build.jbob.io/Tools/CleanLegacyClient.exe.

                    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.

                    1 Reply Last reply Reply Quote 1
                    • R
                      Rudy Delsaut
                      last edited by Jan 18, 2018, 1:18 PM

                      Hello,

                      have same issue. The CleanLegacyClient.exe doesn’t work.
                      Have you another way?

                      Thank you

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by Jan 18, 2018, 8:14 PM

                        @Rudy-Delsaut We need more information. What exactly “doesn’t work”? Any error messages? Did you uninstall the legacy client first?

                        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

                        R 1 Reply Last reply Jan 19, 2018, 8:13 AM Reply Quote 1
                        • R
                          Rudy Delsaut @Sebastian Roth
                          last edited by Jan 19, 2018, 8:13 AM

                          @sebastian-roth
                          Hello,
                          yes i delete the legacy client first, restart, then use “CleanLegacyClient.exe”, restart, and tried to install Fog Client from 1.3.5 ver. but i receive “please uninstall legacy client first and re-install”.

                          But, i can re-install fog tray version 0.1

                          Thank you !

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by Jan 19, 2018, 4:28 PM

                            @Rudy-Delsaut Did you “run as Administrator” with the cleanup tool?

                            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

                            R 1 Reply Last reply Jan 22, 2018, 7:35 AM Reply Quote 0
                            • R
                              Rudy Delsaut @Sebastian Roth
                              last edited by Jan 22, 2018, 7:35 AM

                              @sebastian-roth

                              Yes

                              1 Reply Last reply Reply Quote 0
                              • J
                                Joe Schmitt Senior Developer @Tom Elliott
                                last edited by Joe Schmitt Jan 22, 2018, 9:53 AM Jan 22, 2018, 3:49 PM

                                @Rudy-Delsaut can you try opening regedit and checking for the leftover legacy client software entry? Sorry for all the trouble, the legacy client was built a long time ago for Windows XP so it has some issues like leftover registry entries. If the machine is 64 bit you should also check under Wow6432Node, keeping the rest of the path the same:

                                @tom-elliott said in Client install issues - Legacy uninstall:

                                Before redoing everything, per @joe-schmitt, the registry is scanned for the presence of a particular GUID for the FOG Legacy Installer.

                                Please Open regedit and look in:
                                HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Remove the key with: {91C5D423-B6AB-4EAB-8F17-2BB3AE162CA1} and try reinstalling, this should work (hopefully).

                                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.

                                R 1 Reply Last reply Jan 23, 2018, 9:03 AM Reply Quote 0
                                • R
                                  Rudy Delsaut @Joe Schmitt
                                  last edited by Jan 23, 2018, 9:03 AM

                                  @joe-schmitt

                                  Hello,

                                  everything is OK. I deleted the regedit path and it’s ok.

                                  Thank you for your reply !!!

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

                                  283

                                  Online

                                  12.0k

                                  Users

                                  17.3k

                                  Topics

                                  155.2k

                                  Posts
                                  Copyright © 2012-2024 FOG Project