Jump to content

Recommended Posts

Posted

Hi guys

 

I have popped a SIMS ticket in already but thought I'd get an edugeek view of this too.

 

Had a mild panic attack yesterday when I got an email from our Solus 3 saying it was deploying the Spring update 2015 for me; how lovely of it! Luckily it failed and didn't deploy but as far as I'm concerned it should not have even downloaded the bloody thing.

 

I have auto download off on the updates tab but auto deploy on for everything else (see screenies) - in my head that would mean that Solus will email me when there are new updates (which it does) but will not download them until I tell it to and therefore will auto deploy them thus controlling the deployment of updates. From what I understand auto deploy needs to be on for the handful of clients that have not been updated yet eg staff who never bring in their laptops.

 

Anybody agree or disagree?

 

Thanks

 

Mark

solus - deployments.PNG

solus - updates.PNG

Posted

For anybody else that experiences this, according to the SIMS helpdesk "auto deploy" overrides auto download. So if you have auto deploy on, even if you have "auto download" unchecked on the update tab, updates will download and auto deploy as they become available.

 

Must be an undocumented feature

  • Thanks 3
Posted (edited)

Agreed - from the settings in your screenshots that's the behaviour I'd expect too.

 

We had a similar issue the other week when solus 3.9 arrived and started deploying itself everywhere, even after switching off auto-deploy and then solus itself.

 

edit- missed your reply. Interesting; that'll go some way to explaining our issue. Thanks for posting the update.

Edited by Chockster
  • Thanks 1
Posted (edited)
From what I understand auto deploy needs to be on for the handful of clients that have not been updated yet eg staff who never bring in their laptops.

 

Auto-Deploy deploys any updates you have in your SOLUS3 as soon as they become available.

 

If an agent for example misses the Spring 2015 release because they were off or not at the school, it will pick it up regardless of the Auto-Deploy setting..

 

The 'SOLUS3SysAdmin' document on Capita My Account explains it much better.

Edited by Atomic_Zombie
  • Thanks 2
Posted

I took the approach years ago now of auto-downloading and setting not to auto-deploy.

 

The concept of auto-download makes some sense to me - I can get in in the morning and solus will have downloaded an update, and PC's will have started to stage the update locally (at least from memory, I think the client will download a future update ready for when it's eventually deployed)

 

The autodownload is quite useful sometimes - got an email from our exchange server today saying solus had downloaded a cheque printing update before I read it on support net.

 

Then manually deploy it when I know no one is logged in. I normally then baby sit it and watch the process until the db is upgraded, and the first pc has upgraded and I can log in, then go home and assume the rest will work.

Posted

Manual deploy ours with Auto download on.

 

This allows us time to get all Staff machines on, update the server and this time around it seems to run smoothly. Previous updates have been a nightmare but so far so good.... touch wood...

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