Installing DPM 2012 R2 – the correct (and working!) way!

This tutorial explains how to install Data Protection Manager 2012 R2 (part of System Center suite). According my experience it is a bit complex process and it may failed if you not follow some additional steps. I saw many “click next” tutorials but none of them work well for me.

Here are the list of all steps:

  • Install prerequisities.
  • Install SQL server locally
  • Configure SQL Reporting services
  • Install DPM
  • Post-installation steps


.NET 3.5, .NET 4.0

SQL 2012 Standard (latest DPM 2012 R2 also can support SQL 2014)

Local account: MICROSOFT$DPM$Acct, member of admin and DCOM

Domain account: MICROSOFT$DPM$Acct, member of local admin and local DCOM

Install SQL server locally.

Components to install: Database Engine Services, Full-text and semantic extraction for search, Reporting services – Native, Management tools – select all (if you want to manage SQL server locally).

You can use named or default instance. Configure Engine, Agent and Reporting services with domain user account MICROSOFT$DPM$Acct, change all to Automatic.

Authentification: Windows mixed, all Domain Admins, local and domain MICROSOFT$DPM$Acct accounts.

Repoting services: Install only

Configure SQL Reporting services

Run Reporting Services Configuration Manager.

Click on Database, then on Change Database, Create a New Port server database, next with defaults.

Click on Web Service URL, click on Apply Button.

Click on Report Manager URL, click Apply button.

Install DPM server.

Run Setup under Administrator, click on Data Protection Manager. Click Next.

Enter the name of server in the “Instance of SQL server” if you install server with default instance.

Click on username, you don’t need to enter credentials. Click on Check and Install button. It will check the configuration of server, if necessary reboot server. Click Next.

Enter all information and the key. Click Next twice. Do not run Windows updates. Click Next. Then click on Install button to complete the process.

Post-installation steps.

Go to SQL server configuration manager, change domain account on Engine and Agent to local one. Otherwise your jobs will not start.

Make sure all installed agents have no sign “Reboot pending”. If so, just delete reg setting HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\2.0\Restart Pending and refresh agent.



Ssms.exe – SQL Management Studio (C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio)

RSconfigTool.exe – Reporting Services Manager (C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn)

You may also like


  1. Hello!
    Is it possible with DPM to use in different location with local storages in each location? Like the SCCM distribution points work.
    Can you give me any advice how can I do that if it is possible please?

    1. Hi Soltan!
      Thanks for your comment!
      Do you meant can DPM use the storage disks which are not installed locally? If so – my answer “No”. The alternative are tapes.

      Best regards,

  2. Hi Dimitry,

    I try to explain my idea / plan. We have a central site in Europe, but we would like to use the DPM solution in Asia also. So in this case how can I manage centrally the DPM? (Like as pssoible at the SCCM)?
    Thank you!

    1. Hi Zoltan!

      DPM doesn’t support concept “manage all servers from one console”. So you have to install DPM in Asia and manage it from console locally.
      There is another concept, but I believe it’s not what are you looking for. You can install DPM and configure then as primary and secondary. Primary server backup all data sources directly. The secondary DPM protects database and replicas of primary DPM.

      Hope it helps you.

      Best regards,

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.