Test your support
If you're like me, you probably avoid calling tech support at almost all costs. Unless there's absolutely no hope of solving a problem on my own, I'll opt to do my own troubleshooting and research to fix a problem rather than create a ticket and wait for a response.
That's a commentary on the generally dismal quality of most IT vendor tech support and on the amazing utility of a Google search in solving just about any problem you'll run across. It's also a result of the fact that I tend to learn a lot more about the tech I'm using when I'm forced to study up and fix it myself.
One real downside to the DIY approach is that you won't get a feel for how good tech support will be when you actually need it. Make sure to throw tech support a bone every once in a while and pay close attention to how quickly and effectively it responds. Even fairly simple questions can give you an idea of what to expect when you find yourself in the weeds and really need the help.
Above all else, never allow yourself to become too cozy with any vendor -- no matter how long you've worked with its products. What may be an excellent hardware or software solution today may become one of the most maligned a year or two from now. Always be ready to consider options.
This article, "When to cut bait on old IT," originally appeared at InfoWorld.com. Read more of Matt Prigge's Information Overload blog and follow the latest developments in storage at InfoWorld.com. For the latest business technology news, follow InfoWorld.com on Twitter.