Exchange 2010 SP2 Rollup 5v2 fails to install (KB2785908):
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/7932aecb-8fa9-4a18-a605-ae6fd1020064
When you start to patch your SBS 2011 box, do NOT install the optional Windows Management Foundation 3.0 pack on the box. It is not supported to be installed where Exchange 2010 is also installed.
Note – I cannot find this fact documented in the PowerShell 3.0 release notes, but I know this from various web sites/googling my brains out and getting a verbal confirmation from several folks that it won’t be supported on Exchange 2010 until SP3 comes out which is some time next year.
Furthermore there is clearly a known issue with SharePoint 2010:
Known Issues
SharePoint Server 2010 Management Shell Stops Working
After Installing Windows Management Framework 3.0
After installing Windows Management Framework 3.0, the SharePoint Management Shell returns the following error:
“Microsoft SharePoint is not supported with version 4.0.30319.239 of the Microsoft .Net Runtime.”
The SharePoint 2010 Management Shell is not supported on Windows PowerShell 3.0.
To resolve the problem:
1. Use the following command to start the Windows PowerShell 2.0 engine.
powershell.exe -Version 2.0
2. Use the following command to add the SharePoint snap-in
Add-PSSnapin Microsoft.SharePoint.PowerShell
…and I get this on my test box:
Edit: 8/22/2013
Update (04/18/2013):
If you have the update (KB2506146 for Windows 2008 SP2 and KB2506143 for Windows Server 2008 R2 SP1) installed on your server, an optional update KB2823180 will be offered through Windows Update.
PowerShell 2.0 is the only current supported version of PowerShell as mentioned on the Exchange Server Supportability Matrix over on TechNet:
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.141).aspx
So don’t install WMF 3.0 on any system running Exchange Server or SharePoint Foundation/Server.
If WMF 3.0 is incompatible to Exchange 2010 and is incompatible to Sharepoint 2010, and both of them are an integral part of SBS 2011, then WHY THE HECK is this update pushed down to every SBS 2011 server through Microsoft Update/WSUS?
And in the release notes or in the knowledge base there is nowhere any mention that you should not install this update!!! I wasted hours beause of this crap
Ya, this update horked up my powershell, too. Were it not for Susan’s posting, I may have pulled out all of my hair trying to resolve Powershell 32784 and WinRM 163 errors that appeared after the installation reboot.
A simple uninstall of the KB in question resolved my issues.
Thanks, Susan, for bringing this to light.
No issues here, but we long since gave up on Sharepoint. Anything that requires such silly handholding to get up and working in the first place was never destined for our servers. Has it improved from the days of old?
OMG, that got installed on our most recent SBS deployment/migration when the patch got picked up from the legacy WSUS server when we paused the setup project overnight. Completely blew up the install when it hit the Exchange and Sharepoint automated install phase.
What a PITA; removed the patch; hand installed Sharepoint and Exchange ran the associated fixes and we are back in business but this little patch just cost 10 hours of digging……
All that so we can have useless wizard that probably will never get used. *sigh*
Thank for posting this; you just saved the rest of my weekend.
If you install WMF 3.0 on a SBS 2011 server, you won’t be able to add users via the SBS console. The process fails with a WinRM error when it gets to the point of adding the new users mailbox.
What the *>##&* is Microsoft thinking in releasing this stuff (even optionally)?????
Hi,
how to uninstall KB2506143? It seems that the patch came with Windows Server Update KB2779562.
When adding users via SBS Managment Console there is a problem cerating the Mailbox.
The December time zone update does not contain WMF 3.0 You must have another issue. Post in the sbs forum please.