Last week we ran into the problem that our MDT task sequences where not manageable and the management point was not healthy anymore. For MDT removing and reconfiguring the integration did not work and just reinstalling the Management Point did also not give us the fix we needed. After some research it seemed that a Microsoft Update of the Windows Management Framework 3.0 (KB2506143) broke down the Management Point, and “luckily” we were not alone.. (see here, here, here and here 😉 ) What we did to get the Management Point up and running again was the following.
- Removed update KB2506143 from the Software Update deployment
- Uninstalled update KB2506143 on the Configuration Manager 2012 server
- Changed the CcmEval=TRUE registry key workaround described in KB2796086
- Rebooted the Configuration Manager 2012 server
- Removed the MDT 2012 integration with Configuration Manager 2012
- Removed the Management Point from the Configuration Manager 2012 server
- Rebooted the Configuration Manager 2012 server
- Installed the Management Point on the Configuration Manager 2012 server
- Rebooted the server
- Configured the MDT 2012 integration with Configuration Manager 2012 again
After this the Management Point was up and running again and the MDT based Task Sequences were manageable again.
What we saw was the following;
- TaskSequenceProvoder.log reported no information anymore
- Automatic reinstall of the MP and client occurred during the night.
- MDT option was gone in the Task Sequence editor
- Unable to create an MDT task sequence (“Failed to load class properties and qualifiers for class BDD_UsePackages in Task Sequence”)
- Lot’s of errors in the MP state messages.
Hope this helps!
Thanks to my colleague Roel Janssens for pointing out to the KB2796086 and retesting the procedure
