Share via

SCCM Client: Orchestration lock is required. LockIsAvailable: 00000000: Updates Cannot Install

Thomas Faherty 151 Reputation points
2021-04-05T19:55:43.52+00:00

Hello,

I am opening a new thread to try and get this solved. I had another thread for what I thought was the issue but was not titled properly so I will probably close that one and try to find help here. I had a Service Desk guy create an Orchestration group without saying anything to me which resulted in 289 clients not being able to install updates.

UpdatesDeployment logs just keeps spamming

Orchestration lock is required.
LockIsAvailable: 00000000.

I deleted the group but no change. I also tried removing the client, removing the machine from SCCM, then installing it on a client to test if I could free the lock but no luck logs are still complaining even after hours.

I am hoping someone can help me get things moving again.

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
1,127 questions
0 comments
Accepted answer
  1. Jason Sandys 31,406 Reputation points Microsoft Employee Moderator
    2021-04-06T18:36:20.327+00:00

    This is a known issue that is addressed in the 2006 HFRU and 2010+. Please upgrade your site.

    1 person found this answer helpful.

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SunnyNiu-MSFT 1,706 Reputation points
    2021-04-06T09:44:05.893+00:00

    @Thomas Faherty
    Here is an answer to your question that hopefully you find helpful!
    According to the information we searched, this is indeed a known issue.
    There must be some registry key or something in WMI that is still remembering the machine being part of the old "Server Groups" or "Orchestration groups".

    If the response is helpful, please click "Accept Answer"and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments
  2. Carl Morris 1 Reputation point
    2021-05-07T12:25:00.327+00:00

    @Thomas Faherty
    Give this a go for versions prior to MECM 2010, run the following powershell script against affected clients:

    Get-Service CcmExec | Stop-Service -Force # -Verbose
    Rename-Item "C:\Windows\CCM\Logs\MaintenanceCoordinator.log"-NewName "MaintenanceCoordinator-$(Get-Date -Format"yyyyMMdd-HHmmss").log"
    Get-WmiObject -Class CCM_PrePostActions -Namespaceroot\ccm\policy\machine\RequestedConfig | Remove-WmiObject -Verbose
    Get-WmiObject -Class CCM_PrePostActions -Namespaceroot\ccm\policy\machine\actualconfig | Remove-WmiObject -verbose
    Get-Service CcmExec | Start-Service # -Verbose

    It has been fixed in version 2010

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.