IT pros around the world know to that before updating a server OS, take the time and test the update before applying to production. If you’re running an enterprise server such as Exchange or SharePoint, this “lab” testing is even more important. Updates can cause problems: we all know this.
Another course of action (if you don’t want to take the time to test) is to check with the product teams for any last minute notes regarding problems that might occur with an update. The Exchange team is a good example of a team that will let you know if a server update – or service pack – will cause a problem or not. Updates can cause problems: we all know this.
So why is it that when WMF 3.0 (PowerShell 3) was released into the update stream in late 2012 as a recommended update, many so called IT pros just slammed the update to production servers without testing or checking with the product teams for products like Exchange or SharePoint? The result? Crash. Makes me wonder who is in charge of updates.
The Exchange team clearly posted “DO NOT” install WMF 3.0 on Exchange 2007 or Exchange 2010 until they release their own update, but unfortunately many ignored this.
So, the result of all of this? WMF 3.0 has been removed from the update stream for Server. Before you upgrade to WMF 3.0, check the list of Not-Ready-For-This-Yet software such as SharePoint, Exchange, SBS, System Center and so on. Here’s a link to complete list and what to do if you updated and broke something. Windows Management Framework 3.0 Compatibility Update.
Knowledge is PowerShell,