Deploying Monitoring Server Reports

Topic Last Modified: 2011-03-17

Monitoring Server contains a set of standard reports that are published by Microsoft SQL Server Reporting Services. In order to use these reports, you need to install Monitoring Server Reports on an instance of SQL Server Reporting Services. The Report Manager publishes the reports to a website.

The following procedures describe how to use Lync Server Deployment Wizard to deploy Monitoring Server Reports. Before running this wizard, make sure that you have the sufficient user rights and permissions to do the following:

Create a user account that has SQL Server sysadmin access rights to the Monitoring Server database.
Deploy reports to SQL Server Reporting Services, which requires both the SQL Server Reporting Services Content Manager role and System Administrator role. For details, see "Using Predefined Roles" at http://go.microsoft.com/fwlink/?LinkId=187491.

The minimum set of user rights and permissions must include local server administrator, domain user, RtcUniversalServerAdmins, and monitoring database (SQL Server Reporting Services) read/write permissions.

To deploy Monitoring Server Reports

Log on to any server in the domain as a member of the DomainAdmins group.
From the Lync Server 2010 installation folder or media, run Setup.exe to start the Lync Server Deployment Wizard.
In the Lync Server Deployment Wizard, click Deploy Monitoring Server Reports.
In Specify Monitoring Server Page, specify the Monitoring Server that you want to collect and store the call detail recording (CDR) and Quality of Experience (QoE) data.

In Specify Monitoring Server Page, specify the instance of SQL Server Reporting Services that will publish the reports.

Note:
In order to publish reports, you need to either disable the Federal Information Processing Standard (FIPS) compliant algorithm policy on the Reporting Services Server or apply the workaround described in Microsoft Knowledge Base article 911722, "You may receive an error message when you access ASP.NET webpages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0," at http://go.microsoft.com/fwlink/?LinkId=196183.

Note:

In order to publish reports, you need to either disable the Federal Information Processing Standard (FIPS) compliant algorithm policy on the Reporting Services Server or apply the workaround described in Microsoft Knowledge Base article 911722, "You may receive an error message when you access ASP.NET webpages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0," at http://go.microsoft.com/fwlink/?LinkId=196183.

In Specify Credential Page , specify the user credentials that you want to use to access the Monitoring Server database (QoEMetrics and LcsCDR).

Note:

For details, see "Specifying Credential and Connection Information for Report Data Sources (SSRS)" at http://go.microsoft.com/fwlink/?LinkId=203152.

Note:
For details, see "Specifying Credential and Connection Information for Report Data Sources (SSRS)" at http://go.microsoft.com/fwlink/?LinkId=203152.

(Optional) In Specify Read-Only group page, specify the domain group that you want to grant read-only access to the Monitoring reports.

Note:
You can also configure the read-only group directly in SQL Server Reporting Services. Local group refers to the local group on the computer running SQL Server Reporting Services. This is true even when you run the deployment remotely. Do not include the computer name when you specify a local group. You can add users to this group to grant them the access to the reports. The read-only group must exist to run the command successfully.

Note:

You can also configure the read-only group directly in SQL Server Reporting Services.

Local group refers to the local group on the computer running SQL Server Reporting Services. This is true even when you run the deployment remotely. Do not include the computer name when you specify a local group.

You can add users to this group to grant them the access to the reports. The read-only group must exist to run the command successfully.