Failing to install Windows Management Framework 3.0 for Windows Server 2008 R2 for x64-based Systems (KB2506143)
Installation Failure: Windows failed to install the following update with error 0xd00000bb: Windows Management Framework 3.0 for Windows Server 2008 R2 for x64-based Systems (KB2506143).
I've same problem on every RODC in company
Windows Server 2008 R2 SP1 Std
any suggestions?
December 12th, 2012 5:18pm
Ditto here. Only on RODCs. And, yes, they all have .NET 4.0 preinstalled and are all 2008 R2 SP1. 5 failures in a row on one machine. Antivirus disabled. Even tried skipping Windows Update and doing a fresh download with manual install. The update process
reports success every time, but after reboot (immediate or delayed until the Trusted Installer process goes from 25% CPU utilization to 0%), a check with the update history shows a failed state.
December 12th, 2012 8:25pm
Microsoft .NET Framework 4.0 installed
Installation process is ok but after reboot its updating configuration or something like that and this process fails
system is reverting changes and update gets status "Failed"
correct me if i'm wrong but this update adds "WinRMRemoteWMIUsers__" group. Yes?
and i can find it on all servers as a local group and in domain.
maybe this configuration fails because RODC can't create this group?
is it good idea to degrade RO controllers to normal server, install update and promote it to RODC once again?
-
Proposed as answer by
Shadow197
Friday, June 27, 2014 6:51 AM
December 12th, 2012 11:17pm
I had the problem on all our RODCs, too.
Solution: In Server Manager, add the feature "Windows PowerShell Integrated Scripting Environment (ISE)".
December 13th, 2012 2:16pm
Interesting. We tried adding the ISE feature to our RODCs, but it made no difference. We are still unable to successfully apply this update.
December 13th, 2012 3:48pm
same here
December 13th, 2012 4:29pm
We are also seeing failure on RODC's.
December 13th, 2012 5:36pm
I am having the same issue with all AD servers of which I have 7 in one client environment. This only fails on AD servers all member servers are successful in applying this update.
December 16th, 2012 12:16pm
Same here. Tried to add the ISE feature to one of our RODCs, but still no success. Failure of this Update on every single RODC, every other server, even DCs are fine.
December 17th, 2012 12:05pm
is it good idea to degrade RO controllers to normal server, install update and promote it to RODC once again?
any one want to tray? :)
December 17th, 2012 7:33pm
Microsoft pulled this patch today. It was causing other havoc with Exchange 2010 and 2007. Do not install this on anything for now. See, e.g., http://marc.info/?l=patchmanagement&m=135588298213669&w=2
-
Proposed as answer by
wjkessler
Wednesday, December 26, 2012 6:06 PM
December 19th, 2012 4:47pm
Just in case anyone was interested, I discovered the following helped to get WMF v3 installed on a Windows Server 2008 R2 SP1 computer. Even with .NET Framework 4.0 for Server Core and all the latest patches installed, I'd still incur
the same failure. After reading this link
http://technet.microsoft.com/en-us/library/hh847837.aspx#BKMK_InstallingOnServerCore
and enabling the features listed,
dism /online /enable-feature:NetFx2-ServerCore
dism /online /enable-feature:MicrosoftWindowsPowerShell
dism /online /enable-feature:NetFx2-ServerCore-WOW64
I was able to successfully install Windows Management Framework 3.0.
-
Edited by
'sm
Saturday, June 01, 2013 6:31 AM
June 1st, 2013 6:28am
Did anyone come right with installing WinRM 3.0 on a Windows Server 2008 R2 RODC ? If so please give all the steps in doing so.
August 26th, 2014 9:43am
I have the same issue when trying to install WinRM 4.0 on a 2008 R2 ReadOnly DC.
After install and reboot, the update is not installed and set as "failed" in the Eventlog.
September 23rd, 2014 8:19pm
I have also the same issue here, on Windows 2008R2
RODC.
Tried WMF 3 and WMF 4 with the same result.
With WMF 4, EventLog says:
Package KB2819745 failed to be changed to the Installed state. Status: 0xd00000bb
October 16th, 2014 6:17am
It seems after years (!!), Microsoft finally released a patch for the problem:
https://support.microsoft.com/de-de/kb/3020369/en-us
April 30th, 2015 3:02am