Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010

Update 9/19/13: A side-by-side coexistence of PowerShell 3.0 and PowerShell 2.0 is supported starting with Exchange 2010 SP3. Note that Exchange 2010 will only use PowerShell 2.0 so PowerShell 2.0 is still a required component.

Recently, Windows Update began offering the Windows Management Framework 3.0 as an Optional update. This includes all forms of update distribution, such as Microsoft Update, WSUS, System Center Configuration Manager and other mechanisms. The key bit here is that the Windows Management Framework 3.0 includes PowerShell 3.0.

Windows Management Framework 3.0 is being distributed as KB2506146 and KB2506143 (which one is offered depends on which server version you are running - Windows Server 2008 SP2 or Windows Server 2008 R2 SP1).

What does that mean to you?

Windows Management Framework 3.0 (specifically PowerShell 3.0) is not yet supported on any version of Exchange except Exchange Server 2013, which requires it. If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Exchange update rollups that will not install, or the Exchange Management Shell may not run properly.

We have seen Exchange update rollups not installing with the following symptoms:

If rollup is installed through Microsoft Update, the installation might error with error code 80070643

If rollup is installed from a download, the error displayed is Setup ended prematurely because of an error.

In both cases, Event ID 1024 may be logged in the Application event log with the error error code “1603”. For example, if you try to install update roll 5 for Exchange 2010 SP2, you may see the following description in event ID 1024:

Product: Microsoft Exchange Server - Update 'Update Rollup 5-v2 for Exchange Server 2010 Service Pack 2 (KB2785908) 14.2.328.10' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127

Our guidance at this time is that Windows Management Framework 3.0 should not be deployed on servers running Exchange 2007 or Exchange 2010, or on workstations with the Exchange Management Tools for either version installed. If you have already deployed this update, it should be removed. Once you remove the update, functionality should be restored.

No offense, but are you out of your mind? I can´t believe this. If an update is delivered via the standard windows update online mechanism, quality asurance at ms HAS TO make sure there are no conflicts or problems. This is a huge step back from my point of view.

On our servers, this update is presented as an "Important" update. There is no indication in WSUS or anywhere else that this update is 1) optional or 2) not supported. After breaking one Exchange server over the weekend, I skipped the update on the other two. Over the past few years Microsoft had improved its reputation for quality checking software updates and releasing them on a predictable schedule, but instances like this one and the recent fiasco with Rollups 4 and 5 are a step in the wrong direction.

SO at MMS 2012 we had classes going over the power and flexibility of PS 3.0 and the new WMF. So now it gets pushed out and Exchange 2010, SCVMM 2012, and a possibly other systems flat out don't work with it?

Really disappointed that MSFT did not properly regression test the Framework prior to deployment. Exchange 2010 is not a fringe product. Customers should not have to deal with mopping up due to bad planning and testing on MSFT's part. In addition to a pre-deployment heads-up regarding the compatibility issues, Windows Update should have been configured to not suggest the Framework if a conflicting product was installed on the target computer. Not good. Very disappointed. I am venting here; however I am not faulting the Exchange team on this … if anything, thanks go to them for the notification … it is just that others should have been more careful and responsible.

Perhaps the Exchange Team should next publish an article describing the joys and benefits of testing patches/updates on your non-production Exchange servers… BEFORE deploying to your production environment.

After unistalling Windows Management Framework 3.0 I could install the RU5v2. But for some problems I had to remove my userprofile. After that the following Error still exists: In the Eventlog I always get an error If I open "Administrative Events". That Error says "at least one protokoll in the query contains an error". The Protokoll is "Forwarded Events". On our other Server this in German – probably the unsinstall routine changed that on the particular server to english.

Now this is lovely. During this month's patch cycle I am trying to uninstall WMF from the Exchange machine. It says it is successful, then during the reboot it gets to 98%, fails, reverts all the changes back, reboots again, and when it's finally running, WMF is still installed.

It seems that every six months or so I end up building a new Exchange server and migrating everything for one reason or another. Here we go again.

@Pepper: Sorry you're having that unusual experience. I'd recommend contacting Support before you decide to rebuild a server. Additionally, if not already deployed, look into HA mechanisms like Database Availability Groups.