If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...

If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting the computer for the protection agent to become available. Otherwise, troubleshoot the problem as follows: 1) Check the recent records from the DPMRA source in the Application Event Log on %ServerName; to find out why the agent failed to respond. 2) Verify that the DPM server is remotely accessible from %ServerName;. 3) If a firewall is enabled on the DPM server, verify that it is not blocking requests from %ServerName;. 4) If %ServerName; is a workgroup computer configured to use NETBIOS, ensure that the NETBIOS name of the DPM server is accessible from %ServerName;. Otherwise verify that the DNS name is remotely accessible.  5) If %ServerName; is a workgroup server, ensure that the DPM server has an IPSEC exception to allow communication from workgroup servers. 6) If %ServerName; is a workgroup server the password for the DPM user accounts could have been changed or may have expired. To resolve this error, run SetDpmServer with the -UpdatePassword flag on the protected computer and Update-NonDomainServerInfo.ps1 on the DPM server. 7) Restart the DPM Protection Agent service on %ServerName;. If the service fails to start, reinstall the DPM protection agent. 8) If %ServerName; is configured using certificates, ensure that the DPM CPWrapper service is running on DPM Server and %ServerName;. Also ensure that certificates used by both the computers are valid.