Client install issues - Legacy uninstall

[Tom Elliott]

@kman1232 what if you reinstall the old and then uninstall from programs?

[Wayne Workman]

@Tom-Elliott said in Client install issues - Legacy uninstall:

@kman1232 what if you reinstall the old and then uninstall from programs?

This is how I do it.

[kman1232]

@Tom-Elliott Unfortunately same result. I even tried running CCleaner.

[kman1232]

@kman1232 I should mention this image was upgraded to Windows 10 from a Windows 7 install. Now on the Windows 7 install and image the uninstall of the old client and install of the new client when perfect. I think I’m going to just re-install the Windows 7 image and uninstall the old client and install the new client and then upgrade to Windows 10.

[Wayne Workman]

@kman1232 wow that’s a lot to do… why not build Win10 from scratch?

[kman1232]

@Wayne-Workman I am building a clean image as well. This image has a lot of individually installed software applications that I’d like not to have to re-install but if it’s the only option then it must be done. Everything else was working perfectly fine on the upgrade, except uninstalling the old Fog and installing the new version.

[Tom Elliott]

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).

[kman1232]

@Tom-Elliott That worked!!! Awesome!! You saved me a lot of time. Thanks

[Wayne Workman]

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

wiki worthy

[Wayne Workman]

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

[Tim M]

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

[Joe Schmitt]

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

[Tim M]

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

[jbrabhamMSD]

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.

[Joe Schmitt]

@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?

[jbrabhamMSD]

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

[Joe Schmitt]

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

[Joe Schmitt]

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.

[Rudy Delsaut]

Hello,

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

Thank you

[Sebastian Roth]

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