FIX: Monitoring Server Reports experiences poor performance in Lync Server 2010

Applies to: Lync Server 2010 Standard Edition

Symptoms


Assume that you deploy Monitoring Server Reports in a Microsoft Lync Server 2010 environment. If the Call Detail Recording (CDR) and Quality of Experience (QoE) databases are populated by more than 2,000 users, the out-of-the-box reports are delayed by 2 to 10 minutes. Additionally, Monitoring Server Reports experiences poor performance.

Resolution


To resolve this issue, download and install the following cumulative update:
2701663 Description of the cumulative update for Lync Server 2010, Core Components: June 2012

To install this cumulative update, follow these steps:
  1. Run the Lyncserverupdateinstaller.exe file.
  2. Upgrade and redeploy the Monitoring Server Reports pack. For more information about how to do this, go to the "More information" section.

    Note You must redeploy the monitoring pack as soon as the install-csdatabase –update command is run on the monitoring server.
  3. Upgrade the Monitoring database. For more information about how to do this, go to the "More information" section.

More Information


Upgrade Monitoring Server Report

To upgrade the Monitoring Server Reports pack, follow these steps.

Note You can apply these steps when you deploy Monitoring Server Reports for the first time.
  1. As a member of the DomainAdmins group, log on to any server in the domain that has the cumulative update installed.
  2. Run the Setup.exe file in the Lync Server 2010 installation folder or media to start the Deployment Wizard.
  3. In the Deployment Wizard, click Deploy Monitoring Server Reports.
  4. On the Specify Monitoring Server page, specify the Monitoring server that will collect and store the CDR and QoE data.
  5. On the Specify Monitoring Server wizard page, specify the instance of SQL Server Reporting Services that will publish the reports.

    Note To publish the reports, you must disable the Federal Information Processing Standards (FIPS)-compliant algorithm policy on the Reporting Services Server. Alternatively, you can apply the workaround that is described in the following Microsoft Knowledge Base article:
    911722 You may receive an error message when you access ASP.NET Web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
  6. On the Specify Credential page, specify the user credentials that will be used to access the Monitoring Server store (QoEMetrics and LcsCDR databases). For more information, go to the following MSDN website:
  7. On the Specify Read-Only group page, specify the domain group that will be granted read-only access to the Monitoring reports.

    Notes
    • This step is optional.
    • You can also configure the read-only group by using SQL Server Reporting Services.
    • This read-only group must exist to run the command successfully.
    • This read-only group refers to the local group on the computer that is running SQL Server Reporting Services. This is true even when you run the deployment remotely.
    • Do not include the computer name when you specify a read-only group.
    • Add users to this group to grant them the access to the reports.

Upgrade the Monitoring database

To upgrade the Monitoring database, follow these steps:
  1. As a member of the DomainAdmins group, log on to any server in the domain that has the cumulative update installed.
  2. Click Start, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
  3. Run the following Lync Server 2010 PowerShell command:
    Install-CsDatabase –DatabaseType Monitoring –update –sqlserverfqdn <MonitoringStoreBox> –sqlinstancename <SQL Server Instance Name>
    For example, the following command upgrades a Monitoring store that is installed on server01.contoso.com\Monitor:
    Install-CsDatabase –DatabaseType Monitoring –update –sqlserverfqdn server01.contoso.com –sqlinstancename Monitor
Important When you run the Install-CsDatabase command without the DatabasePaths parameter or the UseDefaultSqlPath parameter, as occurs in step 3, the command uses a built-in algorithm to determine the best placement for the log and data files. The algorithm works only for stand-alone SQL Server implementations. It is not intended for use on SQL Server clusters. SQL Server clusters should use either DatabasePaths to define the paths for log and data files, or UseDefaultSqlPath.

Note The articles that are listed in the "References" section contain more information about how to use the Install-CsDatabase Lync Server 2010 PowerShell command.

References


For more information about how to deploy Monitoring Server Reports, go to the following Microsoft website:For more information about how to plan for monitoring, go to the following Microsoft website:For more information about how to use the Install-CsDatabases PowerShell command, go to the following Microsoft website: