Fog Client - 0.10.3 issues after update on host from previous version.

[Joe Schmitt]

Thanks for checking. Whats happening is because of the pre 0.10.3 MSI issues, your FOG server is becoming unpinned during upgrade.
If you have pdq deploy or GPO you can either re-deploy the client or manually pin the server (harder).

[RipAU]

@Jbob

We don’t actually have access to the deployment via GPO as that is controlled by externally but we can install what we need manually or via login scripts.
So just re-reinstalling with the MSI over top the existing install should fix this?

e.g.

FOGService.msi" /quiet USETRAY="1" HTTPS="0" WEBADDRESS="fog2" WEBROOT="/fog" ROOTLOG="1"

Thanks

[Joe Schmitt]

Unfortunately no. You’d need to do an msiexec /x .....(uninstall), then install it, and either restart or do a net start FOGService

[RipAU]

@Jbob

No worries, I’ll have a check on how I can do this easily

Thanks again.
Cheers.

[Joe Schmitt]

I have confirmed and isolated the source of this issue. It will only affect 0.10.0 to 0.10.2 auto upgrades. 0.10.3 will operate normally when auto updating in the future. Sorry about the oversight.

[Joe Schmitt]

If you can wait until Tom gets around to pushing 0.10.4, it should auto repair all of hosts when you upgrade. (Keyword being should. It depends how damaged the 0.10.3 install is)

We designed the auto update system to be completely independent of server authentication in 0.10.X for scenarios just like this. Even though the client won’t take commands from your server, it will still process FOG Project update requests.

[RipAU]

@Jbob Awesome.

Thanks, Happy to wait and test it out

[Joe Schmitt]

@RipAU v0.10.5 is released. As long as your “broken” clients still have our FOG Project certificate installed, they should repair themselves. If they do not, you can simply run the v0.10.5 msi via a script and it will manually upgrade the broken installation that is running (you’ll still want to either restart or manually start the service when done). No need to first uninstall v0.10.3 now.

[RipAU]

@Jbob

Perfect I’ll update the server and test

Thanks for the quick response guys.

[RipAU]

Yep, looks like the problem clients have updated themselves. All working it seems.

Cheers.