Updating fog client
-
@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!
