Take the pain away from manual deployment – grab the agent and put it into SCCM. The command lines for agent install (2016 UR2) are:
DPMAgentInstaller_KB3209593_AMD64.exe /q /IAcceptEULA
DPMAgentInstaller_KB3209593.exe /q /IAcceptEULA (for x86)
Just make sure all the agent pre-reqs are in place (WMF 4.0 for 2008 R2 etc…) and make the detection of those a pre-req for the SCCM deployment.
If you know what DPM server you are going to protect with – simply add the server name to the install above – that will open the ports and make the agent ready to be attached.
If you dont just yet – then run a second SCCM task to call a batch file running the setdpmserver.exe (in the DPM agent Bin directory) to configure the agent.
Run an “Application deployment type compliance details” report in SCCM, using your target collections, application, deployment type and status of “Success” to generate a CSV file of the installed agents.
Take the computer name column in excel, append your domain name (using concatenate) and put the resulting list into a .txt file (no headings or any other info required)
Open the DPM console – select Install, Attach Agents, click add from file and point to your txt file.
Output from SCCM report, manipulate and import in ~10 mins saving many hours of manual config.