Recently I have implemented Lync Monitoring Server in production environment. For Monitoring server we need to have a separate Server. We can collocate Monitoring server with Archiving server but not with Front end server /Mediation server.
Before deploying Monitoring Server you must install Message Queuing (also known as MSMQ), with Active Directory Domain Services Integration enabled, on the server running Monitoring Server and each Front End Server from which a Monitoring Server will collectdata. Monitoring Server uses Message Queuing to ensure reliability when processingdata.
Log on to the server that will be running Monitoring Server or the Front End Server using a user account with local administrator rights and Domain User permissions on the domain.
Click Start, point to Programs, point to Administrative Tools, and then click Server Manager.
Expand Message Queuing, expand Message Queuing Services, and verify that the Message Queuing Server and Directory Service Integration check boxes are selected.
Monitoring Server requires the Microsoft SQL Server database software to store the collected Quality of Experience (QoE) and call detail recording (CDR) data. Monitoring Server describes this data using a standard set of reports that are published by SQL Server Reporting Services. To view the reports, you must also install an instance of SQL Server Reporting Services.
In Topology Builder, right-click Monitoring and then click Define Monitoring Server.
In Monitoring Server FQDN, specify the FQDN for the Monitoring Server.
Select a SQL Server and instance from the list, if you are going to use an existing SQL Server or click Define SQL Store to create a new SQL Store reference.
On the computer on which you want to install Monitoring Server, log on using an account that is a member of the local Administrators group, is a domain user account that is a member of the RTCUniversalServerAdmins group, and has access permission for the SQL instance for the Monitoring database (or an account with equivalent user rights).
Start the Lync Server Deployment Wizard.
In the Lync Server Deployment Wizard, click Install or Update Lync Server System.
In Step 1: Install Local Configuration Store, click Run.
If you are running Monitoring Server as a stand-alone server role on the computer, you can skip Step 3: Request, Install or Assign Certificates. There are no special certificate requirements for the deploying Monitoring Server.
Before you start the services, verify that the LcsCDR database and QoEMetrics databases were created in the SQL Server instance that you specified for Monitoring Server. The two databases are used to store call detail recording (CDR) and Quality of Experience (QoE) data.
Monitoring Server contains a set of standard reports that are published by Microsoft SQLServer 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.
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.
In Specify Credential Page , specify the user credentials that you want to use to access the Monitoring Server database (QoEMetrics and LcsCDR).
(Optional) In Specify Read-Only group page, specify the domain group that you want to grant 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 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.