FOG Client Service Updater

[Joe Gill]

@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

[Wayne Workman]

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.

[Joe Gill]

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

[Wayne Workman]

Do it via imaging, or via policy.

[Joe Gill]

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

[Joe Gill]

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

[george1421]

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

[Wayne Workman]

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.

[george1421]

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