Jump to content

Recommended Posts

Posted

So what if we're still using SOLUS 2 because SOLUS 3 is rubbish and unsuitable in our environment?

I have to install the .exe patch on 100 PCs manually???

Posted
So what if we're still using SOLUS 2 because SOLUS 3 is rubbish and unsuitable in our environment?

I have to install the .exe patch on 100 PCs manually???

 

I'd imagine so, yes. You've chosen not to use the tool that's provided for deployment of patches...

 

What's unsuitable or rubbish about SOLUS3? Its been nearly flawless for us since we started using it.

Posted

Maybe it's improved since I last tested, but issues were:

- If a PC was offline at the time of update deployed then a user wouldn't be able to login to SIMS (Incompatible Database)

- There was a huge delay between switching a workstation on and it detecting their was an update

 

Overall, users could not use SIMS straight away if the PC was Off, whereas with SOLUS 2, computer boots, user logs in, SIMS update runs, they log in to SIMS.

 

if any time SOLUS 3 doesn't detect the update no users can log In from that workstation as on previous version.

Posted
Maybe it's improved since I last tested, but issues were:

- If a PC was offline at the time of update deployed then a user wouldn't be able to login to SIMS (Incompatible Database)

- There was a huge delay between switching a workstation on and it detecting their was an update

 

If a PC is off, the update is deployed when the machine appears back on the network. The user is prompted that an update is about to be deployed. In my experience, this happens within a couple of minutes of the PC being turned on, so only the fastest of users who turn their PC on and instantly open SIMS will ever see the "Incompatible Database" message. Also, the SOLUS client now allows users to click a button to check for updates, so it should be entirely possible to provide training for staff to go and press that button if they ever see that message.

 

Overall, users could not use SIMS straight away if the PC was Off, whereas with SOLUS 2, computer boots, user logs in, SIMS update runs, they log in to SIMS.

 

You hope. SOLUS 2 updates failed for us (and many others) far too often. Our worst release saw about a 60% failure rate requiring a complete re-install of SIMS.

 

if any time SOLUS 3 doesn't detect the update no users can log In from that workstation as on previous version.

 

See above.

Posted

Only issue we usually have is needing to re-install SIMS for the 3 PCs that use Exams Organiser as it comes up with an Automation Error.

- An error known to Capita but unable to replicate and release a fix for.

 

Such a seamless process rather than messing about with the long winded agent setup.

 

Users take no notice here - I can send out an email saying data will be archived about 2 weeks in advance, then get an email the next day asking me where it's gone after being removed.

Posted
Anyone who has the issue, able to test with FMS and let us know if that too suffers? I'm hoping it's still so rooted in the DOS days, it's not gonna be affected.
Posted
Anyone who has the issue, able to test with FMS and let us know if that too suffers? I'm hoping it's still so rooted in the DOS days, it's not gonna be affected.

 

Will check this am

Posted
Anyone who has the issue, able to test with FMS and let us know if that too suffers? I'm hoping it's still so rooted in the DOS days, it's not gonna be affected.

 

Yes what you said. Fms date picker fine. ....

Posted
patch works, now how to deploy?

 

SOLUS 3 should deploy it - your local SIMS team should release it to you and it will deploy. At least that's the way Somerset have done it.

Posted
I don't have solus 3, I didn't know such a thing existed until this thread! The DCC do the support for SIMS.

 

It should be up to DCC to deploy the update then shouldn't it? I'd be contacting them.

Posted
again just stumbled across this, did the spring upgrade last night, does that include the fix?

No Spring upgrade has the issue (in combination with .net update). Fix is in separate patch.

Posted
Our code hasn't been changed since ~2009 so this is not to do with the spring release!

Ok I'll rephrase, the Spring release does not contain a fix for the issue, its a standalone patch :p

Posted
no silent install on the exe :(

 

Yep, I found that too. You can specify the usual /s switch, but it'll still pop up a message suggesting a restart. I decided to extract the files from solus3, then just use a batch file to deploy the new files to workstations. There'll be some users who won't get updated as the files are in use, but for us at least there aren't that many people that are being affected, so anyone who reports the issue I'll tell them to exit SIMS while I reapply.

 

Meldrew.

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...