Implementing the Skype for Business Call Quality Dashboard

Abstract: This short HowTo will outline the steps needed to install the Skype for Business (=SfB) Call Quality Dashboard

Preparation:

– Download the SfB Call Quality Dashboard installer from here and store it on the sfbcdq01 server

– Install a supported SQL version on the sfbcdq01 server (We will use SQL 2012 Standard in this howto). You need “Database Engine Services”, “Analysis Services”, the full “Management Tools”. During installation the AD account which is used should be added to the administrator section. You later one can change that. Once done start the SQL Server Agent and set that to automatically.

– Create an 2nd AD account (contoso\SfBCQDPortal). Grant him also administrator access on sfbcdq01

Steps:

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.) Download and install (on the Call Quality Dashboard server) the following SQL features from here:

SQL_AS_AMO.msi

4.) run the SfB Call Quality Dashboard installer (you can find more details here)

 

B.) QoE Archive SQL Server Instance:the The local SQL Server instance name for where the Archive DB is to be created. Leave this field blank for the default SQL instance installed on the current server.

D.) Database File Directory: location where the new database files are to be created. Recommended a separate disk volume, so change the folder to “D” instead “C”

F.) SQL Agent Job User: AD User Name & Password which is used to connect to the QoEmetrics database and replicate the QoEArchive

4f.) the next is the “Cube Configuration”

A.)  QoE Archive SQL Server Instance: SQL Server instance name for where the QoE Archive DB is located. To specify a default SQL Server instance on the current server, leave this field blank.

C.) Partition: ‘Multiple partition’ requires Business Intelligence edition or Enterprise edition of SQL Server. ‘Single Partition’ only requires for a Standard edition (but cube processing performance may be impacted) which must be selected here.

After that press on “next”

B.) Cube Analysis Server: SQL Server Analysis Service instance name for where the cube is located. If Cube component was selected for the install, this field will be pre-populated with the value provided on the Cube Configuration page.

D.) Repository Database: By default the option is set to “Create new database”. Since Repository DB upgrade is not supported, the only circumstance under which the “Use existing database” option can be used is if the existing Repository DB has the same schema as the build to be installed.

4h.) Press “Install”

4i.) Press “Finish” to close the installer.

5.) Now add a https binding to the server and assign an SSL certificate to it. For security reasons you can now also remove the http binding

6a.) Create a local  group on the server called “CQDPortalUsers”. You can use the GUI or use powershell:

6b.) Now add the users (e.g. AD user) you need to the local AD group

According to the Microsoft Technet, the next step is to configure the dashboard of the CQD. After users are authenticated by IIS, they will have to have file permissions on the CQD directory in order to access the web portal content. It is possible to change the ACLs through the security tab of the CQD directory properties to add individual users or groups; however the recommended approach is to leave the file permissions untouched. Instead, change the IIS setting to use the IIS worker process to access the CQD directory no matter which user is authenticated.

If you wish to troubleshoot something you can configure the debug mode in the QoEDataService/Web.config as written here.

As the accounts we use have administrator access you might wish to finetune that and lower the needed rights for security purpose.

Follow the Post-install tasks here now. For more infos how to use the DashBoard, check the Microsoft Website here.

SSL encryption for an SQL Server instance

Leave a Reply

Your email address will not be published. Required fields are marked *