Data Protection Manager - Setup and Agent management announcement

We have had several reports of having trouble installing the DPM 2016 agent on Windows server 2008 and Windows Server 2008 R2 systems.

The symptoms vary depending on how the installation / upgrade is performed but below is a common error if installing it manually:

The program can’t start because mi.dll is missing from your computer. Try reinstalling the program to fix this problem

The file MI.DLL is part of Windows Management Framework Infrastructure and is installed by Windows Management Framework (WFM). Either WFM is not installed or the installation is corrupt and missing some files.

Another symptom is when you attempt to "Attach" an agent you get an error saying it cannot start DPMAC service which is also caused by not having WMF installed on the protected server.

System Center DPM 2012 is not supported running on Windows Server 2012. We have had reports of DPM 2012 console crashes when navigating to the recovery tab if DPM 2012 is installed on Windows server 2012. This issue is fixed in System Center 2012 SP1 which supports being installed on Windows 2012 operating system.

If you are already in this condition, you have two options:

A) You can upgrade to System Center 2012 Sp1.

B) You can backup the DPMDB, rebuild the DPM server using Windows 2008 R2 install DPM 2012, then restore your current database. The process is explained in the below technet article.

We also do not support protecting Windows Server 2012 workloads using SCS DPM 2012, you must upgrade to DPM 2012 Sp1. Please do not expect any support for DPM 2012 running on Windows Server 2012, or issues while protecting data sources in Windows Server 2012.

Data Protection Manager - Setup and Agent management announcement

We have had several reports of having trouble installing the DPM 2016 agent on Windows server 2008 and Windows Server 2008 R2 systems.

The symptoms vary depending on how the installation / upgrade is performed but below is a common error if installing it manually:

The program can’t start because mi.dll is missing from your computer. Try reinstalling the program to fix this problem

The file MI.DLL is part of Windows Management Framework Infrastructure and is installed by Windows Management Framework (WFM). Either WFM is not installed or the installation is corrupt and missing some files.

Another symptom is when you attempt to "Attach" an agent you get an error saying it cannot start DPMAC service which is also caused by not having WMF installed on the protected server.

System Center DPM 2012 is not supported running on Windows Server 2012. We have had reports of DPM 2012 console crashes when navigating to the recovery tab if DPM 2012 is installed on Windows server 2012. This issue is fixed in System Center 2012 SP1 which supports being installed on Windows 2012 operating system.

If you are already in this condition, you have two options:

A) You can upgrade to System Center 2012 Sp1.

B) You can backup the DPMDB, rebuild the DPM server using Windows 2008 R2 install DPM 2012, then restore your current database. The process is explained in the below technet article.

We also do not support protecting Windows Server 2012 workloads using SCS DPM 2012, you must upgrade to DPM 2012 Sp1. Please do not expect any support for DPM 2012 running on Windows Server 2012, or issues while protecting data sources in Windows Server 2012.