Share iT…

Last week microsoft released Windows Management Framework (WMF) 3.0 which includes Powershell 3.0 (KB2506146 for Windows 2008 SP2 and KB2506143 for Windows Server 2008 R2) as an optional Windows update. So everyone can approve and install the update via Windows update, WSUS or any other updating mechanism you are using.

But installing this update on a Small Business Server (SBS) 2008 and 2011 or on an Exchange Server 2007 and 2010 will give all kind of trouble.

Symptoms for an Exchange Server:
Installation of Exchange update rollups will fail one of the errors is: error code of 80070643.

The Exchange Team wrote this blog about this issue. It states: “Windows Management Framework 3.0 (specifically PowerShell 3.0) is not yet supported on any version of Exchange except Exchange Server 2013. If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Rollups that will not install, or the Exchange Management Shell may not run properly.”

Symptoms for a Small Business Server:
When running some SBS wizards like the Fix My Network wizard it will end up with errors about access denied for the Exchange Management Shell.
Also other kind of problems may occur with the Exchange and / or SharePoint 2010 Management Shell and as written for Exchange Servers installation of Exchange update rollups may fail.

On the Small Business Server Blog there is a post on these issues.

Recommendation for both Exchange and Small Business Servers is to NOT install the Windows Management Framework 3.0 update at this time. If you already installed the update and encoutered the previously described problems, uninstall the update. Your server should be fine when it comes back online after a restart.

Update:
There is another problem reported in the Small Business Technet forum uninstallation of the also removes a registry key that gives problems to the event log. This is the key that is deleted: “HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ WINEVT \ Channels \ ForwardedEvents”

Anytime later in the same post there is a mention that the updates are removed from Microsoft Update:

As a result of these regressions and feedback from customers and experts like you, we have expired the WMF 3.0 Update for all platforms (Windows 7, Server 2008, and Server 2008 R2) as of 5:07 pm PDT.

doug neal
Microsoft Update (MU)

This is a question I see a lot and today the SBS team clarified there statement that you should install windows server 2008 R2 SP1 on your SBS 2011 server.

Quote:
“We have been receiving a few questions on whether or not Windows Server 2008 R2 SP1 can be installed on SBS 2011 and wanted to provide the definitive answer on this blog. Yes, it can and should be installed on SBS 2011 Standard. Please note that SBS 2011 Essentials already has SP1 installed out of the box.

A good rule of thumb is that if the patch or service pack is offered to your SBS server on Windows Update, it is supported to be installed on SBS. The SBS SE team reviews patches and service packs before they are offered to SBS servers.

If you download the service pack manually you may notice that it is listed as Windows Small Business Server 2011 Service Pack 1. This is normal. Windows Small Business Server 2011 Service Pack 1 == Windows Server 2008 R2 Service Pack 1.

Please be sure to back up your server before installing any update.”

Source: the official SBS blog

Go directly to SBS 2011 index file. With links to all articles from this serie.

After we have finished with Part 14 Configuring “Add a new report” we go to the security page of the SBS console and choose for the updates tab.

Here you see an overview of the windows updates if there are updates pending for approval or errors you can see them over here. Also By default Optional Updates are not installed automatically.

Right click an update and choose if you want to deploy or decline the selected update.

If you choose approve you get this warning message, to continue click OK.

And another message that it could take 4 till 24 hours before the update will be deployed to the computers on your network.

After you approved or declined all updates we are going to take a look on the software update settings. On the right taskbar choose “Change the software update settings”

On the Server Updates part, choose the update level you would set for your servers. Think carefully before you set this setting to high and approve every update automatically. If it may go wrong it concerns your server.

On the Client Updates part, you choose the same setting as on server updates but this time for client computers.

On the Schedule part you choose separate for server and client if you would install the updates automatic during a schedule or only notify the new updates are available.
Note!! Is you choose for automatic installation and an update requires a restart the client or server will automatically restart at that time. So think twice before you set this for a server computer.

On the Included Computer part, you can add or remove if a server or client computer must be part of the software update group. If you have some very important client computers that may never restart automatically. You can select the client computer and choose Modify…

And change the update group, so if you leave the settings for server not to automatically install and restart change the Update Group to the Server Computers. The selected client will now perform updates according to the Server Computers settings.

Go back to Part 14 Configuring “Add a new report”
Continue to Part 16 Configuring “Configure a virtual private network (VPN)”

On a Windows 2008 R2 Hyper-V configuration with 2 network adapters I experienced the following problem: I installed a Windows 2008 R2 guest this was no problem, but when I try to do windows updates I got an “Windows could not search for new updates, An error occurred while checking for new updates for your computer. Error(s) found: Code 80072EE2” error message.

Everthing else looks fine, dns resolving works fine, network browsing looks good, I could access internet pages even the windows update page, but trying to update gives this particulary error.
Tried the same on a windows 2003 guest and everything looks fine. Installed another Windows 2008 R2 server same problem occurres.

Solution: After some more trouble shooting I found that when I start the windows update I lost network connection on that particulary network adapter, even on all other VM’s using that adapter and on the Host. Now I was connected with the other adapter so I didn’t see this behaviour in first place. So I bound the other network adapter to one of the Windows 2008 R2 guests and I could windows update with no error.

Because I would like to know what was causing this problem I found after some more troubleshooting and testing that the problem was caused by the Large send Offload setting enabled on the network adapter. After disabling this setting everything works fine.

The network adapter was causing the trouble was a D-Link DGE-528T Gigabit Ethernet Adapter.

After installing a fresh installation of windows 2008 R2 standard on a HP proliant dl380 g6 and turning on windows updates I got a error: code 80072F8F

Solution: Date and time range were not allright by default date and time on a hp proliant server are most of the time a few months in the past.

After downloaded all updates and installing arround 20 updates it stops with error: code 800F0902. 7 updates failed.

Solution: I restarted the server so the installed updates are configured. After restart I ran windows updates again and now the other updates are installed fine.