Remove legacy client and install 0.9.5 client

[johnomaz]

Had anyone found a way to issue a command to remove the old legacy client and install the new client? using the msiexec commands have proven unsuccessful to remove the old legacy client. I edited the new client’s msi file to put my servers IP address in and it looks like it’ll deploy out via AD just fine but removing the legacy client is the issue. I have 1000+ computers with it and manual removal looks to be a long process.

Nevermind, I had a brainfart moment and forgot I can just use the Product ID. msiexec /x {91C5D423-B6AB-4EAB-8F17-2BB3AE162CA1} if anyone happens to be looking for this info too.

if exist "C:\Program Files (x86)\FOG\Handlers.dll" goto end
if exist "C:\Program Files\FOG\Handlers.dll" goto end
goto update
:update
msiexec /x {91C5D423-B6AB-4EAB-8F17-2BB3AE162CA1} /quiet /passive
\\pathtomsi\FOGService.msi /qn /passive
net stop fogservice
net start fogservice
:end

I’m sure there is a more elegant way of doing it, but this works.

[Scott B]

That works great, but how do you tell the new client your FOG’s address or is that some kind of magic with the new client, not necessary?

[johnomaz]

I used Orca to edit the MSI and change fog-server to my server’s IP address.

That screen shot is the place where you can edit the MSI file and add your own IP address in.
https://imgur.com/EYPkqsj

[Wayne Workman]

I’m currently testing out the new client on just my workstation right now at work.

Here soon I’ll be removing all the old clients and pushing out the new one. I’ll update this thread when I get to that.

[johnomaz]

So far the removal has been very smooth. I’ve checked about 60 or so workstations in two computer labs and they have all done it just fine. Printers have also reappeared.

[Wayne Workman]

@johnomaz I was planning on doing something similar to what you did, and my plan always involves using msiexec and product codes

[Joe Schmitt]

@johnomaz , a couple quick notes:

1. Handlers.dll will not exist in newer version of the client, FOGService.exe is the safest file to check for.
2. Any setting you see in the MSI can be set via CLI arguments. For example, to set the server address, just append WEBADDRESS=“x.x.x” to the install command.

[johnomaz]

@Jbob I used Handlers.dll because it doesn’t exist with the legacy client install. If in the next version of the client it doesn’t exist, I’ll change the argument to look for a different file. FOGService.exe exists for all versions so it would never uninstall if it found the file on the legacy install.

[Joe Schmitt]

@johnomaz ,the next version should automatically remove the legacy client:
https://github.com/FOGProject/fog-client/issues/31

[Scott B]

@Jbob said:

@johnomaz ,the next version should automatically remove the legacy client:
https://github.com/FOGProject/fog-client/issues/31

Do you mean the next SVN or the next version of the client (0.9.6?).

[Joe Schmitt]

Version of the client.

[d4rk3]

1. Open a command prompt as Administrator.
2. Type wmic and hit enter.
3. /node:“Computer-01”,“Computer-02”,“Computer-03” /user:domain\user /password:password product where name=“FOG Service” call uninstall /nointeractive
4. From there you can deploy the new client

[Wayne Workman]

@d4rk3 While a valid solution, it’s not all that easy to accomplish when you have 500 to 6,000 hosts…

[d4rk3]

@Wayne-Workman Other than waiting for v0.9.6/re-imaging are there any easy ways to accomplish this on a large amount of hosts?

[Joe Schmitt]

@d4rk3 Snapins. If you are smart about forking processes you could use a snapin to upgrade the client.

[Wayne Workman]

@d4rk3 Or if your clients are bound to Active Directory, you can use a simple startup script similar to what is in the first post.

[d4rk3]

I’ve already upgraded all of my clients, I was just genuinely curious to know if any easier methods existed