Remove legacy client and install 0.9.5 client
-
@johnomaz I was planning on doing something similar to what you did, and my plan always involves using msiexec and product codes
-
@johnomaz , a couple quick notes:
- Handlers.dll will not exist in newer version of the client, FOGService.exe is the safest file to check for.
- 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.
-
@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.
-
@johnomaz ,the next version should automatically remove the legacy client:
https://github.com/FOGProject/fog-client/issues/31 -
@Jbob said:
@johnomaz ,the next version should automatically remove the legacy client:
https://github.com/FOGProject/fog-client/issues/31Do you mean the next SVN or the next version of the client (0.9.6?).
-
Version of the client.
-
- Open a command prompt as Administrator.
- Type wmic and hit enter.
- /node:“Computer-01”,“Computer-02”,“Computer-03” /user:domain\user /password:password product where name=“FOG Service” call uninstall /nointeractive
- From there you can deploy the new client
-
@d4rk3 While a valid solution, it’s not all that easy to accomplish when you have 500 to 6,000 hosts…
-
@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?
-
@d4rk3 Snapins. If you are smart about forking processes you could use a snapin to upgrade the client.
-
@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.
-
I’ve already upgraded all of my clients, I was just genuinely curious to know if any easier methods existed