Monitoring Configuration

The good news about Lync Server 2013 is that with the Topology Builder tool much of the configuration is done automatically. Although both configuration and administration can be done from the Silverlight web GUI or the Lync Server Management Shell, the configuration section focuses on the former and the administration section focuses on the latter, to avoid duplication of concepts.

Open the Lync Server Control Panel. For reference, it can be found at the short URL you defined earlier, https://lyncadmin.companyabc.com/ in the sample environment, or https://<pool_FQDN>/Cscp/.

Scrolling down in the left bar, click on the Monitoring and Archiving button. This brings up the settings menus for the Monitoring and Achiving server roles. By default, there is only one Call Detail Recording policy. Select it and click Edit and then Modify. These are the available options:

• Name (the name of the policy)

• Enable Monitoring of Call Detail Records (CDRs)

• Enable Purging for Monitoring Servers

• Options for duration to keep CDRs and error reports

The next item across the top bar is the Quality of Experience (QoE) Data menu. Microsoft’s approach to measuring the user experience is through QoE data that provides qualitative and quantitative analysis of every call. It also provides some metrics around instant messaging and network type (VPN versus LAN versus WAN) as well. This also comes with one policy by default. The only option is whether to enable purging and, if so, how long to keep QoE data. By default, this value is set to 60 days.

The next step is to deploy the Monitoring Server reports to the SQL Reporting Server. This step can be done using the Lync Server Management Shell or from the main screen of the deployment wizard. From any of the Lync Server 2013 servers, open the Lync Server Management Shell and run as administrator. Where D is the drive letter assigned to your CD/DVD drive where the Lync installation CD/DVD/ISO is mounted, run the DeployReports.ps1 PowerShell script as this:

D:setupamd64setup eportingsetupDeployReports.ps1 -storedUserName <domainuser> -storePassword <password>

This is the most minimalist version of the command. The full syntax including optional items is outlined here:

Click here to view code image

DeployReports.ps1 -storedUserName <domainuser> -storedPassword <password>
-readOnlyGroupName <ReportReadOnlyGroupName> -reportServerSQLInstance
<ReportServerSQLInstance>

An explanation of each option is presented here:

• storedUserName—The username used to access the Monitoring Server store.

• storedPassword—The password for the value of storedUserName.

• readOnlyGroupName—The domain group that will be granted read-only access to the Monitoring Server reports. This group must already exist in Active Directory for the action to complete successfully.

• reportServerSQLInstance—The SQL instance that is hosting SQL Reporting Services. If this is left blank, the script assumes that it is the same server that holds the Monitoring Server databases.

Run the get-CsService -MonitoringServer cmdlet and pay special attention to the ReportingURL field. This is the URL where you’ll access the Lync Server reports. For the sample environment it would be this: http://mcssql.companyabc.com/ReportServer?%2fMCSReports%2fMCS+Reports+Home+Page. The reports themselves are covered in detail in the following section.