Quality of Service (QoS) is a combination of Network technologies that allows the administrators to optimize the experience of real time Audio/Video and application sharing communications.

Configuring QoS for Skype for Business on the Surface Hub can be done through MDM or through Provisioning Package.

In this article we will focus on the Mobile Device Management (MDM) configuration using Microsoft Intune.

Here are the main steps to follow:

1.You first need to create a custom policy in Intune:

2. Next you can start configuring the source ports for audio, after checking with your Skype administrator:

3. Configure the DSCP marking for audio:

4. Source ports for video:

5. Configure the DSCP marking for video:

6. Then you need to configure the originating process name which for the Surface Hub is Microsoft.PPISkype.Windows.exe, first for audio:

7. The same process needs to be followed for video:

8. After all settings have been configured, your policy should look like this:

Here is a summary of a test policy we created:

Once the policy has been created, make sure it is deployed to the Surface Hub and the Surface Hub has synced the Settings. As reference, please check this article.

A note to this:

Currently you cannot configure the settings IPProtocolMatchCondition. If this parameter is configured, the policy will fail to apply. This is something we are working on and expect to have a fix in the February update. The same update is expected to also fix the issues you might have experienced with applying QoS Settings via Provisioning Package.

     %windir%\explorer.exe shell:::{80F3F1D5-FECA-45F3-BC32-752C152E456E}

• Save the following lines as script.ps1 on your Desktop:

  # // first argument is mapped to $url
  param($url)
  
  [Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
  [System.Uri] $u = New-Object System.Uri($url)
  [Net.ServicePoint] $sp = [Net.ServicePointManager]::FindServicePoint($u)
  [System.Guid] $groupName = [System.Guid]::NewGuid()
  
  # // create a request
  [Net.HttpWebRequest] $req = [Net.WebRequest]::create($url)
  $req.Method = "GET"
  $req.Timeout = 600000 # = 10 minutes
  $req.ConnectionGroupName = $groupName
  
  # // Set if you need a username/password to access the resource
  #$req.Credentials = New-Object Net.NetworkCredential("username", "password")
  
  [Net.HttpWebResponse] $result = $req.GetResponse()
  $sp.CloseConnectionGroup($groupName)
  $fullPathIncFileName = $MyInvocation.MyCommand.Definition
  $currentScriptName = $MyInvocation.MyCommand.Name
  $currentExecutingPath = $fullPathIncFileName.Replace($currentScriptName, "")
  $outfilename = $currentExecutingPath + "Export.cer"
  [System.Byte[]] $data = $sp.Certificate.Export([System.Security.Cryptography.X509Certificates.X509ContentType]::Cert)
  [System.IO.File]::WriteAllBytes($outfilename, $data)
  Write-Host $outfilename

  Note - We left out the last line in the original script, as we don't need to add the certificates on the machine where we are running the script. We will package the certificates up and deploy them on the Surface Hub.
• Start PowerShell As Administrator and navigate to the path where you saved the PowerShell script and run the following command: .\script.ps1 https://lyncdiscoverinternal.yoursipdomain.com Note - make sure you put https:// in front of the lyncdiscover record, otherwise the script will fail
• The script will save the certificate chain (Export.cer) to the same location where the script is located (Desktop)
• Open the certificate chain and go to "Certification path"
• You will need to export the root and intermediate (if there is one) certificates and save them locally. Please note that the server certificate does not need to be saved, just the certificates above it, in the chain
• Double click the certificate you want to save, go to Details, and select "Copy to File"
• Select DER encoding (.CER)
• Once you saved the certificates locally, create the Provisioning package using Imaging and Configuration Designer (see the admin guide for more details)
• The Root CA goes into RootCertificates, and the Intermediate CA goes into CACertificates Note - All certificates that are part of the chain need to go into one package
• Build the package and deploy it to the device

Note: Before deploying the new package to the Hub, make sure you first remove the packages that were installed for this same purpose. After the old packages are removed, reboot the device. Install the new package containing the correct certificates, then reboot the device again.

• Requirements for the Lync Windows Store App
• Requirements for Lync mobility
• Requirements for media traffic