Jump to content


Peter33

Warning: KB2506143 (WMF 3.0) breaks MP Control Manager on Windows 2008R2

Recommended Posts

Hi,

 

we got a little issue with an WSUS update today. The server team published the update for the Windows Management Framework 3.0 on all servers.

Unfortunately that was causing the MP Control Manager to fail on all SCCM Servers :wacko: .

The mpcontrol.log showed some WMI errors. So i looked which updates lately got installed and found the KB2506143 in the list.

The solution was to uninstall KB2506143, reboot the server and hide the update. After that i just had to remove the management point roles and to reinstall them.

 

Here is someone with the same issue. The Microsoft answer is sorta funny.

Share this post


Link to post
Share on other sites

This is an optional update, just checked my servers as I do not allow SCCM to manage them and I also have auto updates turned off, they download but I choose what to install(some extra management but worth it in cases like this). I have now made this update hidden on all Site servers.

 

Also my win 7 ADRs' on all sites have 3 filters associated with them Bulletin ID(MS), product(windows7) and superseded(NO). This update was filtered out due to the Bulletin ID filter(thankfully). It is in the all software updates group but it shows not downloaded and my ADR is running tomorrow a week later after patch tuesday, this is not a mistake, I do this for cases like this also, the ADR runs tomorrow and the deadline is 2 days after this each month so i have 9 days of a windows to catch problematic updates if they arise.

 

Thanks peter.

Share this post


Link to post
Share on other sites

until microosft releases a fix the suggested workarounds on myitforum are what you should do (don't deploy this update and/or disable wmi rebuilding.)

Share this post


Link to post
Share on other sites

"Microsoft has officially notified me it is a bug and they duplicated it.

their recommend fix are:

option 1: Services Pack 1

or

option 2: disable SCCM 2012 Client Health Check from rebuilding WMI.

i told them to come up with option 3. waiting to hear back"

 

:D LOL

Share this post


Link to post
Share on other sites

Our server team is using powershell 3 now for maintanace tasks. So that's why the update was publisheda as mandatory. If you are not planning to use PS3 you don't need the update. Otherwise wait for SCCM 2012 SP1 until you depoy it. Same goes for Windows 7 clients because it will break the client health check of the sccm client.

Share this post


Link to post
Share on other sites

Sorry to hear that. Client health check is an important part of SCCM 2012 from my point of view, so i would not want to disable it. You might just remove the update and reinstall your sccm clients, or disable the client health check until SP1. Otherwise the client will always try to repair WMI and create a lot of alerts on your server.

Just had to remove the SCCM Clients from our servers today and to reinstall the MP roles, because the client health check broke the MP again last night. I did'nt remove the client installations after uninstalling the update yesterday.

I hope that the status is green tomorrow with the fresh clients.

Share this post


Link to post
Share on other sites

Sad to say I am a victim of this evil KB. My management points crashed so I uninstalled the role and reinstalled. Also removed the KB from the servers and removed the CCM client. My management points went green for a while today but look to be failing again. Client check failure is going up in count by the hour. Anyone know if SP1 will truley fix this issue? I know its in beta but I am tempted at this point to apply it.

 

I am also hoping this wont require alot of clean up work on my clients. Right after a migration too from SCCM 2007. Happy Holidays from Microsoft :angry:

Share this post


Link to post
Share on other sites

Victim here aswell. 92 clients with the Failed to delete namespace root\cimv2\ccm2 error. Also noticed software center is not populated on these computers seems broken, also new clients installing the SCCM client, seems like it does half a job, doesnt install SCEP, got some investigating to do on this. I just hope SP1 sorts out this mess.

 

UPDATE: ok, got a fix for it, make sure you uninstall the windows managment framework on the server and client computers first. Remove the Management point role on the SCCM server, reboot, add the managment point back on the SCCM server, reboot server. Unistall the SCCM client from a pc, reboot pc, client reinstalls, all seems well. Just got to do this on 90 client machines now.

Share this post


Link to post
Share on other sites

Its just that simple! I have removed the update on my primary and 3 of my MPs and removed the SCCM client from all 4 servers. Thats the only way I have been able to keep my MP roles stable. I have had some issues with auto client installation on machines as well. If I right click the machine and push the client through the wizard it will install fine.

 

SIMONLJ when you removed WMF on workstations and reinstalled the client did you have to rebuild the repository folder in C:\windows\wbem? I read that this is someth that needs to be done but I have tried on some servers and their clients still fail checks. So I have no evidence in my enviornment this resolves anything.

 

Anyways this is horrible but glad I am not alone in this issue.

Share this post


Link to post
Share on other sites

no I didnt rebuild the repository folder in C:\windows\wbem, still have some issues, got some red stuff in componant status

SMS_SRS_REPORTING_POINT

SMS_PORTAL_CONTROL_MANAGER

SMS_MP_CONTROL_MANAGER

SMS_AWEBSRV_CONTROL_MANAGER

 

ahhh this sucks, but the client pc's are happier unlike me, merry christmas microsoft

Share this post


Link to post
Share on other sites

So to reinstall a client I have had to stop WMI, nuke the repository folder(s), and then restart WMI to rebuild the repository. After that the client will install fine. Otherwise it fails. I am actually going to try a reset on the repository through cmd line because MS says this is better practice. We'll see. To have to hit 250 clients is going to be painful. MS really screwed up on this one.

Share this post


Link to post
Share on other sites

OK people. I have installed SCCM 2012 SP1 and can confirm this issue has been fixed. Installation went quite smoothly, a couple more pre-req's needed addressing before the installation went through on the Site upgrade. Once site upgrade has completed, you can install the console, I recommend uninstalling the console first before installing the SP1 console. 3 Days after the upgrade the majority of clients have upgraded and are green for go and not red for wmi repository read write test remediation fail. Just going to leave the rest to gradually update and sort themselves out as they come online.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...