Read more about File Share Delivery in SQL Reporting Services documentation.

Reference to a view or a task is a regular RDL Hyperlink that points to a specially formatted URI. This formatting lets SCOM console to treat it as an execute a view or a task command rather than a report drill-down. There is a ConsoleIntegration class that helps in formatting console links correctly. This class is defined in the SCOM reporting code extension library (Microsoft.EnterpriseManagement.Reporting.Code.dll) that is shipped with the product and installed into Report Server Bin directory during setup. You need to reference this library to make it available for the report code to call.

<CodeModules>
    <CodeModule>Microsoft.EnterpriseManagement.Reporting.Code, Version=6.0.0.0, Culture=neutral</CodeModule>
</CodeModules>

After the library is referenced you can start using it. Here is an example that references State view from a report:

<Textbox Name="textbox">
    ...
        <Action>
            <Hyperlink>= Microsoft.EnterpriseManagement.Reporting.ConsoleIntegration.CreateConsoleViewLink(
                                    Fields!ManagementGroupGuid.Value,
                                    "Microsoft.SystemCenter.StateView",
                                    Fields!ManagedEntityGuid.Value)
            </Hyperlink>
        </Action>
    ...
</Textbox>

ConsoleIntegration class defines a set of overloads for links. Here is the list:

string CreateConsoleViewLink(
  Guid managementGroupId,
  string viewName,
  Guid viewTarget)

string CreateConsoleViewLink(
  string managementGroupId,
  string viewName,
  string viewTarget)

string CreateConsoleTaskLink(
  Guid managementGroupId,
  string taskName,
  Guid taskTarget)

string CreateConsoleTaskLink(
  string managementGroupId,
  string taskName,
  string taskTarget)

Since data warehouse can collect data for multiple management groups "managementGroupId" is a required parameter for all calls.

The important thing to remember is that these links make sense only in a context of SCOM console. They will fail to execute in case you try to clink on them in default SQL Report Manager interface. To avoid these failures you need to make sure you declare Interactive parameter in your report. SCOM console always sets this parameter to True when the report is executed in the console.

<ReportParameter Name="Interactive">
    <DataType>Boolean</DataType>
    <Nullable>true</Nullable>
    <DefaultValue>
        <Values>
            <Value>=False</Value>
        </Values>
    </DefaultValue>
    <Prompt>Interactive</Prompt>
    <Hidden>true</Hidden>
</ReportParameter>

The last step is to make sure you use the parameter to hide hyperlinks in the report.

<Visibility>
    <Hidden>=Parameters!Interactive.Value &lt;&gt; True</Hidden>
</Visibility>

• Service Level Tracking reporting.
  First step towards solving a problem of service level monitoring. Service Level Tracking "contract" along with tracking objectives needs to be created before the report could be run but they can use existing state and performance data that is already collected by the system.
• Saving reports to a Management Pack.
  Now in addition to saving reports to Favorites and Publishing reports you can also save reports to a management pack. This solves a problem of sharing published reports with all reporting users in the organization. Reports get deployed to SSRS automatically after the management pack is imported in the system. Delete saved reports functionality is obviously also there.
• Class filtering for report object picker.
  The feature allows filtering down search results to only certain classes of objects. Filter settings are available under "Options" button for both "Add Objects" and "Add group" functions.
  This feature has most value when the list of supported classes is defined in a management pack. Not all the management packs take advantage of this feature though yet.
• Reporting support in Authoring console.
  Authoring console now has a new "Reporting" space and exposes all available reporting elements including Reports, linked reports, scripts and resources. This feature for sure should simplify custom repot authoring a lot. There is no integrated editor for RDL and RPDL but existing files could be easily uploaded there.
• Improved search interface for performance rules.
  Additional fields had been added to the search dialogs to help distinguish rules with the same name.
• Multi-selection parameters for Most Common Events report.

Using the Microsoft Generic Report Library
This video demonstrates generic overrides report.
Running Time (minutes): 6:16

Using favorite reports and the report publishing feature
This video demonstrates favorite reports and report publishing features.
Running Time (minutes): 6:44

1. Make sure SCOM 2007 Reporting is installed.
   
2. Copy MicrosoftRSChart.dll and MicrosoftRSChartDesigner.dll from SSRS bin directory to Visual Studio private assemblies directory on your development machine.
   
   Location of SSRS bin directory depends on the way you install SQL Sever but usually the path looks like this: \Program Files\Microsoft SQL Server\MSSQL.N\Reporting Services\ReportServer\bin
   
   Visual Studio private assemblies directory usually could be found under \Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies
   
3. Find RSReportDesigner.config file in the Visual Studio private assemblies directory and add the following records to it:

   <Configuration>
       <Extensions>
               ...
               ...
   
           <ReportItemDesigner>
               <ReportItem Name="EnterpriseManagementChartControl"
                       Type="Dundas.ReportingServices.DundasChartDesigner,
                                 MicrosoftRSChartDesigner" />
           </ReportItemDesigner>
           <ReportItems>
               <ReportItem Name="EnterpriseManagementChartControl"
                       Type="Dundas.ReportingServices.DundasChart,
                                 MicrosoftRSChart" />
           </ReportItems>
           <ReportItemConverter>
               <Converter Source="Chart" Target="EnterpriseManagementChartControl"
                       Type="Dundas.ReportingServices.RSChartConverter,
                                 MicrosoftDundasRSChartDesigner" />
           </ReportItemConverter>
   
       </Extensions>
   </Configuration>

4. Restart Visual Studio.

Please note that these steps will only work with SCOM 2007 SP1 RC or later releases. The files mentioned here were not a part of SCOM 2007 RTM.

SP1 RC is adding several interesting reporting features to the product. Here are some of them:

• Ability to view favorite reports in the Web Console.
• Report publishing functionality.
• Brand new Overrides report.
• Basic data warehouse capacity planning using data warehouse properties report.
• Improved availability reporting by introducing new "Monitoring Available" state.

If you haven't done this already I highly recommend reading "Linked availability reports" and "Linked reports" posts before continue. They cover some theory behind linked reports authoring. Reading "Report parameters block" and "Report parameter controls" could also be useful in understanding RPDL part of the story.

RuleId, SortOrder and TopCount are parameters that are customizable for "Performance Top" reports. "Performance Top Objects" report also has an additional RuleInstance parameter. This parameter is not valid for "Performance Top Instance" report since the rule instance is the result of the report rather then a filter.

RuleId

This parameter defines the rule report operates on. If you look at the actual report code (RDL file) you find that this parameter is in fact GUID of a performance rule in SCOM management group installation. You may ask me how could I know a GUID of the rule in a particular management group at the time of management pack authoring? The answer is you can't. Instead you should use a special $MPElement syntax which allows referencing of management pack elements by a system name at authoring time. $MPElement reference is resolved and converted to GUID automatically at the time of report deployment. Here is an example:

<Parameter Name="RuleId">
  <Value>$MPElement[Name="SQL!Microsoft.SQLServer.2005.NumberDeadlocksPerSecond"]$</Value>
</Parameter>

SortOrder

This parameter switches report algorithm. Here is the list of possible values:

TopCount

This is "N" value for the SortOrder parameter. Specify any positive number here but be reasonable. Setting the value too high can make the report chart unreadable.

RuleInstance

As I said before this parameter only valid for "Performance Top Objects report". It is used in cases where you know an instance or a set of rule instances you like to include in the report filter criteria.

<Parameter Name="RuleInstance">
  <Value>A</Value>
  <Value>B</Value>
  <Value>C</Value>
</Parameter>

Now when we know all these parameters it is a snap to define the lined report. As usually you should not forget about parameter definition for the new report. To simplify the process just copy and paste context of the Microsoft.SystemCenter.DataWarehouse.Report.PerformanceTop.rpdl or Microsoft.SystemCenter.DataWarehouse.Report.PerformanceTopInstance.rpdl. In most cases however you can choose to remove some parameter controls from the block to disallow users changing the parameters you specified. The most common control to disable is the rule picker, but you can choose to remove TopCount and/or SortOrder as well. Here is the complete example:

<LinkedReport ID="Demo.Bottom10DeadlockedDatabases"

        Accessibility="Public" Visible="true" Base="Reporting!Microsoft.SystemCenter.DataWarehouse.Report.PerformanceTop">

   <ParameterBlock columns="2" xmlns="https://schemas.microsoft.com/mom/reporting/2007/ReportParameterSettings">
      <Controls>
        <Control type="Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.RelativeDateTimePicker">
          <ReportParameters>
            <ReportParameter name="TimeZone" binding="TimeZone">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.TimeZone
              </Prompt>
            </ReportParameter>
            <ReportParameter name="TimeZoneName" binding="TimeZoneName" />
            <ReportParameter name="StartDate_BaseType"
                             binding="StartDate_BaseType" />
            <ReportParameter name="StartDate_BaseValue"
                             binding="StartDate_BaseValue">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.StartDateTime
              </Prompt>
            </ReportParameter>
            <ReportParameter name="StartDate_OffsetType"
                             binding="StartDate_OffsetType" />
            <ReportParameter name="StartDate_OffsetValue"
                             binding="StartDate_OffsetValue" />
            <ReportParameter name="EndDate_BaseType"
                             binding="EndDate_BaseType" />
            <ReportParameter name="EndDate_BaseValue"
                             binding="EndDate_BaseValue">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EndDateTime
              </Prompt>
            </ReportParameter>
            <ReportParameter name="EndDate_OffsetType"
                             binding="EndDate_OffsetType" />
            <ReportParameter name="EndDate_OffsetValue"
                             binding="EndDate_OffsetValue" />
          </ReportParameters>
        </Control>
        <Control type="Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.ComboBox">
          <ReportParameters>
            <ReportParameter name="ManagementGroupId">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.ManagementGroup
              </Prompt>
            </ReportParameter>
           </ReportParameters>
         </Control>
     </Controls>
   </ParameterBlock>

  <Parameters>

    <Parameter Name="RuleId">

      <Value>$MPElement[Name="SQL!Microsoft.SQLServer.2005.NumberDeadlocksPerSecond"]$</Value>

    </Parameter>

    <Parameter Name="SortOrder">

      <Value>1</Value>

    </Parameter>

    <Parameter Name="TopCount">

      <Value>10</Value>

    </Parameter>

  </Parameters>

</LinkedReport>

So here is a script to create a new Report Operator user role using Command Shell:

$mg = (get-item .).ManagementGroup
$reportOperator = $mg.GetMonitoringProfiles() | where {$_.Name -eq "ReportOperator"}
$obj = new-object Microsoft.EnterpriseManagement.Monitoring.Security.MonitoringUserRole

$obj.Name = "TestReportOperatorRole"
$obj.DisplayName = "Test Report Operator Role"
$obj.Description = "Test Report Operator Role"
$obj.MonitoringProfile = $reportOperator

$mg.InsertMonitoringUserRole($obj)

After you execute this script “Test Report Operator Role” appears in UI and you would be able to add users to it using User Role Properties dialog.

Performance Detail report could be either run directly or as a drill down from the Performance report. The report shows detailed performance chart along with a summary table below. If you choose to display histogram in the parameter block a “Detail Table” link appears inside the summary table. The link allows you to see a value table the chart is based on.

Unfortunately in RTM version of SCOM the “Detail Table” link is disabled for non-histogram reports. However if you export this non-histogram report to Excel or XML format the value table will be exported as well and could be easily viewed or used in your custom application.

One important thing to understand in linked report authoring is that objects should never be used as a hard-coded parameters to your reports. Monitoring objects are specific to a particular SCOM management group installation and could not be known at the time the management pack is created.

Monitor and downtime states on the other hand are things that are well known at the authoring time. Hard-coding them could be quite useful in cases where you either want to look at the particular monitor or when your organization has some specific rules around downtime definition.

Let's say we like to create an availability report based on ping status assuming that device is not available when the monitor is in down or warning states. Here is a definition of such report:

<LinkedReport ID="Demo.ComputerPingHealth"

    Accessibility="Public" Visible="true" Base="Reporting! Microsoft.SystemCenter.DataWarehouse.Report.Availability">

  <Parameters>

    <Parameter Name="MonitorName">

      <Value>Microsoft.SystemCenter.Ping</Value>

    </Parameter>

    <Parameter Name="DownTime">

      <Value>2</Value>

    </Parameter>

  </Parameters>

</LinkedReport>

Notice that we put only value 2 for DownTime parameter even though I said we will consider both monitor down (red) and warning (yellow) states as downtime. This is because "monitor down" state is always considered as downtime regardless of what we specified it in the DownTime parameter.

Here is the list of  all possible values for the DownTime parameter:

The last thing to do is to create parameter definition for the new report. To simplify the process just copy context of the Microsoft.SystemCenter.DataWarehouse.Report.Availability.rpdl there. Here is the result:

<LinkedReport ID="Demo.ComputerPingHealth"

        Accessibility="Public" Visible="true" Base="Reporting!Microsoft.SystemCenter.DataWarehouse.Report.Availability">

   <ParameterBlock columns="4" xmlns="https://schemas.microsoft.com/mom/reporting/2007/ReportParameterSettings">
      <Controls>
        <Control type="Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.ComboBox">
          <ReportParameters>
            <ReportParameter name="DataAggregation">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.DataAggregation
              </Prompt>
            </ReportParameter>
           </ReportParameters>
         </Control>
         <Control type="Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.MonitoringObjectXmlPicker" columnSpan="2" rowSpan="2">
          <ReportParameters>
            <ReportParameter name="ObjectList">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.ObjectList
              </Prompt>
            </ReportParameter>
            <ReportParameter name="ManagementGroupId" binding="GroupList"/>
          </ReportParameters>
         </Control>
         <Control type="Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.CheckedListBox" rowSpan="2">
          <ReportParameters>
            <ReportParameter name="DownTime">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.AvailabilityDownTime
              </Prompt>
           </ReportParameter>
         </ReportParameters>
        </Control>
        <Control type="Microsoft.SystemCenter.DataWarehouse.Report.ParameterControl.BusinessRelativeDateTimePicker">
          <ReportParameters>
            <ReportParameter name="TimeZone" binding="TimeZone">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.TimeZone
              </Prompt>
            </ReportParameter>
            <ReportParameter name="TimeZoneName" binding="TimeZoneName" />
            <ReportParameter name="StartDate_BaseType"
                             binding="StartDate_BaseType" />
            <ReportParameter name="StartDate_BaseValue"
                             binding="StartDate_BaseValue">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.StartDateTime
              </Prompt>
            </ReportParameter>
            <ReportParameter name="StartDate_OffsetType"
                             binding="StartDate_OffsetType" />
            <ReportParameter name="StartDate_OffsetValue"
                             binding="StartDate_OffsetValue" />
            <ReportParameter name="EndDate_BaseType"
                             binding="EndDate_BaseType" />
            <ReportParameter name="EndDate_BaseValue"
                             binding="EndDate_BaseValue">
              <Prompt>
Microsoft.SystemCenter.DataWarehouse.Report.Library!Microsoft.SystemCenter.DataWarehouse.Report.ParameterPrompt.EndDateTime
              </Prompt>
            </ReportParameter>
            <ReportParameter name="EndDate_OffsetType"
                             binding="EndDate_OffsetType" />
            <ReportParameter name="EndDate_OffsetValue"
                             binding="EndDate_OffsetValue" />
            <ReportParameter name="TimeType" binding="TimeType" />
            <ReportParameter name="TimeWeekMap"
                             binding="TimeWeekMap" />
          </ReportParameters>
        </Control>
     </Controls>
   </ParameterBlock>

  <Parameters>

    <Parameter Name="MonitorName">

      <Value>Microsoft.SystemCenter.Ping</Value>

    </Parameter>

    <Parameter Name="DownTime">

      <Value>2</Value>

    </Parameter>

  </Parameters>

</LinkedReport>