Removing orphaned Operations Management agents using PowerShell

Article ID: 2626752 - View products that this article applies to.
Expand all | Collapse all

Symptom

In a System Center Operations Manager Command shell, you may see agents that are still in a pending management state even though they do not appear under pending management in the Operations Manager console.   

Cause

This can occur if there are agent records left behind in the Operations Manager database. At some point these agents were deployed to a management server manually but later that management server was decommissioned and the agents were never properly removed.

Resolution

Follow the steps below to resolve this issue.

In this example we assume we have two agent systems named Agent1.contoso.msft and Agent2.contoso.msft. Both agents were assigned to a management server named ManagementServer.Contoso.msft that no longer exists. In your environment you would substitute the names for your specific agents and management server. 

AgentName : Agent1.contoso.msft
ManagementServerName : ManagementServer.Contoso.msft
AgentPendingActionType : PushInstallFailed
LastModified : <date/time>
ManagementGroup : Opsmgr-Group
ManagementGroupId : 888a2cd4-0db6-f669-32f8-5b08aa25d2e2

AgentName : Agent2.contoso.msft
ManagementServerName : ManagementServer.Contoso.msft
AgentPendingActionType : PushInstallFailed
LastModified : <date/time>
ManagementGroup : Opsmgr-Group
ManagementGroupId : 888a2cd4-0db6-f669-32f8-5b08aa25d2e2

NOTE Before executing any query against the Operations Manager database be sure that a complete and current backup exists. 

-Run the following queries  

SELECT AgentPendingActionId
FROM AgentPendingAction WHERE AgentName like 'Agent1.contoso.msft'  

Result:
2A5C2E8F-2AD4-1703-D3BE-4755DF1A8E2E

SELECT AgentPendingActionId
FROM AgentPendingAction WHERE AgentName like 'Agent2.contoso.msft'  

Result:
360DB30E-3C2C-50A9-B047-A123A87280C0

Execute QUERY:-
DECLARE @ActionId uniqueidentifier
SET @ActionId = (SELECT AgentPendingActionId
FROM AgentPendingAction WHERE AgentName like 'Agent1.contoso.msft')  
EXEC p_AgentPendingActionDeleteByIdList @AgentPendingActionIdList = @ActionId

-Record is deleted successfully.

Do the same for the second agent as well.

Now via powershell we can confirm no records exist for these two systems. 

Following command will show us each agent and its assigned primary and failover management server via powershell.

get-agent|ft -a ComputerName,primarymanagementservername,@{l="secondary";e={$_.getfailovermanagementservers()|foreach{$_.name}}}
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2626752 - Last Review: July 9, 2012 - Revision: 3.0
APPLIES TO
  • Microsoft System Center Operations Manager 2007
  • Microsoft System Center 2012 Operations Manager
  • Microsoft System Center Operations Manager 2007 R2
  • Microsoft System Center Operations Manager 2007 Service Pack 1
Keywords: 
kbtshoot KB2626752

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com