Topic Last Modified: 2010-06-23
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 reports are made available by a Web site that is published by the Report Manager.
The procedures below describe how to use Deployment Wizard to deploy Monitoring Server Reports. Before running this wizard, make sure that you have the sufficient permissions to:
- Create login and access database role to a user in Monitoring
Server database. This permission required to work with the SQL
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 more information, see Using Predefined Roles.
To deploy Monitoring Server
Reports
-
Log on to any server in the domain as a member of the DomainAdmins group.
-
From the Communications Server “14” installation folder or media, run Setup.exe to start the Deployment Wizard.
-
In the Deployment Wizard, click Deploy Monitoring Server Reports.
-
In Select Monitoring Server, specify the Monitoring Server that will collect and store the CDR and QoE data.
-
In Choose a SQL instance in which Reporting Services is installed, specify the instance of SQL Server Reporting Services that will publish the reports.
-
User Name and Password, specify the user credential used to access the Monitoring Server store (QoEMetrics and LcsCDR). For more info, please refer to http://msdn.microsoft.com/en-us/library/ms160330.aspx.
-
(Optionally) In Provide a read-only group, specify the domain or local group that will be granted read only access to the Monitoring reports. 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 computer. This is true even when you run the deployment remotely. Do not include the computer name when specifying 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.