Deploy Monitoring Server Reports (Recommended)

Monitoring Server contains a set of standard reports that are published by Microsoft SQL Server Reporting Services. The reports are made available by a Web site that is published by the Report Manager.

After you have started the Monitoring service, you can deploy the Monitoring Server Report Pack to an instance of the Microsoft SQL Server Reporting Services. This step is optional.

Note:
To deploy the Monitoring Server Report Pack, you must first install SQL Server Reporting Services. For details, see Install SQL Server Reporting Services. Additionally, the account that you are logged on with must be assigned to the Content Manager role of the Reporting Services instance that you will deploy the report pack to. For details about assigning users to a SQL Report Services role, see Creating and Managing Role Assignments .

Note:

To deploy the Monitoring Server Report Pack, you must first install SQL Server Reporting Services. For details, see Install SQL Server Reporting Services. Additionally, the account that you are logged on with must be assigned to the Content Manager role of the Reporting Services instance that you will deploy the report pack to. For details about assigning users to a SQL Report Services role, see Creating and Managing Role Assignments .

To deploy Monitoring Server Reports

In the Deployment Wizard, at Step 4: Deploy Monitoring Server Reports, click Run.
On the Welcome to the Monitoring Server Report Pack Deployment Wizardpage, click Next.
On the Specify Report Pack Accountpage, type the name of a new or existing service account to use for this server, type the password for the account, and then click Next.

Note:

The default account is RTCReportPack. For a new account, use a strong password that meets the Active Directory password requirements of your organization.

Note:
The default account is RTCReportPack. For a new account, use a strong password that meets the Active Directory password requirements of your organization.

On the Report Pack Configurationpage, type the URL of the reporting server, and then click Next.

Caution:
You can publish the reports only to an HTTPS Web site. When you publish the reports, you must use the name of the reporting server within the URL. Before you deploy the report pack, ensure that Ignore client certificatesis selected for the Web site. After you have finished deploying the report pack, you can change the Client certificatessetting if you’d like.

On the Authorize Grouppage, do one of the following:

To grant read-only access for Monitoring Server reports to a domain group, select the group’s domain in Select domain, and type the name of the group in Name of existing group.
To not grant access to any groups, click Skip this step. If you do this, you can manually configure access after you have deployed the report pack, as described following this procedure.

Note:
If the Monitoring Server report pack is deployed onto a SQL Server Reporting Server that is in a different domain in the forest, then domain local groups cannot be used to grant read-only access. In this case, you can use only global or universal groups.

Caution:
Members of this domain group will be granted read-only access to personal identifying information, such as the URIs and phone numbers of callers and callees, in the Call Detail Recording (CDR) and Quality of Experience (QoE) database.

On the Ready to Deploy Report Packpage, click Next.
When the wizard has completed, select the View the log when you click Finish check box, and then click Finish.
In the log file, verify that Successappears under the Execution Resultcolumn. Look for Successat the end of each task to verify that the report pack was deployed. When you are finished, close the log window.

You can now view reports by using the Reporting Services instance that you specified in the wizard. The format of the URL will be https://< fqdn>/reportserver?%2fOCSReports.

Note:
Because the reporting server uses a different service account than that for Monitoring Server, you will need to ensure that you change the passwords of both the reporting server and Monitoring Server accounts before they expire. In addition to the service accounts, the data source of the Monitoring Server report pack uses stored credentials to access the Monitoring database. When you change the password for this account, you must also update the stored credentials of the data source. The data source of the report pack can be found in the OCSReports folder of the report pack. To access, open http(s)://<FQDN>/Reports.

Note:

Because the reporting server uses a different service account than that for Monitoring Server, you will need to ensure that you change the passwords of both the reporting server and Monitoring Server accounts before they expire.

In addition to the service accounts, the data source of the Monitoring Server report pack uses stored credentials to access the Monitoring database. When you change the password for this account, you must also update the stored credentials of the data source. The data source of the report pack can be found in the OCSReports folder of the report pack. To access, open http(s)://<FQDN>/Reports.

To manually configure read-only access to reports

At the URL that you specified on the Report Pack Configurationpage during the previous procedure, open the SQL Reporting Services page.
Click the OCSReportsfolder.
Click the Propertiestab.
Click Security.
Click New Role Assignment.
In the New Role Assignmentpage, type the name of the group or user to whom you want to provide read-only access in the Group or user namebox.
Select the OCS Reports Browsercheck box, and then click OK.