Generally, certification is useless except for "compliance" and "get support for something". If you are running a supported combination of hardware and softwar

Generally, certification is useless except for "compliance" and "get support for something". If you are running a supported combination of hardware and software, the hardware vendor can't officially close your case just because "you are running unsupported software and we are sure your OpenBSD damaged your mouse" or similar BS. However, as long as there is a hardware problem you are able to clearly identify, support is usually not a problem even with non-certified software with most (but not all) vendors. Problems that might be either hardware or software are always a problem, because you are almost always dealing with 2 vendors blaming each other. The certification leads to a slightly lower overhead for convincing the support to take the case and a slightly higher number of solved cases. But nothing dramatic. And also take care that the supported software is usually a specially adapted version of something, e.g. the exact installation of Windows your laptop came with. If you reinstall your companies default Windows image you are out of luck. If you upgrade to another service pack or major version, you are out of luck. Also "certfied" is necessary for stuff like "our processes for adding numbers are certified ISO12345 and demand supported hard- and software". There is no real benefit besides complying with some obscure checklist some useless PHB came up with. But in some industries, you cannot do business without that, no matter how pointless, expensive, unsafe, insecure or counterproductive it might be. In sum "certified" means "the bureaucracy won't be able to complain", not "it works".