I'm interested in using Steady state for clone machines we are going to send out to customers.
There could be aproximatley 800 of these over the next year.
One problem I have is where to turn automatic updates on or not.
I'd like to have them on for Security sake. However history has taught us that Automatic Update is far from flawless.
We've had Windows Updates patches which have rendered our SQL Server reports black, others that have made our software
completely inoperable. Other updates don't work at all and get stuck in a repetative loop.
If Steady State were to apply an update which caused one of these kind of issues, is there some easy way of reverting it back again?
Is there also anyway of delaying the updates by a week so we can become aware of the problem before it happens 800 times, and with some extra random time variable
so as to not have to support 800 clients all at once!
My guess is at the moment we're better off without the updates, but I'd like to hear how others do it.
Equally the machines will be standalone with no administrators to speak off so they could become sitting ducks if certain updates are not applied.
Cheers
Chris
