This blog is to outline the supported configurations for Operations Manager Reporting and help align this to the supported configurations of SQL Reporting Services.
Note: This does not cover the OperationsManagerDW component. For information on the high availability solutions for the OperationsManagerDW see - http://technet.microsoft.com/en-us/library/bb309428.aspx
Install Notes: Operations Manager Reporting is fully supported in this configuration.
Install Notes: Operations Manager Reporting is not supported in this configuration as OM Reporting installs a custom security extension as part of the setup of the front end components which cannot be replicated across the web farm.
Install Notes: Operations Manager Reporting is not supported in this configuration. There is an issue during Operations Manager Reporting upgrade that causes the upgrade to fail if the ReportServerDBs are not on the first installed node when the upgrade is performed. Aside from this issue Operations Manager will work as expected in this scenario.
Based on the above the first 2 are the supported options. For high availability scenarios we would recommend Option 2 and combine this with the recovery knowledge found in the Operations Guide which easily shows how to recover from a failure in the reporting components.( http://download.microsoft.com/download/7/4/d/74deff5e-449f-4a6b-91dd-ffbc117869a2/OM2007_OpsGuide.doc )
PingBack from http://aceddl.cn/x/operations-manager-reporting-%c2%96-supported-ssrs-configurations.jsp
Is there an updated version of this for SCOM and SQL 2012?