Installing Monitoring server role in Lync 2013/SFB in SQL remote instance

In this article we will have a look at configuring the monitoring server role for enterprise deployment  in a remote instance for Lync Server 2013 and SFB.

If you want to monitor Lync Server 2013/SFB  and Lync Client 2013 you need deploy Lync Monitoring server role.

As an overview deploying the monitoring role into an Existing Lync enterprise deployment would look easier. Un proper planning according to your environment and  installation will result you in Empty reports.

But when we look into the real time practical scenarios the situation changes on each and every environment basis according to your SQL setup.

So we cannot follow the installation  as such  unless and until we are clear on the SQL configuration.

In this article based out of my real time experience I will post few points and tips:

1) Before installing the monitoring server role ,You need to deploy the monitoring server and then you need to deploy the monitoring reporting service.

2) For that your Lync Admin user account should have SYSADMIN on the SQL server (assigned through SQL Server Management Studio > Security > Logins).

3) Lync only supports Windows Authentication.  So the remote SQL Server instance  you have chosen to install the monitoring role  will need Windows Authentication enabled, similarly user who launches topology builder needs to have permissions to create/edit databases and access the SRS you have configured.

https://exchangequery.files.wordpress.com/2015/11/lync-security.png?w=600

Make sure the use windows credentials is selected.

https://exchangequery.files.wordpress.com/2015/11/lync20133.png?w=600&h=150

4) You need to have  lcsqoeq and lcsCDRQ on the public queues of Message Queuing accessible from the Lync Server so that it can pull the data and show you the reports.

For example you can try accessing the reporting services instance you configured from the Lync Monitoring server and the configured SRSS should show as below.

https://exchangequery.files.wordpress.com/2015/11/lync20132.png?w=600&h=184

5) The lync monitor server name (NETBIOS) should not be more than 15 characters
If this is the case MSMQ will not able to deliver the messages

Basically the approach should be the below:

a) First you need to configure the SRS instance on your remote SQL.
b) Install the SQL reporting services.You’ll have to run the SQL report server setup wizard to define the report server URL. usually sql.domain.com/reportserver_lync
c) Define the monitoring server in the topology.
d) Publish the topology.
e) And then install the reports from the installation wizard.

f) Make sure the Lync server monitoring services is started, and the connectivity is good with SQL server

g) Make sure that your SSRS instance SQL version (version and SP level) match the SQL version of your database instance that has the monitoring databases.

h) You should verify that the LcsCDR database was created in the SQL Server instance that you specified for Monitoring Server.

i) You need to run the dbo.RtcRecreateSummaryTable once the databases are created from the management studio.

Very IMP: You need to make sure that you are allowing the required ports for the SRS URL.

Example if you have multiple SRS configured on a SQL enterprise farm like one for Archive solution use a different port rather than 80 since the other application will be using this port.

Make sure that you are able to access the webpage of the report service URL from the Monitoring  server you are trying the installation

Usually the URL would be your SQL server the port you defined and then the reports

Example :- http://SQL:8888/reports

If you have multiple applications using the SRS then you need to create the URL for the Lync and make them to listen on different ports. Also you can see the other instances created under this location.

https://exchangequery.files.wordpress.com/2015/11/5678.png?w=600&h=315

If its not accessible then you are having an issue with the permission with the account you have logged in on the SQL Server.

Finally a healthy report should look like below:

https://exchangequery.files.wordpress.com/2015/11/lync201331.png?w=600&h=480