UPDATED: — After a week of pain, WMF3.0 has been expired from the Microsoft Update catalog to stop anyone else from experiencing these issues. Microsoft has said they will work to find out how something like this could have made it through testing. For the text of Microsoft’s public statements and information about fixing your broken infrastructure, see this post by Rod Trent. —
Windows Management Framework 3.0 (KB2506143 for W7/2K8R2, KB2506146 for 2K8) may be causing issues in System Center 2012 Configuration Manager environments. Although KB2506143 and KB2506146 were first released to the Microsoft Download Center back in September, the updates just became available this past week to WSUS and Software Update Points on December 11th with the normal monthly patch Tuesday update to the Microsoft Update catalog.
While KB2506143 and KB2506146 have the update classification of “Update”, they contain significant improvements with Windows PowerShell 3.0, WMI, WinRM, Management OData IIS Extension, and the Server Manager CIM Provider. In some circumstances these changes appear to be causing issues with Management Points, Distribution Points, and the client CCMEval health task according to community members on MyITForums, TechNet forums, and individual blogs.
Rob Plank’s Blog: Bugs with SCCM 2012 And Powershell v3
TechNet Forums: Ccmeval error – WMI Repository Read/Write Test
TechNet Forums: SCCM console suddenly unable to connect
Some forum posters report that they have worked with Microsoft CSS and been told this is a bug which will be fixed in Service Pack 1. No official information about these issues has been publicly posted on the ConfigMgr Blog, Support Team blog, the Microsoft Knowledge Base, or in the WMF3 release notes.
If you are experiencing issues with your Configuration Manager infrastructure and clients after installing KB2506143 or KB2506146, you should open a support case with Microsoft CSS. Support for problems stemming from updates should be resolved without charge. I would encourage you to post in the comments the results of your support case and any links to public information they refer you to.
This post will be updated as more information becomes available. We are eagerly looking to the ConfigMgr team for public information. Public information posted here.
RELATED: The Exchange team has a blog post about WMF3 causing issues with Exchange Server 2007/2010. They explicitly state WM3 is only supported on Exchange Server 2013. (Friday, Dec 14th)
RELATED: The Small Business server team has a blog post about WMF3 causing issues on SBS 2008/2011 with the Exchange and SharePoint management shells, and several of the SBS wizards. The SBS team officially recommends not deploying WMF3 to SBS 2008/2011 servers at this time. (Saturday, Dec 15th).
UPDATED: After a week of pain, WMF3.0 has been expired from the Microsoft Update catalog to stop anyone else from experiencing these issues. Microsoft has said they will work to find out how something like this could have made it through testing. For the text of Microsoft’s public statements and information about fixing your broken infrastructure, see this post by Rod Trent.
I hope that helps!