[sims] SOLUS 3 Reports

[RiffRaff]

I want a report that shows me the current status of all our SIMS clients - i.e. what version of SIMS they are at - 7.142 / 7.144 etc.

When I run the report it is showing some clients still at 7.142 even though I know for a fact they have been updated to 7.144. How do I force the report to update itself to show the clients at the correct version?

I have tried running it again after leaving it over night to see if that made a difference - it didn't.

Cheers

[matt40k]

If you go into SOLUS3 Agents, then select the computer that hasn't updated then click on View agent details - does this report the correct version?

[RiffRaff]

No, it is showing as 7.142 when the laptop is actually at 7.144

[matt40k]

Did SOLUS3 actually upgrade it, or did it fail then you upgraded it manually?

[RiffRaff]

I sent the upgrade via SOLUS, it's not a major issue, I just want a report that accurately shows me what versions of SIMS all my clients are so that I can get the rest of them updated. I am having to Redeploy as they don't seem to be upgrading automatically (not all of them anyway)

Cheers

[Stuart_C]

I've been there and done that.

 

My offical response from capita is to uninstall the agent and re-install it. At which point it will sort the reporting issue.

 

(yes I know that's at best teniously unhelpfull) I wait to see what happens with the next upgrade to spring.

[wpjon]

We have seen this, it seems to happen to us when a sims deployment through solus3 ends with a status of 'partially successful' and solus doesn't seem to update the version number of the clients which have updated successfully. Redeploying sims to the clients which solus reports the wrong version for sorts it for us (so long as the deployment finishes with a status of successful).

[Wayne_K]

That's very interesting as I rarely get a SIMS deployment that finishes successfully.

 

They always end up Partially successful due to other machines been turned off.

 

I gave up on the reports and use some VBS scripts that run at logon to log the version of Pulsar, FMS, Discover Executables to a CSV file.

 

Hopefully in next release this will be resolved.