Wednesday, December 16, 2009

Remove an Orphaned DPM Agent from the DPM Console

If you have a failed or an orphaned computer that is still showing DPM console, you need to manually remove it from the console. 

If this server is still part of any Protection Group, you need to remove this server from the PG first.

  1. In DPM Administrator Console, click Protection tab on the navigation bar.
  2. In the display pane, select the protection group member that you want to remove.
  3. Right click the member and click Stop protection of member option.
  4. In the Stop Protection dialog box, choose whether you want to retain the protected data or delete it.

image

Second step in the process is to remove the server record from the DPM

  1. In DPM Administrator Console, in the Management task area, on the Agents tab, select the failed protected computer.
  2. In the Details section, click Remove the record of the server from this DPM computer option.

Note: If you don't see the Remove the record of the server from this DPM computer option, right click the protected server and select Refresh Information option

image

This will completely remove the protected server from the DPM.

DPM 2010:  In DPM 2010, you can use remove-productionserver.ps1 script to remove stale agent records. 

Here is the syntax:

Remove-ProductionServer.ps1 <DPM Server Name> <Protected Server Name>

SS

Santhosh Sivarajan

Microsoft MVP · Identity & Cybersecurity Architect

Santhosh has 30+ years of hands-on enterprise experience in Identity and Access Management, Microsoft Entra ID, Active Directory, Microsoft 365 and Zero Trust architecture. He is the author of two books on Windows Server and security, and leads consulting, assessments and training at SAG Business Group.

2 comments:

Simple yet very effective.

Thank you very much.

Thanks for the feedback.This is an old blog. I am glad that people are still using this.

Post a Comment

Popular Posts
Workstation Trust Relationship Issue Issue: You receive the following error message, when you try to login to the domain.  The security database on the server does not have ... ADMT Service Account - Permission and Configuration The ADMT service account needs to have proper permission in source and target domains.  You don’t need to use 2 separate accounts.  You can ... My First Peek into Microsoft Exchange 2010 By Santhosh Sivarajan Before I really dive into Exchange 2010, I thought I would install and play with it first. I took some screen shots and notes during the ins... ObjectSID and Active Directory What is an objectSID in Active Directory? When a new object is created in Active Directory, Domain Controller assigns a unique value used ... AD Group Report - List Group Members in Active Directory–PowerShell Script Updated Script - http://portal.sivarajan.com/2011/10/search-ad-collect-local-admin-group.html Script #1 This script... Add Users to a Group–PowerShell Script Purpose – Add users to a group from an input file – PowerShell V2 Script.  Input file – Input file (Users.csv) contains samAccountName in... User Account Migration and Merging – Part I (ADMT) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM pre-creating user account ... User Account Migration and Merging – Part II (Quest Migration Manager) Part I - User Account Migration and Merging Using ADMT Part II - User Account Migration and Merging Using QMM Pre-creating user account in... Delete Stale or Inactive Computer Accounts from Active Directory Here is an easy way to identify and delete inactive or stale computers in an Active Directory environment.  Using the dsquery command you c... Converting PowerShell (PS1) to EXE / Standalone Application As we know, there many applications available to convert a PowerShell file to a standalone executable file.  Based on my experience, PowerSh...