Check out the most comprehensive, actively managed Lync blog roll in the known universe, your one-stop source for links to over 100 of the very best Lync blogs. Here you will also find weekly blog highlights and a feed for a dozen of the top blogs.
Lync Server Support Home
Top Lync Solutions RSS Feed
Microsoft Senior Support engineers walk you through real-life support cases, giving you an insider’s view into the systematic approach they use to troubleshoot Lync Server issues.
These short videos focus on specific tasks and show you how to accomplish them for Microsoft Lync Server 2010.
Abstract: This article leads the reader through the process of enabling DSCP marking for Windows access computers that run the Lync 2013 VDI Plug-in to deliver a great audio and video experience on networks where QoS has been deployed.
Author: Lester Hewett
Technical Review: Kaushal Metha
Publication date: October 2013
Product version: Lync 2013
I have recently joined Microsoft Services working in the Enterprise Communications Centre of Excellence in EMEA, I have worked on a number of Lync 2013 VDI Plug-in deployments and wanted to share some key learnings relating to configuring the Lync 2013 VDI Plug-in to run in a QoS enabled environment.
Lync 2013 VDI Plug-in and QoS
The first great thing to understand is that the QoS planning and subsequent PowerShell configuration to separate out the media streams that you already have in place to support your Lync 2013 deployment will be honoured by the Lync 2013 VDI Plug-in.
If you are just starting on configuring Lync 2013 support for QOS, the following planning topic may be beneficial: “Managing Quality of Service (QoS)” at http://technet.microsoft.com/en-us/library/gg405409.aspx.
The second great thing to understand is that the method you used to configure the Windows Packet Scheduler to mark Lync media packets for the Lync 2013 client will be reused also with some minor changes.
The key thing to keep in mind is that the Lync 2013 VDI Plug-in is exactly that, a plug-in installed on the local access computer. The Lync 2013 VDI Plug-in runs on the local access computer and pairs with the Lync Desktop Client running on the remote virtual machine through Remote Desktop Client session. Once you have deployed the Lync 2013 VDI Plug-in onto the local access machine, you will not find a lync.exe process but you will find mstsc.exe, the Remote Desktop client when pairing is successfully established.
So let’s assume that you have already configured your Lync 2013 platform so that your media ports used by the clients are as follows and you have agreed the Differentiated Services Code Point (DSCP) marking scheme with the network team (here we have allocated 100 TCP and UDP ports per modality).
40803 to 40903
DSCP Marking 24
49152 to 49252
DSCP Marking 46
57501 to 57601
DSCP Marking 34
We are assuming that your Windows local access computers are domain joined so all that we need to do now is to create a new Group Policy Object to target our local access computers running the Lync VDI Plug-in so we can apply the DSCP marking scheme simply and consistently. This process is defined in “Configuring Quality of Service Policies for Clients Running on Windows 7 or Windows 8” at http://technet.microsoft.com/en-us/library/jj205371.aspx.
After you have created the QoS policy for Lync VDI audio you should then create policies for App Sharing and Video.
Save the new GPO and ensure you apply it to the target OU, either reboot the local access machines with or run gpupdate /force once the GPO is available.
Confirmation of Success
We are going to look for two confirmation points:
The first thing to check is that your GPO has applied correctly, go to the local access computer, sign in and open up a command prompt (if you are using a locked down thin client you may need to follow the manufacturer’s procedure to sign in as an administrator before you gain access to the command prompt).
Type gpresult /h c:\temp\report.html
Once the report has been created, open it and search for the name of your GPO (Lync VDI DSCP Marking in our example and confirm it has applied correctly).
The following screen shot shows a Netmon packet capture showing the DSCP marking enabled on an audio packet from the local access machine (192.168.1.112).
Once you have confirmed all is well, take the opportunity to make yourself a nice cup of tea!
Configuring Port Ranges for Your Microsoft Lync Clients at http://technet.microsoft.com/en-us/library/jj204760.aspx
Configuring Quality of Service Policies for Clients Running on Windows 7 or Windows 8 at http://technet.microsoft.com/en-us/library/jj205371.aspx
Installing the Lync 2013 VDI Plug-in at http://technet.microsoft.com/en-us/library/jj204683.aspx