Let’s be honest, most of us who play individual games like golf are cheaters. We don’t play by the rules of the game 100% of the time. OK, labelling ourselves cheaters may be a harsh indictment of our collective scorekeeping.
Yet, it’s true for almost all of us who tee up in anything that isn’t an official tournament. The kind of tournament regulated by an organized league, or which could have career-limiting or relationship
Perhaps cheaters is a strong word – maybe rule-breaker is better. It has a rebellious ring to it. C’mon, missing a server patch once in a while is a victimless offense, right? Unless there’s a data breach, or an application outage, or….
If you think about it, the process of patching apps and servers is a lot like golf. In both scenarios there are a set of rules, and each patch process has its own unique challenges, just like holes on a golf course. But unless your manager, CIO or CTO is following you, some patching doesn’t happen. – Just like how you might take a mulligan on a par three if your tee shot ends up in the trees.
We all know the consequences, when your Windows, SQL, or other application owners aren’t available to validate each update. Besides, your company couldn’t be a target for hackers, right? You’ll be fine until the cumulative update rolls out in a couple of weeks. Not to mention, many of the updates show up as “unknown” in SCCM reports if you do them. At least you’ll be sure of which server to prioritize in the next patch cycle, right?
(By the way, we’ve heard all the excuses of why servers have not been patched. We could write a book about it, or at least a really interesting blog)
In the sport of golf, some recreational players break (or bend) the rules without fully considering the reasoning behind the rules of the game. Sometimes recreational golfers deviate from the rules to accelerate the pace of play when the course is packed, or to improve one’s game when the fairways are quiet.
On Patch Tuesday every month, do you have a clearly-defined process for updating your apps and supporting physical or virtual servers? Do vacations or human errors change this process?
Are you using Microsoft SCCM? Are you an application owner or are you accountable to an application owner? The best way to ensure that the monotonous, never-ending, and unavoidable cycle of patching tasks is always completed, is through process automation.
Automation will do the following:
If you play golf like most of us on the beekeeper team, you’d be just happy to get to the 19th hole without rewriting every rule in the book. Yet, if you’ve read this far, (and thanks for doing so), then automating server patching must truly be a priority in your life.
Ready to find out how you can automate server patching and be the performance and security hero you were born to be? Reach out, let us help.
Maybe you can start spending more time on the links in the sunshine, and less time in the data center – so you can be the golfer you’ve always wanted to be.