KB: Configuration Manager Management Points collocated with clients fail after installing Windows Management Framework 3.0 and running Client Health Evaluation

KB: Configuration Manager Management Points collocated with clients fail after installing Windows Management Framework 3.0 and running Client Health Evaluation

  • Comments 4
  • Likes

imageWe’ve been getting a couple support calls regarding an issue with Windows Management Framework 3.0 and the recently released associated KB2506143.   System Center 2012 Configuration Manager admins are experiencing a failure on management points collocated with clients post installation of Windows Management Framework 3.0.  

The issue is that daily, System Center 2012 Configuration Manager Management Points (MPs) that are collocated with the client will fail, returning HTTP 500s to calling clients.  This occurs after the Client Health Evaluation task runs and reinstalls the client.  Inspection of the CCMEval.log will show entries similar to the following:

Loading manifest file: C:\Program Files\SMS_CCM\CcmEval.xml
Successfully loaded ccmeval manifest file.
Begin evaluating client health rules.
Successfully retrieved all client health checks.
Evaluating health check rule {4AB7D77D-3BB0-4EAB-BEFD-7C0F7DA10296} : Verify WMI service exists.
Evaluating health check rule {518C0699-03F8-4F38-85C4-4D319EAEFC05} : Verify/Remediate WMI service startup type.
Evaluating health check rule {7F4B6E15-2221-455B-9615-93C379E470D5} : Verify/Remediate WMI service status.
Evaluating health check rule {A81778B5-9A1E-4A52-9C6E-6939CEFAA118} : WMI Repository Integrity Test.
Windows has an improper shutdown before the latest start up at 20121218093732.000000-000
Evaluating health check rule {14E6774A-1795-4E09-B17D-B6F36A124205} : WMI Repository Read/Write Test.
Failed to delete class 'CIM_ClassDeletion' (80041002)
Failed to delete class 'CIM_ClassCreation' (80041002)
Failed to delete class 'CIM_ClassModification' (80041002)
Failed to delete class 'CIM_ClassIndication' (80041002)
Failed to delete class 'CIM_InstCreation' (80041002)
Failed to delete class 'CIM_InstModification' (80041002)
Failed to delete class 'CIM_InstDeletion' (80041002)
Failed to delete class 'CIM_InstIndication' (80041002)
Failed to delete class 'CIM_Indication' (80041002)
Failed to delete class 'MSFT_ExtendedStatus' (80041002)
Failed to delete class 'MSFT_WmiError' (80041002)
Failed to delete class 'CIM_Error' (80041002)
Fail to delete namespace (root\cimv2\ccm2) (0x80041002)
Checking WMI repository for feature General failed
WMI check failed
Windows has an improper shutdown before the latest start up at 20121218093732.000000-000
Stopped the service 'ccmexec' successfully
Stopped dependent services for service 'winmgmt' successfully
Stopped the service 'winmgmt' successfully
Attempting to launch repository repair.
Attempting to remediate client or client prerequisite installation.
Client or client prerequisite installation remediation succeeded.
Failed to delete class 'CIM_ClassDeletion' (80041002)
Failed to delete class 'CIM_ClassCreation' (80041002)
Failed to delete class 'CIM_ClassModification' (80041002)
Failed to delete class 'CIM_ClassIndication' (80041002)
Failed to delete class 'CIM_InstCreation' (80041002)
Failed to delete class 'CIM_InstModification' (80041002)
Failed to delete class 'CIM_InstDeletion' (80041002)
Failed to delete class 'CIM_InstIndication' (80041002)
Failed to delete class 'CIM_Indication' (80041002)
Failed to delete class 'MSFT_ExtendedStatus' (80041002)
Failed to delete class 'MSFT_WmiError' (80041002)
Failed to delete class 'CIM_Error' (80041002)
Fail to delete namespace (root\cimv2\ccm2) (0x80041002)
Checking WMI repository for feature General failed
WMI check failed
Result: Remediation Failed, ResultCode: 304, ResultType: 202, ResultDetail: root\cimv2\ccm2#CCMEVALPARAMSEP#20121218093732.000000-000

Please see KB2796086 for more information.

-----

2796086 - Configuration Manager Management Points collocated with clients fail after installing Windows Management Framework 3.0 and running Client Health Evaluation (http://support.microsoft.com/kb/2796086)

J.C. Hornbeck | Knowledge Engineer | Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Why didn't Microsoft thoroughly communicate the impact Windows Management Framework 3.0 would have on their products prior to releasing it and classifying it as important? Now, after the fact, Microsoft has numerous blog posts and other information about the problems Windows Management Framework 3.0 causes to its own products which are not compatible with Windows Management Framework 3.0. Microsoft can and should do better

  • not good - all our Clients have this installed with issues all around. Regedit is not an option as we have our staff locked down to User.  Any news of a Fix we can deploy asap??

  • We have SP1 installed on our ConfigMgr site but we still have this issue every night. We need to reinstall the MP every day!

  • I agree with Roel. We have SP1 installed and still i get errors from ALL Win8 machines.