[sims] Solus 3.12.59.5 problems

[robjduk]

Morning,

I posted yesterday after I had an awful morning of SIMS updates not working but I've been thinking and the problems started after we installed Solus 3.12.59.5 so wondering if anyone has some tips on troubleshooting it or is aware of if anything changed?

Our latest SIMS update was met but endless "one or more errors occurred" and I struggled to even find logs in the ProgramData to help. I've been playing with permissions on the endpoint's SIMS folder and found changing access to "everyone" seemed to allow it to deploy but it wasn't consistent.

 

All very odd and just wondered if anyone knows a tip.

 

Thanks all.

[Boredguy]

There has been a few issues that occured with SIMS 7.202 from what we've noticed, in that even when it has been deployed via Solus 3 it gives a System.io error when you try and launch/login to SIMS.

 

For the stations we had with the issue, we just used the Solus 3 agent to tell it to check again for updates so it reinstalls SIMS and then it's fine.

We only had this on 3 or 4 stations so it was not a major issue

[FWBD]

We've just upgraded to 7.202 last night and have had a few hiccups too. The few that I've seen were to old name entries on Solus

 

Did a complete removal of the Solus client and re-install resolve it?

[robjduk]

Not really. We ended up copying the content from the SIMS folder on the server over to every workstation and laptop manually. Even testing now I still get "one or more errors has occurred".

 

My SIMS support did play about with it and a few random laptops started updating correctly but its not a sure thing. I've no idea what to do with it.

[FWBD]

What's it like on a device without any SIMS installs on?

[robjduk]

What's it like on a device without any SIMS installs on?

 

It shows SIMS workstation 0.0.0.0 and after checking for updates it claims it will be installed shortly but nothing ever happens.

[Boredguy]

If it just sits on waiting to install, on the workstation stop the Solus 3 Agent service, go to C:\ProgramData\Capita\Solus3\Deployments and delete the contents. Restart the service.

Then within the Agent get it to check for updates and hopefully it should then start to install.

 

Other thing to do is check on your Solus server how many concurrent agent downloads are set and the time they download between (Settings -> Solus 3 -> Deployments) We upped out concurrent deployments to 99 early last year which sped up a lot of our S3 deployments