Upgrade it, Patch it, Break it

The classic dilemma for patch management is when to do it and what will it break.  Especially, when dealing with Operating systems you run the risk of the application you’ve been using for decades suddenly not working (not supported).

This issue is bad enough when doing the upgrade for yourself but when you do it on behalf of a client you run the risk of being the root cause of the problem.

The latest MacOs upgrade is not compatible the Outlook for Mac 2013 (version 15.3), which was released October 2014….WTF.  So now you have to spend time and money on an upgrade.

Always plan your Technical upgrades

The best practice is to run a compatibility test on all applications especially business-critical ones. But why haven’t two of the biggest software vendors in the world built that into the OS upgrade process to at least notify the user?

Money talks louder, so shut up and buy the Office365 upgrade


Meanwhile, I try to keep my head straight and get totally distracted by just looking out the window.  Austria is a great place to avoid mass marketing but dammit this has just pushed me back into my one-track mind.

Everywhere I look….

What was the approval process for a company to register and pay for this domain and then actively market it?

So much for Global Thinking