Unable to install DPM agent in the DC servers.

@Rajshekhar K G I hope you are doing well,

Welcome to Microsoft Q&A,

Installing protection agents on Domain Controllers frequently encounters Error 337 during console push due to AD hardening.

To get your DCs protected cleanly, follow the manual installation and attachment method, which is the recommended approach for Domain Controllers:

Step 1: Install the Agent Locally on the DC

1. On your MABS/DPM server, navigate to:

Plaintext

C:\Program Files\Microsoft Azure Backup Server\DPM\DPM\ProtectionAgents\RA\14.0.46.0\amd64

(or the equivalent DPM ProtectionAgents folder path).

1. Copy DPMAgentInstaller.exe to the Domain Controller.
2. Run an elevated Command Prompt on the DC and execute:

DOS

DPMAgentInstaller.exe

Step 2: Configure the MABS Server Name & Firewall on the DC

From the elevated Command Prompt on the DC, navigate to the DPM bin directory:

DOS

cd "C:\Program Files\Microsoft Data Protection Manager\DPM\bin"

SetDpmServer.exe -dpmServerName <Your_MABS_Server_FQDN>

(Make sure to use the FQDN of the MABS server, e.g., MABSSRV.domain.local).

Step 3: Attach the Agent from the MABS Console

1. Open the MABS / DPM Administrator Console.
2. Go to Management > Agents > click Install in the ribbon.
3. Select Attach agents (instead of "Install agents").
4. Choose Computers in a trusted domain, enter the DC's FQDN and domain admin credentials, and complete the wizard.

If Manual Attachment or Push Still Hits Access Denied:

• DCOM Security Permissions on DC: Run dcomcnfg on the DC > expand Component Services > Computers > My Computer > Properties > COM Security tab. Ensure ANONYMOUS LOGON and Authenticated Users have Remote Access / Launch permissions.
• Verify Admin$ Share Access: From the MABS server, verify you can access \DC2\Admin$ using the Domain Admin account without an access denied prompt.
• Remote Registry & MSDTC Services: Verify that both Remote Registry and Microsoft Distributed Transaction Coordinator (MSDTC) services are running on the DC.

References:

• Troubleshoot DPM/MABS protection agent installation issues
• Install the DPM protection agent manually

If this answer helped clarify the platform capabilities and save you troubleshooting time, please consider marking it as Accepted. This helps others in the community find similar solutions.

The issue was resolved.

We have performed all the suggested steps, but the problem was our MABS server was not part of the Administrator group in Active directory.We added our MABS server to the Administrator group, we were able to push the agent from console itself.