Troubleshooting protection agents
Updated: November 1, 2013
Applies To: System Center 2012 R2 Data Protection Manager, System Center 2012 SP1 - Data Protection Manager, System Center Data Protection Manager 2010
Before you start troubleshooting System Center 2012 – Data Protection Manager (DPM), consider whether any of the following blocking issues might apply to your situation. For more information about resolving issues with agents, see Troubleshooting DPM Installation.
DPM protection agent will not install on a computer
Is the computer connected to the network and can it be remotely accessed from the DPM server?
Both the DPM server and the computer to be protected must be connected to the network during installation of a protection agent.
Does the protected computer have a supported Windows operating system installed?
Verify the operating system on the computer to be protected.
Is a firewall enabled on the computer to be protected that could be blocking requests from the DPM server?
If a firewall is enabled, you need to configure the firewall to allow communication between the DPM server and the computer to be protected. For information about configuring the firewall, see Configuring Windows Firewall on the DPM Server
Is a firewall enabled on the DPM server?
If a firewall is enabled, you need to configure the firewall to allow installation of a protection agent on the computer.
Has a previous version of the protection agent already been installed on the protected computer?
You cannot install two versions of the protected agent on the same protected computer.
Is the Remote Registry service running on the computer to be protected?
The Remote Registry service must be running on both the DPM server and the computer before you can install a protection agent. In Administrative Tools, start the Remote Registry service and then install the protection agent.
Is Remote Procedure Call (RPC) unavailable?
RPC must be available. See Microsoft Knowledge Base article 555839, Troubleshooting RPC Server is Unavailable in Windows.
Is the boot volume on the computer formatted as file allocation table (FAT)?
Convert the boot volume to NTFS file system if you have sufficient space.
DPM protection agent will not uninstall from a computer
Is the protected computer disconnected from the network?
To uninstall a protection agent, the protected computer must be connected to the network.
Was the protected computer renamed or moved to another Active Directory domain after the protection agent was installed?
To uninstall a protection agent, the protected computer must have the same name and be in the same domain as it was when the protection agent was installed.
Uninstall the agent locally, and then remove the entry from DPM Administrator Console.
DPM protection agent is incompatible with DPM or other software
Did you upgrade the DPM software without updating the protection agent?
To determine whether an agent update is available, check the Agents tab in the Management view.
Did you upgrade a protection agent by using Microsoft Update before DPM received the corresponding server update?
Because Microsoft Update can occur automatically, ensure that the protection agent and DPM are compatible.
An error occurred when the agent operation attempted to communicate with the DPM Agent Coordinator service on the specified computer
Did you check the COM permissions?
Verify COM permissions on the protected computer. See Troubleshooting Protection Agent Installation.
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.