If you just installed an agent on %ServerName;, the server might be restarting. Wait a few minutes after Windows starts for ...

If you just installed an agent on %ServerName;, the server might be restarting. Wait a few minutes after Windows starts for the agent to become available. Otherwise, troubleshoot the problem as follows:
1) Make sure that %ServerName; is remotely accessible from the DPM server.
2) If a firewall is enabled on %ServerName;, make sure that it is not blocking requests from the DPM server.
3) Restart the DPM Protection Agent service on %ServerName;. If the service fails to start, re-install the protection agent.

If you have re-imported the management pack recently, the role configuration may be corrupted. Open the DPM-specific roles ... If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts ... If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts ... If you just installed an agent on %ServerName;, the computer might be restarting. Wait a few minutes after Windows starts ... If you just installed an agent on %ServerName;, the server might be restarting. Wait a few minutes after Windows starts for ... If you just installed an agent on %ServerName;, the server might be restarting. Wait a few minutes after Windows starts for ... If you just installed an agent on %ServerName;, the server might be restarting. Wait a few minutes after Windows starts for ... If you no longer want to protect any data sources on the computer, you can uninstall the protection agent from the computer. ... If you recently installed a protection agent on %ServerName;, the computer may be restarting. Wait a few minutes after restarting ...