none
DPM Servers not reporting on SCOM. RRS feed

  • Question

  • I Installed SCOM and upgraded it to version 1807 as I want to use it monitor our 5 DPM server which are SAC 1807 version. 

    After upgrade, I notice as per the version mentioned by @leon on https://thesystemcenterblog.com/scom-build-versions/, it should be reflect below highlighted build number : 

    But in my case, console is showing version 1807, and when I see in program & features, it still reflect build number mentioned for 1801.

    I am not sure of there's any issue in upgrade I performed was with only 4 packages I am using this standalone SCOM. 

    Above is the case I am suspecting DPM servers are not showing in reporting tab after installing management packs. 

    I have installed management agents but DPM servers are showing not monitored. I read once agent is installed, DPM servers should reflect in reporting tab automatically under SCDPM management pack. 

    1. Is there any further configuration task I need to perform manually so DPM serevrs appears in reporting, or would they show automatically. 

    2. I can see DPM management packs only available up to 1801 on following link https://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx. Will they work for DPM 1807 as well ?

    3. Above mentioned scenario of SCOM build could be the reason DPM servers not reporting ?

    Below components were get installed when I installed management packs. 

    Friday, June 7, 2019 8:49 PM

Answers

  • Hello,

    It's normal behavior that the Control Panel still shows the SCOM 1801 build number, nothing to be concerned about, it actually also shows the 1801 build number in the Operations Console under Administration > Management Servers.

    1. Is there any further configuration task I need to perform manually so DPM serevrs appears in reporting, or would they show automatically. 

    Answer: There should not be any further configuration needed.

    2. I can see DPM management packs only available up to 1801 on following link https://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx. Will they work for DPM 1807 as well?

    Answer: The DPM 1801 management pack should work with DPM 1807 as well.

    3. Above mentioned scenario of SCOM build could be the reason DPM servers not reporting ?

    Answer: Your about screen shows that you have SCOM 1807 installed, so this should not be any reason for it not to work.


    Make sure you followed the instructions provided in the MPGuide_DPMReporting.docx which can be obtained from the DPM 1801 management pack download link.

    Install Instruction

    1. Uninstall any existing DPM MPs.
    2. InstallDPM Central Consoleversion using the guide here.
    3. Install SCOM Agents using Discovery wizard on all DPM Servers that you want to monitor using central console.
    4. Install latest MPs that came with this update
      1. Double click on the msi file that came with this update, accept the license agreement and click on Next.
      2. Select the installation folder and click on Next
      3. Click on Install
      4. It will extract the MP at selected folder

    1. In the SCOM Operations Console, right-click the Management Packs entry in the Administration view and Import the following Management Packs using “Add from Disk” option and browsing to the folder selected in Step 4.b
      • Microsoft.SystemCenter.DataProtectionManager.Discovery.MP(version 5.0.1400.0)
      • Microsoft.SystemCenter.DataProtectionManager.Library.MP(version 5.0.1400.0)
      • Microsoft.SystemCenter.DataProtectionManager.Reporting.MP(version 5.0.1400.0)

    Note: If you get an error while importing the Management Pack try to delete RTM version of Library and Discover & Monitoring MPs(version 5.0.1200.0) and then import the latest Management packs.

    The frequencies which the DPM management pack has for it's discoveries are very long, so you might have to be patient, but you can override these values as well.

    Default frequencies:

    • DPM server discovery - 21600 seconds = 6 hours
    • DPM data source discovery - 43200 seconds = 12 hours

    You can find all of these information on the System Center Wiki over here:
    https://systemcenter.wiki/?GetCategory=System+Center+Data+Protection+Manager+%28version+1801%29

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Proposed as answer by Leon Laude Tuesday, June 11, 2019 10:54 PM
    • Marked as answer by V Jay Rana Wednesday, June 12, 2019 9:40 PM
    Friday, June 7, 2019 9:59 PM

All replies

  • Hello,

    It's normal behavior that the Control Panel still shows the SCOM 1801 build number, nothing to be concerned about, it actually also shows the 1801 build number in the Operations Console under Administration > Management Servers.

    1. Is there any further configuration task I need to perform manually so DPM serevrs appears in reporting, or would they show automatically. 

    Answer: There should not be any further configuration needed.

    2. I can see DPM management packs only available up to 1801 on following link https://social.technet.microsoft.com/wiki/contents/articles/16174.microsoft-management-packs.aspx. Will they work for DPM 1807 as well?

    Answer: The DPM 1801 management pack should work with DPM 1807 as well.

    3. Above mentioned scenario of SCOM build could be the reason DPM servers not reporting ?

    Answer: Your about screen shows that you have SCOM 1807 installed, so this should not be any reason for it not to work.


    Make sure you followed the instructions provided in the MPGuide_DPMReporting.docx which can be obtained from the DPM 1801 management pack download link.

    Install Instruction

    1. Uninstall any existing DPM MPs.
    2. InstallDPM Central Consoleversion using the guide here.
    3. Install SCOM Agents using Discovery wizard on all DPM Servers that you want to monitor using central console.
    4. Install latest MPs that came with this update
      1. Double click on the msi file that came with this update, accept the license agreement and click on Next.
      2. Select the installation folder and click on Next
      3. Click on Install
      4. It will extract the MP at selected folder

    1. In the SCOM Operations Console, right-click the Management Packs entry in the Administration view and Import the following Management Packs using “Add from Disk” option and browsing to the folder selected in Step 4.b
      • Microsoft.SystemCenter.DataProtectionManager.Discovery.MP(version 5.0.1400.0)
      • Microsoft.SystemCenter.DataProtectionManager.Library.MP(version 5.0.1400.0)
      • Microsoft.SystemCenter.DataProtectionManager.Reporting.MP(version 5.0.1400.0)

    Note: If you get an error while importing the Management Pack try to delete RTM version of Library and Discover & Monitoring MPs(version 5.0.1200.0) and then import the latest Management packs.

    The frequencies which the DPM management pack has for it's discoveries are very long, so you might have to be patient, but you can override these values as well.

    Default frequencies:

    • DPM server discovery - 21600 seconds = 6 hours
    • DPM data source discovery - 43200 seconds = 12 hours

    You can find all of these information on the System Center Wiki over here:
    https://systemcenter.wiki/?GetCategory=System+Center+Data+Protection+Manager+%28version+1801%29

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    • Proposed as answer by Leon Laude Tuesday, June 11, 2019 10:54 PM
    • Marked as answer by V Jay Rana Wednesday, June 12, 2019 9:40 PM
    Friday, June 7, 2019 9:59 PM
  • Thanks Leon 

    The root cause I found was 'Run As Account' was not assigned 'Allow logon locally' on DPM serevrs and computers I installed agents on. I created policy and this is working now. 

    I found this following the steps you mentioned above so marking this as an answer as I see this is to be done sequentially and helps to analyze issues. :) 

    Wednesday, June 12, 2019 9:45 PM
  • Great to hear that!

    Note: For future reference, earlier version of Operations Managers has Allow log on locally as the default log on type. Operations Manager 2019 uses Service Log on by default.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, June 12, 2019 10:19 PM
  • Thanks again. 

    I have another little query, I am trying to optimize it's dashboard so it's easy to manage by our other engineers. I found a cool dashboard MP https://gallery.technet.microsoft.com/SCOM-DPM-Dashboard-8eef9b58 which is supported on DPM 2012 SP1/R2 only. Is there anything same supported for 1807/2016 DPM or SCOM. 


    • Edited by V Jay Rana Wednesday, June 12, 2019 10:55 PM
    Wednesday, June 12, 2019 10:43 PM
  • As far as I know there are none for the DPM 2016/1807 versions, but you can either create your own dashboards within SCOM or create an own management pack :-)

    It might be something that I might be looking in to in the future.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, June 12, 2019 11:01 PM