yeah so I'm not the master of large scale IT, but I do test my code on the h/w it's going to run on before I publish it. I'm not saying it's simple to do so given how many different configurations might be deployed. That's why I'm not the master of IT to tell you how to do that. But the principle is I think the same.
Add in the part about convincing the company to buy every third-party security software suite who's sales guy takes you out to lunch. You should see an average business computer now, there's a stack of random security software, none of which that place nice with anything.
Automate. The word you are looking for is automate.
You absolute want some measure of manual control over your update process because sometimes updates brick things and blindly trusting that an update won't is a good way to get yourself into trouble. There's a reason IT departments employ some degree of change management.
When it comes to servers and security, you want to update as soon as possible. If updates are frequent, there's no reason not to automatize it.
There is at least one reason to not automatize updating and it just happened.
I disagree. in a business environment, you should be testing updates before you deploy company-wide, and this crowdstrike fiasco is a good reason why.
It's all fun and games until the update somehow manages to break all of the network printer configurations.
...and don't get me started on the stupid shit they "fix" while a certain network glitch seems to climb from one major version to the next...
yeah so I'm not the master of large scale IT, but I do test my code on the h/w it's going to run on before I publish it. I'm not saying it's simple to do so given how many different configurations might be deployed. That's why I'm not the master of IT to tell you how to do that. But the principle is I think the same.
You want to update by choice as soon as possible.
Auto-updating without consent creates downstream disasters, even security vulnerabilities. If I don't see release notes, I ain't updating.
Sure, except for the giant clusterfuck we’re talking about that happened just a couple days ago.
Bad automatization software, I guess.
Sysadmin For DEI hires:
"Install operating system and services with default settings, turn on auto update. Collect paycheck. Point fingers when something does break."
Add in the part about convincing the company to buy every third-party security software suite who's sales guy takes you out to lunch. You should see an average business computer now, there's a stack of random security software, none of which that place nice with anything.
Automate. The word you are looking for is automate.
You absolute want some measure of manual control over your update process because sometimes updates brick things and blindly trusting that an update won't is a good way to get yourself into trouble. There's a reason IT departments employ some degree of change management.