Today I tried to remove an orphaned DPM 2010 agent from my DPM console. But I couldn’t find how to do that. 🙂
I found out that there is a powershell script to do just that. It’s called “Remove-ProductionServer.ps1”, sweet
Just startup your DPM Powershell environment and run the script.
It will ask you for your DPM server and the server to remove. You could also provide these as parameters, like so:
.\Remove-ProductionServer.ps1 <DPM Server Name> <Protected Server Name>
Yesterday I started installing DPM (System Center Data Protection Manager) 2010 on some test servers. My setup is a server acting as a domaincontroller with SQL server and another server acting as the DPM server. Some information I found on Internet states that DPM could not be installed on the following servers.
- Domain Controller
- System Center Operations Manager
- Exchange Server
Also I found that “Cluster Services” must not be installed on the DPM server.
In the final stage of the installation a got the following error.
The Data Protection Manager error logs says:
“[7/27/2010 4:44:44 PM] Information : Add user: *****\SA_DPM to local group: DPMDBAdministrators$DPM on server: *****
[7/27/2010 4:44:45 PM] Information : Adding local group DPMDBReaders$DPM on server *****
[7/27/2010 4:44:45 PM] Information : Deleting local group DPMDBReaders$DPM on server *****
[7/27/2010 4:44:45 PM] * Exception : Ignoring the following exception intentionally => An error occurred while trying to configure DPM.Uninstall DPM by using Add or Remove Programs in Control Panel, and then run DPM Setup again.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: Exception of type ‘Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException’ was thrown.
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.SecurityConfigurationHandler.DeleteLocalGroup(String serverName, String localGroupName)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.SecurityConfigurationHandler.AddLocalGroup(String serverName, String localGroupName)
*** Mojito error was: DpmSetupConfigurationError; 2220; WindowsAPI”
It tries to add the domainaccount used for the installation to a “local group” on the server where the SQL server instance is located, huh… 😉
In my testsetup the domaincontroller also has the “remote” SQL server role, and localgroups does not exists anymore on that server. 🙂
That’s probably the reason I get this error. I will try some other configuration and update this post with the results. 🙂
I used the option to install SQL Server with DPM and the install finished properly.
I want to test the option with the remote SQL Server instance to. Keep you posted.