Managing and Monitoring System Center DPM 2012 with SCOM Part 2

In Part 1 of this blog series I walked through the steps to get the DPM 2012 Central Console components installed onto a SCOM Management Server.

This post will go through the next phase of the installation, covering the import of the DPM 2012 Management Pack into SCOM and making the necessary changes to your SCOM servers to allow for smooth operation of the DPM 2012 Central Console once it's integrated into your SCOM environment.

Once the Central Console installation is finished, you need to browse to your DPM installation location (generally it’s something like - C:\Program Files\Microsoft DPM). If all is going to plan, then we should now have a ‘Management Packs’ directory in here which contains the new DPM 2012 Management Packs for SCOM.

Now, open up your SCOM 2007 R2 console, go to the ‘Administration’ tab, right mouse click on ‘Management Packs’ and then click on the ‘Import Management Packs’ option from the flash out menu to open the ‘Import Management Packs’ wizard

From here, click on the ‘Add’button and then click on ‘Add from disk’

Click on ‘No’ from the screen below

Now in the ‘Select Management Packs to Import’ window, browse to the location of your DPM 2012 SCOM Management Packs and select them both. Now click on ‘Open’ to import them into SCOM

You should then see a security warning message coming back from one of the management packs – at this point, you can safely ignore this security warning and then click on ‘Install’

 Click ‘Yes’ from the confirmation window below

After a few seconds, the two management packs should be installed correctly

Once the Management Packs have installed correctly, click on 'Close' to exit the 'Import Management Packs' window

Now, staying within the SCOM Console, go back to the ‘Monitoring’ tab and then you should see a new management pack available called ‘Data Protection Manager 2012’ as shownindicating that the DPM 2012 Management Pack for SCOM has installed correctly

Before you start using the SCOM console to manage your DPM 2012 installations, you will need to possibly make some changes to your SCOM environment in the form of some overrides. You will also need to add 1 registry key to the Operations Manager Management Server and 3 additional registry keys to your DPM 2012 server.

Note: You DO NOT need to worry about creating the 4 overrides below in your SCOM environment if you have installed the most recent core ‘Operations Manager 2007 R2 Management Pack’ into your environment (you always keep your SCOM MP’s up to date right?). The new core MP for SCOM automatically updates these values within SCOM for the Management Server role so no need to change anything for your DPM 2012 install!

I highly recommend updating your SCOM MP’s on a regular basis and you can download the latest core ‘Operations Manager 2007 R2 Management Pack’ from here:

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=23081

The tables below are taken from the DPM 2012 BETA documentation and outline the changes required in your environment:

Post-Installation

If you are using an Operations Manager server to monitor the DPM servers, you must make the following overrides on the server running Operations Manager:

	Default	Override Value
Health Service Handle Count Threshold	2000	8000
Health Service Private Bytes Threshold	100MB	1GB
Monitoring Host Handle Count Threshold	2000	8000
Monitoring Host Private Bytes Threshold	100MB	1GB

Whether or not you had to make the above overrides to your SCOM environment, you will definitely need to make the following changes to the registry on your SCOM server and also your DPM 2012 server.

On the SCOM Management Server where you have the DPM 2012 Central Console installed, open up ‘Regedit’ and browse to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules\

Note: It is VERY IMPORTANT that you use the exact letter case size when specifying keys and DWORD entries. Make sure you use Capital letters exactly in the examples, otherwise it won’t work!
Now create a new ‘Key’ below the ‘Modules’ key called ‘Global’

Now create a new ‘Key’ below the ‘Global’ key called ‘PowerShell’

Finally, right mouse click on a blank space within the new ‘PowerShell’ sub-key and create the two new DWORD Values as specified below

Value: IsolationLevel  Type: dword   Data:00000000

Value: QueueMinutes  Type: dword   Data:00000077

On the DPM server, you need to make changes to two keys and four values.

Note: Before making the following changes, ensure that Operations Manager agent (not console) is installed on this computer.

On the DPM server open up ‘Regedit’ and browse to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules\

Note: It is VERY IMPORTANT that you use the exact letter case size when specifying keys and DWORD entries. Make sure you use Capital letters exactly in the examples, otherwise it won’t work!
Now create a new ‘Key’ below the ‘Modules’ key called ‘Global’

Now create a new ‘Key’ below the ‘Global’ key called ‘PowerShell’

Finally, right mouse click on a blank space within the new ‘PowerShell’ sub-key and create the two new DWORD Values as specified below

Value: IsolationLevel Type: dword Data:00000000

Value: QueueMinutes Type: dword Data:00000077

Now, still on the DPM server, within Regedit, you need to browse to the following location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HealthService\Parameters

Once here, you need to change the value for the ‘Persistence Version Store Maximum’ DWORD value to 0005dc00

Next, from the same screen, you need to right mouse click on a blank area and then select ‘New’ and then ‘DWORD (32 Bit) Value’ and then you need to name the new DWORD ‘State Queue Items’ with a value of 0x00001000 as shown below

For the final registry edit on the DPM server, browse to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HealthService\Parameters\Management Groups\<Management Group Name>

Now change the ‘MaximumQueueSizeKB’ DWORD value to 0x00019000 as shown below

That completes the registry edits on the DPM server and all that’s left to do now is to restart the ‘System Center Management’ service (Health Service) on the DPM server from the ‘services.msc’ snap-in to enable the new registry values.

If you have followed the steps in this post and also Part 1 of this series, you should now have the DPM 2012 Central Console installed and integrated into your SCOM Console with all of the relevant overrides and registry changes in place too.

In the final post of this series - Part 3 - I will demonstrate running some administrative tasks for DPM 2012 direct from the SCOM Console which will show a central management pane for both System Center products.