Jump to content

Recommended Posts

Posted (edited)

Latest version of Solus 3 v3.9.0.18 has been released.

 

Upgrade seemed to go OK.

 

Interface speed seems to not have been fixed. It still takes over 3 seconds from when I click on Environment >> Agents to show the list of agents.

Edited by zag
Posted
Is 3 seconds really a big issue?

 

I would say so yes. It frustrates me every time I use the thing. Its simply bad programming and user interface design.

 

Solus 2 was instant.

Posted
Latest version of Solus 3 v3.9.0.18 has been released.

 

Upgrade seemed to go OK.

 

Interface speed seems to not have been fixed. It still takes over 3 seconds from when I click on Environment >> Agents to show the list of agents.

 

I don't suppose you know what version you updated from? We are on 3.8.22.0 and the documentation for 3.9.0.10 says that you need to be on 3.8.53.0 to update - and I don't really want to update twice.

Thanks.

Posted
Solus 2 was instant.

 

If you can get SOLUS2 to tell me about your all your workstations in less then 3 seconds like you claim, then I'll buy you a beer.

  • Thanks 1
Posted
I don't know if its 3.9 update or previous one but I'm happy I can remove more than one computer at a time as it was pain when imaged room of machines then had to remove agents one at a time to then redeploy SOLUS.
Posted
I don't know if its 3.9 update or previous one but I'm happy I can remove more than one computer at a time as it was pain when imaged room of machines then had to remove agents one at a time to then redeploy SOLUS.

 

You put sims on every machine?

Posted (edited)
You put sims on every machine?

 

Only our main computer rooms as they run weekly 30 min SIMS training sessions for staff , we also have it on every teacher machine at front of each room . We image and update every half term via SCCM but never have tried putting SOLUS in the image as thought it had to be deployed by server so machine is registered with server.

 

Just noticed reinstall agent option too this would solve my issue with imaging.

Edited by xenonive
Posted
I don't suppose you know what version you updated from? We are on 3.8.22.0 and the documentation for 3.9.0.10 says that you need to be on 3.8.53.0 to update - and I don't really want to update twice.

Thanks.

 

It turns out that all of our clients were on SOLUS 3.8.53.0, but the SOLUS 3 Console was 3.8.22.0! I took the plunge and rolled out the update to v3.9.0.18 and the Console and all of the clients updated sussessfully - so only the one rollout in the end phew - all seemed to go smoothly.

  • 1 month later...
Posted
Just about to apply this myself, did it kick anyone out of SIMS whilst the update takes place? Does it add the functionality to redeploy solus agent installs when they fail for whatever reason?
Posted

AFAIK SOLUS console/client updates themselves shouldn't kick anyone out of SIMS, but it will roll out the new agent so things may/will flash up on client machines.

 

The best part of the 3.9 update is the added ability to select a downloaded update and Extract it to a location of your choice, to be able to install an update manually.

 

I still have the occasional client that doesn't install - or "Installer Completed Successfully, but the Agent was not Installed"!! I hate that error... Grr.

Installing the agent manually, then uninstalling it and then trying the install through SOLUS console usually sorts this one out though.

Posted (edited)

You have to go to:

 

Upgrades (at the top) > Update Library > Updates (tab) > Update specific update (Highlight) > Extract (Click - button at the bottom, in-between View and Download)

 

Ash

 

Edit:

Sorry, I didn't read that properly - thought you meant the extract for the updates, not the agent.

Edited by sllorep
Posted

Ah well, I should have realised, good old faithful error message "Deployment selection. Critical target(s) missing version information, please check credentials or contact your local support unit."

 

Anyone seen this before, happens to us every time we upgrade SOLUS and usually requires a remote session from capita to fix.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...