I was recently tasked with setting up a DPM 2010 environment to troubleshoot a customer issue. When attempting to deploy the DPM agent from the DPM Administrator console, I received an error 349. “An error occurred when the agent operation attempted to transfer agent installation files to <server name>. Review the error details, take the appropriate action, and then retry the agent operation.” In my case the DPM Server and protected agents were all Windows Server 2008 R2. The out of box firewall settings do not allow DPM Server and agent to communicate. When running the "Protection Agent Installation Wizard" I noticed the "Install Agent" option is for computers where required firewall settings have already been configured. Since I did not know what those setting should be, I opted to execute agent installer manually from a share on the DPM Server to resolve issue.[Option A]\\%DPMServer\c$\ProgramFiles\Microsoft DPM\DPM\ProtectionAgents\RA\3.0.7696.0\amd64\DPMAgentInstaller_x64.exe %DPMServerName%If you do not pass in the DPMServer name you may need to run the second command on the protected server to update/create firewall rules.
[Option B]C:\Program Files\Microsoft Data Protection Manager\DPM\bin>SetDpmServer.exe -DPMServerName %DPMServerName%
[Output from command line]Configuring dpm server settings and firewall settings for dpm serverConfiguration completed successfully!!!
After the commands were executed I was successfully able to manage agents from DPM Administrator Console. Reviewing Windows Firewall with Advanced Security shows several new inbound rules for dpmra.exe.
[DPM 2010 Error Code Catalog]http://technet.microsoft.com/en-us/library/ff399290.aspx
Each DPM QFE comes with a new version of the agent and is installed on the DPM server under C:\Program Files\Microsoft DPM\DPM\agents\RA\<version> folderFor instance KB 2250444 agent is under the 3.0.7706.0 folder and KB 2465832 is under 3.0.7707.0 folder. You can use the agent from the QFE version or the RTM version defined above, then update the agent to the latest under the DPM agents console – it will say update available, just click the link and it will automatically install the latest agent.
Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
The name of agen installer executables seem to have changed with a recent DPM update to DPMAgentInstaller_KB2250444_AMD64.exe and DPMAgentInstaller_KB2250444.exe.
Could somone confirm that?
Yes, the DPM Support team has confirmed. I added a note at the bottom of the blog with their comments on your question.