Wednesday, October 12, 2011

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:



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.

10 comments:

  1. Hello i had this problem
    on my DPM server the SCOM health service was stoping automaticaly.

    I created the above registry keys and the issue is resolved.
    I still wonder how that happned

    ReplyDelete
  2. Any chance these Management packs will work for SCE 2010?

    ReplyDelete
  3. Hi Jason,

    The SCDPM 2012 management packs should install into SCE 2012 as it's effectively SCOM 2007 R2 - which they do work with.

    The caveat though, is that the central administration console will definitely NOT work with SCE 2010 so you'll miss out on a whole raft of integration there unfortunately.

    SCE 2010 isn't high on the radar of Microsoft's System Center roadmap (there's no plans for any future SCE releases as far as I'm aware) and you won't be getting any new updates for it anytime soon.

    Hope this helps,

    Kevin.

    ReplyDelete
  4. Hello, Kevin!
    Thanks for the post. I am trying to monitor SCDPM 2012 with SCOM 2007 R2. At first, after importing MPs I also had the problem, where health service was stopping, so I changed registry keys, and Health Service started to work normally. However, I know get error - The PowerShell script failed with below exception

    System.Management.Automation.RuntimeException: The term 'Connect-DPMServer' is not recognized as the name of a cmdlet, function, script file, or operable program.

    I tried to run Connect-DPMServer locally on DPM server, and it connected successfully.

    Do you have any suggestions? Thank you in advance!

    ReplyDelete
    Replies
    1. Hi Janis,

      Try installing the DPM 2012 management console onto the SCOM 2007 server. The error means that it doesn't understand the new DPM 2012 PowerShell commands and by installing the console it should deploy the new shell module including the commands.

      Hope this helps!

      Kevin.

      Delete
    2. Hi Kevin,

      The alert source is DPM server, so I'm pretty sure, that discovery script is failing on DPM server.

      I also tried to extract discovery script from agent cache and put exact same commands in my powershell script - it connected successfully.

      However, just to be sure, I tried your advice and installed DPM management console on SCOM server, stopped Health service on DPM server, cleared agent cache, started health service, and alerts shown up again.

      Delete
    3. Hi,

      In case you are still wondering about this problem, I could solve it by setting execution policy of DPM server to "Bypass". This command is executed on DPM server and if your server like mine is following a domain group policy by default, it will not load DPM powershell module for any user, in this case the account that is running the agent.
      Hope this will help.

      Delete
  5. Can DPM 2012 be monitored with SCOM 2007 R1? I'm currently running SCOM 2007 not 2007-R2 and don't have a plan of upgrading it in the near future.

    Thanks!

    ReplyDelete
    Replies
    1. Hi there,

      You should be able to import the DPM 2012 management pack into SCOM 2007 R1 but you won't be able to install the DPM Central Console for management. I would strongly advise planning for a migration over to SCOM 2012 as the benefits and new features far outweigh any hassle that you might incur carrying out the intial deployment.

      Kevin.

      Delete
  6. I did not see the "Data Protection Manager 2012 Management Pack" when I select "Download Management Packs" in my SCOM 2007 R2. Is there a URL to download the "Data Protection Manager 2012 Management Pack" only ?

    ReplyDelete