SOLUS3 February Release (3.4.107) - Now Available
Resource ID: 18940
Just to repeat Mr Wood's message, if your on 3.4.103, apply the upgrade. Only the SOLUS3 DS will upgrade to 3.4.107, the agents will stay on .103, however any agents not on .103 will be upgraded to .103. Vital any LA upgrade as the authorisation panel is much, much better.Hi,
I have just authorised an update to SOLUS3 to improve the reliability of the agent heartbeat functionality in advance of the SIMS Spring release.
We would strongly recommend that all SOLUS3 customers take this update before taking the SIMS Spring release in order to resolve issues where SIMS/FMS upgrades were not being initialised on target machines.
This update consists of an update to the Deployment Service and Deployment Server User Interface only and will be updated to version 3.4.107 There are no updates to the SOLUS3 Agents and they will remain at (or upgrade to when the agents are back online if that update is pending) version 3.4.103.
This update of SOLUS³ improves the reliability of the agent heartbeat functionality that was introduced with the SOLUS³ November 2011 release (SOLUS³ 3.4.103). The following improvements are included in this release:
· SOLUS³ Agents with a version prior to 3.4.103 are handled correctly by the Deployment Service, enabling deployments to these devices, including the 3.4.103 agent upgrade.
· Enhanced agent heartbeat processing, where a device had multiple database targets of the same type (e.g. FMS database).
Full details on the new release and its enhancements can be found in the release note (resource Id 18936 in SupportNet).
Existing SOLUS3 customers
The release is now available for you to download and apply in SOLUS3 onto a SOLUS 3.4.103 system only as
SOLUS3 – 184.108.40.206 – Agent Heartbeat Fix
Sites not yet on 3.4.103 should upgrade to this version first by applying the release called ‘Solus3 – 3.4.103’ before upgrading the Deployment server to the new version as above.
Just as a quick note - if an agent has been installed since you last did the Solus 3.4.103 upgrade (I had 2 which the machines I'd reinstalled) then Solus will redeploy the 3.4.103 upgrade to them for some reason because it thinks they haven't met the dependancy (even though Solus obvious installs 3.4.103 when you deploy it to the workstations through the DeploymentUI)
This update seems to have resolved the issues we were experiencing. We've done some testing with it and so far, so good. How is everyone else getting on with it?
Just two schools with problems with "it". I say "it" as it's most likely nothing to do with the upgrade. But yes, seems ok, if you've got .64 or below agents, make sure you click the check agent status button for them before you start (and turn off heartbeat).
What problems were you having prior to the update that you state have now been resolved?
I am having problems with my sites and I am trying to gather as much information as possible.
There are currently 1 users browsing this thread. (0 members and 1 guests)