Call Quality Dashboard Config/Use
Posted on May 05, 2015 by Richard Brynteson in Skype for Business
The Call Quality Dashboard (CQD) is a new feature that allows you to have a new view of your CDR/QoE information. Unlike the existing Monitoring Server, this feature doesn’t require or rely on SQL Reporting Servers (SRS) but rather used the SQL SAAS Cube, Archive Database and a web portal.
EXPERT NOTE: Do not confuse the Skype for Business Archive database that is used as part of CQD offering. The archive database is a copy of your existing archiving data into another database. This database is used as the back end database used by the SAAS Cube.
The software ships as a separate download then the main SfB Server and is available on the Microsoft Download Page here.
It is important to know that you should deploy a separate server for the purposes of CQD and not attempt to re-provision another server as the performance hit of SAAS can be significant.
The setup and configuration of the server is well established here.
It boils down to a few main steps:
1) Install IIS Pre-Reqs
add-windowsfeature Web-Server, Web-Static-Content, Web-Default-Doc, Web-Asp-Net, Web-Asp-Net45, Web-Net-Ext, Web-Net-Ext45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Url-Auth, Web-Windows-Auth, Web-Mgmt-Console
2) Install SQL Server
- Product Install
This really boils down to three main areas within the configuration.
Here we indicate the the location that stores our existing Lync QoE Data. Second we specify the instance name of the QoE Archive server. Again, this is the server you just installed SQL Server and Analysis Server onto. You also must pick a location where to store the files. These should NOT be on your C (system) drive. The partition (single vs multiple) is based on if you installed Standard vs Enterprise. If you have a large amount of data you will see a significant performance increase by selecting multiple partitions/Enterprise SQL. Lastly, you must specify a username and password that has the correct permissions. In this instance it is read to Lync QoEMetric database and account that can login to the QoE Archive server (the one we are creating now).
On the Cube Configuration page you will specify the instance name of where the QoE Archive database is (NOT YOUR QoEMetrics Database). You also need to specify which server will run the cube analysis. In a larger deployment you might split the Archive DB and Cube to different servers. Lastly, you need to enter a user with the correct permissions. In this instance it is a user that will run permissions, read/write on the QoE Archive database.
On the Portal Configuration page you must specify the QoE Archive SQL Server (AGAIN, NOT THE QoEMetrics Server), Cube Analysis and Repository Server. This can be the same server in all three instances if you are doing a single server deployment. Additionally you must specify an account that will run as the portal user. Setup will create a login security principal to QoE Archive database (with read privilege), a login security principal to Repository database (with read and write privilege) , and a member in QoERole (with full control privilege) for the Cube.
EXPORT NOTE: The installation recommends that you use three different accounts for access. Clearly it is possible to use a single account. Outside of a strict security concern there isn’t a technical reason one account won’t work.
Using the Portal
At this point in time your portal is configured and should work. There are steps for configuring debug mode on TechNet (which you should do) and limiting access on the server. To access the server, simply browse to the URL (http://server.domain.com/CDQ/). You should see something very similar to this.
For the most part I have not run into many problems. You can check the health of your system by viewing the health page at http://server.domain.com/CQD/#/Health .
The largest issue I’ve seen is when I’ve needed to re-install the product because of corruption or upgrade. When attempting to re-install the product you can select to reuse the same QoE Archive database but on the Cube Configuration page you will be prompted that a QoECube already exists and you cannot continue.
To solve this problem:
- Launch SQL Management Studio
- Select Analysis Server and connect to your database.
Don’t pick Database Engine. You won’t find the object and the installer will continue to fail.
- Select the QoECube object and delete.
In the coming days I’ll be posting some neat tricks and how-to articles on using the Cube. It’s a powerful application that allows you to create your own reports. It doesn’t have nearly the feature set of paid products like EventZero or IRPrognosis but it certainly can insight then the standard reports.