Introduction
An update is available for Microsoft Lync Server 2010 Monitoring Server to create a new report that is called Media Quality Comparison Report. The report provides a comparison view of the quality of audio calls. The comparison view reflects the difference in the quality of audio calls over the following types of connections:
-
VPN and non-VPN connections
-
Wired network and wireless network connections
-
Internal environment and external environment connections
This report helps an administrator to better troubleshoot an issue that is caused by VPN, wireless network or edge server configuration.
More Information
For more information about the cumulative update, click the following article number to view the article in the Microsoft Knowledge Base:
2740403 Description of the cumulative update for Lync Server 2010, Core Components: October 2012 To install the cumulative update, follow these steps:
-
Run the Lyncserverupdateinstaller.exe file.
-
Upgrade and redeploy the Monitoring Server Reports pack. For more information about how to do this, go to the "Upgrade Monitoring Server Report" section.NoteYou must redeploy the monitoring pack as soon as the install-csdatabase-update command is run on the monitoring server.
-
Upgrade the Monitoring database. For more information about how to do this, go to the "Upgrade the Monitoring database" section.
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.
-
As a member of the DomainAdmins group, log on to any server in the domain that has the cumulative update installed.
-
Run the Setup.exe file in the Lync Server 2010 installation folder or media to start the Deployment Wizard.
-
In the Deployment Wizard, click Deploy Monitoring Server Reports.
-
On the Specify Monitoring Server page, specify the Monitoring server that will collect and store the CDR and QoE data.
-
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. Additionally, 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
-
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:
Specifying credential and connection information for report data sources (SSRS)
-
On the Specify Read-Only group page, specify the domain group that will be granted read-only access to the Monitoring reports.Note
-
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:
-
As a member of the DomainAdmins group, log on to any server in the domain that has the cumulative update installed.
-
Click Start, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
-
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 Monito
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.If you have a coexistence topology that has Lync Server 2010 and Lync Server 2013, the only way to set or reset the URL for Lync Server 2010 Monitoring server is using the Lync Server 2013 Powershell cmdlet. Lync Server 2010 Powershell cmdlet does not work.For more information about how to deploy Monitoring Server Reports, go to the following Microsoft website:
How to deploy Monitoring Server Reports For more information about how to use Lync Server Management Shell for database installation, go to the following Microsoft website:
How to use Lync Server Management Shell for database installation For more information about the Get-CsAdminRole cmdlet, go to the following Microsoft website:
General information about the Get-CsAdminRole cmdlet For more information about a similar update for Monitoring Server, click the following article number to view the article in the Microsoft Knowledge Base:
2736037 An update enables a Monitoring Server to create a new report in a Lync Server 2010 environment
