Wiki re: How to uninstall the Legacy FOG Client (FOG Project Service 3.0.29) from Windows

[sudburr]

Server

• FOG Version: n/a
• OS: n/a

Client

• Service Version: FOG Project Service 3.0.29
• OS: any Windows

Description

I know it’s discussed here in the forums, but I found the Wiki (FOG Client) is missing this information.

I used the following for a silent, non-interactive removal:

msiexec.exe /x {91C5D423-B6AB-4EAB-8F17-2BB3AE162CA1} /quiet

Buuuuut, there is more fun to this story.

The “FOG Project Service 3.0.29” was installed to Windows while the image was built in Audit mode. I could not uninstall using the above command until I invoked it from a CMD prompt run as Administrator. Running it as a scheduled task using account “NT Authority\SYSTEM” would not remove it.

Hopefully a .vbs with Self-Elevation will work because I have 8000+ systems to upgrade.

[george1421]

Warning a bit off point: Consider the free version of PDQ Deploy to run this MSI. The paid for version is great, but for this task the free version will work perfectly as long as you have an domain account with local admin rights.

[sudburr]

Even logged into the machine using an account that is a member of the Local\Administrators group isn’t enough to uninstall the legacy client.

Deployment of a program I don’t have a problem with… just this removal.

[george1421]

@sudburr I agree, PDQ Deploy handles the process elevation for you. There are many reasons for using PDQ Deploy but one is that you can use a domain OU as a target list and then PDQ Deploy will track which systems deployed correctly (uninstalled in your case) and which ones didn’t. Believe me its worth your time to set it up and try it. There is no cost other than about 1 hr of your time to install, watch 1 or 2 youtube videos, and create your first package.

[Joe Schmitt]

@sudburr If you’re crazy you can also use the legacy client to upgrade to the new client. Basically you’d make a snapin that immediatly backgrounds another script and exits, so the snapin is “completed” but your backgrounded batch script is actually performing the upgrade process.

[Wayne Workman]

@sudburr Not a guarantee, but you might try scripting the uninstall using the old fog client msi instead of the product ID.