DPM is 2012 R2. Trying to install on Server 2016 Running hyper-v. Error is id 347. I have tried the agent coordinator,.net 3.5 install and same issue. CHARBEL NEMNOM MVP - Cloud & Datacenter Management. To install DPM 2016 on Windows Server 2016. Data Protection Manager 2016. Installing Data Protection Manager. Mar 17, 2016 Hello friends Today I am going to show you how to install DPM (Data Protection Manager) 2012 R2 on Windows Server 2012 R2. In this demo I am going to use.

Although this question was originally asked in 2011, someone decided today, 5 years later, that it was a good idea to make a comment on a 5 year-old answer. Free Full Pc Games Download 2011 International Volleyball 2010 Html. Which was enough to make me to want to update my answer to reflect my more current views.

Since it still shows up in search results, I think it's worth making the answer more up-to-date. Several new versions of Windows and several new versions of Data Protection Manager have come out since you asked this question. Back in 2011, installing DPM on Server Core was difficult to impossible, depending on the version of DPM you were using, which specific components of DPM you were trying to install, (the agent or the server?) and your willingness to hack things like DCOM permissions to get it actually working. (And yes, there is still a lot of software, including Microsoft's own software, that doesn't run on Server Core because Server Core does not support the full.NET framework.

Especially not back in 2011, when this question was asked.) But, time has marched on and there have been new developments. If you're talking about installing the DPM Agent on Server Core, you'll find examples of people successfully, albeit not entirely hassle-free. Of even getting the agent installed on 2008 R2 core, again, with some extra fiddling required. In the archived (read: outdated) Microsoft documentation that you cited, 2008 R2 Core was supported as being able to install the agent even as far back as DPM 2010, however, the DPM 2010 server component itself was not supported on Core.

That link is a great compatibility matrix with regards to System Center 2016, including DPM. It shows that the agent can be installed on either Server Core or Server with 'Desktop Experience,' and the DPM Server component can be installed on Server Core as well, but the Remote Administration console still requires the 'Desktop Experience,' i.e., not Server Core. Hope that helps.

My 2012 server core wasn't allowing a push install of the DPM agent from the DPM 2012 server. I received errors about not being able to connect, etc. It turns out the windows firewall was blocking the installation. Simple enough, you can disable the firewall and try again, or you can use the below manual method of installation, thus keeping your firewall enabled. Find the agent installation files on your source 2012 DPM server. I found them here; c: Program Files Microsoft System Center 2012 DPM DPM agents RA 4.1.3408.0 amd64 1033 Copy the files to your target server. I chose to create a new folder, c: temp Connect remotely to the target server, open the cmd prompt and cd into the folder with your copied files.