Forum Discussion
MaintenanceCoordinator Orchestration Lock is required
I have been getting this since installing the update that converted Server Groups to Orchestration Groups. I have removed all "converted" Server Groups and now have no Orchestration Groups. I have un...
Have look at the properties of the Orchestration Group. Make sure the "Orchestration Group Member timeout" covers the sum of the maximum runtimes of all updates. It's similar to maintenance windows, it won't start installing unless there's enough time to do all updates.
I opened a case with MS support. Orchestration groups created prior to MECM 2010 can exhibit this issue. New Orchestration groups created in 2010 and later should no longer have this issue. If you use WMI explorer and check the namespace root\ccm\policy\machine\ and class CCM_PrePostActions you will see the pre and post scripts there from when it was a member of the Orchestration Group. You need to delete the instances. Haven't had any updates that I've needed to install yet, but I'm hopeful.
Thanks I will give that a try. I think I already tried clearing WMI namespace but I can't remember for sure.
Dave
