Utilizing some of the new capabilities in Operations Manager 2007 R2, such as PowerShell hosting and new monitoring templates, the new Exchange 2007 MP for Operations Manager 2007 R2 is now available for download from the System Center Catalog, as well as via the new web-service catalog from which Ops Mgr 2007 R2 can download MPs.

To highlight some of the key enhancements of this MP over its predecessors:

• Full, native implementation of the management pack, leveraging the latest capabilities offered in Ops Mgr 2007 R2, (e.g., basing health rollups on factors such as synthetic transactions, not just on component health, enabling alerting and response based on end-user impact).
• 60% reduction in noise-based alerts, enhanced by allowing the user to enable only the monitors and alerts that they require (as opposed to delivering the MP with all monitors turned on, whether needed or not).
• Integration with the Exchange BPA, providing a summary alert for deviations per Exchange Server.
• New wizard-driven monitoring templates simplify the ability to create synthetic transactions against Outlook Web Access (OWA), Exchange ActiveSync, Web Service, POP3 and/or IMAP.
• Visualization of synthetic transactions, allow rapid identification of where issues exist.
• Over 30 new/enhanced availability and performance reports against Service Level Objectives help identify alignment of service delivery against service targets.
• Full support for Microsoft Clustered configurations.

Unfortunately, the reinstallation of this product can be hampered by the modified state of the underlying SQL 2005 Reporting instance as well as a bug in the XML configuration file creation.

 

Here's a step-by-step guide that may help you reinstall the reporting component of SCOM R2:

 

1) Uninstall SCOM Reporting Server (using Add\Remove Programs)

2) Uninstall SQL 2005 Reporting (using Add\Remove Programs)

3) Open IIS Administrator and delete the Reports and ReportServer Web Sites (under the Default Web Site)

4) Issue an IISRESET command

5) Open SQL Server Management Studio and delete both the ReportServer and ReportServerTempDB databases

6) Reinstall SQL 2005 Reporting

7) Reapply SQL 2005 SP3

8) Configure the default Reporting instance using the Reporting Services Configuration utility

9) Using your browser, verify you can successfully connect to http://Reports/

10) If you get an error, select the Reports Web Site under IIS Admin and select Browse

11) If you get a "ReportServerVirtualDirectory missing" error, proceed with step 12; otherwise proceed to step 14

12) Edit the C:\Program Files\Microsoft SQL Server\MSSQL.n\Reporting Services\ReportManager\RSWebApplication.config file and change the line that reads <ReportServerVirtualDirectory></ReportServerVirtualDirectory> to <ReportServerVirtualDirectory>ReportServer</ReportServerVirtualDirectory>

13) Verify you can successfully connect to http://Reports/

14) Install SCOM R2 Reporting

15) Click on the Reporting pane in the Ops Console, select Reporting and Refresh the View to see the Reports (Reports may take a while to get loaded)