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?)
Thanks a ton! Same thing just happened to us.
Does this use Kerberos by default for auth ?
No, it uses NTLM. You can follow this guide to switch Reporting from NTLM to Kerberos:
https://blakedrumm.com/blog/how-to-change-reporting-to-use-kerberos-instead-of-ntlm/
Thanks a lot. You’re the best source of information for all SCOM topics. 🙂
Fantastic and Excellent KB on SCOM . It worked for us..
Afternoon Kevin, did’nt you write a short item about reinstalling SCOM Reporting, something about changing a version number in one of the DB, installing then changing it back?
I am trying to reinstall the Reporting piece but keep getting errors about SSL (which there is currently none), and other issues. Could you please point me to something useful for this? I have an incident open, waiting for a call.
Case 2610020040004734 Your question was successfully submitted to Microsoft Support TrackingID#2610020040004734
Thank you so very much!
Tony