I have a SCOM 2007 R2 installation in my test environment and a colleague (Islam Gomaa) and myself are presenting on DPM 2010 protecting Hyper-V R2 and monitoring the solution using SCOM 2007 R2.
I imported the DPM 2007 Management Pack but out of the box, the DPM 2010 servers do not get discovered.
In order to discover these servers, some digging was required.
In the Authoring Pane, select Object Discoveries and Change the target type to DPM Server.
From here, you can view the properties of the DPM 2007 server discovery.
The issue lies in the script below:
The script is called DPMServerDiscovery.vbs. You can search for it under %Program Files%\System Center Operations Manager 2007\Health Service State\
It will be in a numbered folder under a Monitoring Host Temporary Files folder.
First, back up the script for safe keeping.
To determine what the product code for DPM 2010 is, you need to search the registry.
From the Agent system where DPM 2010 is installed, launch regedit.
Next, do a search for ProductCode. You may have to bypass a few irrelevant hits…
You will find your target as below:
The registry key should be: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10.MSDPM2010EVAL\Setup\. Right click ProductCode and select Modify to copy the key value.
Paste the copied value in the script above.
Now, to force the discovery…
By default, the discovery runs every 28800 seconds or every 8 hours.
Override the DPM Server discovery to some value to make it run soon. That should do it. See below:
Your DPM Server should now get picked up and members of the DPM Server group will also become populated.
Don’t forget to put the discovery interval frequency back to 28800 seconds. Happy hunting!