Updating fog client
-
Hi.
Two things to note, as far as I know FOG client version and FOG server version are kind of tied together (aka if you want to update client, you should update your server). The client ships with the server software (so if you want a newer client you will need to update)
If the option for automatic FOG service update is enabled, it should be enough to update FOG to the newest version (FOG 1.3 RC10).
-
Thanks for your help @Quazz .
I’ve updated server version to 1.3 RC10, but now fog client log file outputs:RSA FOG Project cert foud
RSA ERROR: Certificate validation failed
RSA ERROR: Trust chain did not complete…
ClientUpdater ERROR: Update file is not authenticShould I reset client encription data ? I have hundreds of clients
-
@Frank It doesn’t hurt to try that. Btw, you can reset encryption data for entire groups, so you can do all of them at once
-
@Quazz Same error in ClientUpdater.
What can it be? could it be corrupted client install file? -
@Frank Try updating manually (click on FOG Client in the Web UI at the bottom) one on computer. If it works, we know the problem lies elsewhere.
-
@Quazz Yes, it works manually. I’ve user FOGService.msi to update
It seem something related to an invalid CA. I did an update to Fog 1.3 RC10, not a clean installation. May be some file was not updated as needed.
-
@Frank Does it still give an error in the log on the new version?
-
@Frank If you just went to RC-10, you might notice the snapins still not running due to the hash value not existing. This is fixed in RC-11, but not sure when that is set to be released. Also if you updated to RC-10, I do not believe client 9.2 will work at all. The last couple release prior to RC’s coming out, you HAD to be on the 11.2 version of the client I think it was in order for everything to work happily together.
Just my experience.
-
@Quazz No, now in ClientUpater client log file section it just shows client version, client os, client-info server version and a success message.
-
@Frank
RSA ERROR: Trust chain did not complete…indicates something with either the signature or pinned certificate is wrong. For now you can disable the fog client auto update setting (it’s a global one). That’ll cut down your bandwidth until we can figure out what’s going wrong. -
@Joe-Schmitt Thanks. I did it. Cpu is still high anyway. Would it be recommended migrate clients to last version using a snapin?
-
@Frank said in Updating fog client:
@Joe-Schmitt Thanks. I did it. Cpu is still high anyway. Would it be recommended migrate clients to last version using a snapin?
No. And when you disable client updating - it’s not immediate. It’ll take the length of your FOG Client checkin time + 60 seconds at most, assuming all defaults this would be 2 minutes.
-
The issue has been found and a patch is being worked on. The patch will not require any additional work to be done on your side, just a simple server update once ready.
-
Cross-linking similar threads and moved to bug reports.
https://forums.fogproject.org/topic/8636/fog-client-is-not-updating
https://forums.fogproject.org/topic/8561/rc10-broken-items-on-upgrade
https://forums.fogproject.org/topic/8556/gui-not-responsive
https://forums.fogproject.org/topic/8616/updating-fog-client -
-
@Joe-Schmitt works perfect!
Thanks!
