I retired a management server – now SCOM reporting doesn’t work?




When you first install reporting, you have to supply a management server.  This is used for SDK based connections that SCOM reporting requires.  If you ever retire this management server, reporting will break so this is an additional step to ensure you check whenever you retire a MS.


There are three places you need to update to a new management server:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\Reporting\DefaultSDKServiceMachine

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\DefaultSDKServiceMachine

and TWO places in the file:

rsreportserver.config on your SSRS server path similar to:  \Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer


(You could always just uninstall SCOM reporting and reinstall it somewhere else…. but that would be a bit drastic, don’t you think?)

Comments (3)

  1. Arthur Silvany says:


    If I replace the name of the management server by the nlb name?Will it work?

    1. Kevin Holman says:

      Yes, and we have several customers who do that.

      Just be aware – that any in place upgrades will often break/fail if you do that – so you have to add a step to any upgrade scenarios to change these back to an actual management server before starting an upgrade process (like SCOM 2012R2 to SCOM 2016 in place upgrade)

      1. Hey Kevin, talking about in place upgrades (from SCOM 2012 to 2016), other than in reporting, anywhere we need to change/update if we are using NLB name?

Skip to main content