Enabling Quality of Service (QoS) on Windows Server 2003 and Windows XP
Topic Last Modified: 2012-10-18
For Microsoft Lync 2010 and Microsoft Lync 2010 Attendant clients that run on the Windows Server 2003 or Windows XP operating system, you cannot use policy-based Quality of Service (QoS).
|For QoS to work on the client, the QoS Packet Scheduler must be running on the client computer, and Windows domain policies must allow the computer to use QoS services. For details about Windows Server 2003, see Install QoS Packet Scheduler at http://go.microsoft.com/fwlink/p/?LinkID=214341. For details about Windows XP, see QoS Packet Scheduler at http://go.microsoft.com/fwlink/p/?LinkId=214394.|
Log on to the computer as a member of the Administrators group.
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
At a command prompt, type the following command, and then press Enter:
Set-CsMediaConfiguration -EnableQoS $true
Use Group Policy to set Differentiated Services Code Point (DSCP) values that mark the IP packets if you need values other than the defaults to match your environment for Guaranteed service type packets (used for audio) and Controlled load service type packets (used for video). By default, the following settings are applied when you enable QoS:
SERVICETYPE_GUARANTEED (DSCP 40, 0x28)
SERVICETYPE_CONTROLLEDLOAD (DSCP 24, 0x18)
- SERVICETYPE_GUARANTEED (DSCP 40, 0x28)
Ensure the QOS Packet scheduler is enabled in all the network interfaces n this machine.
The client must be stopped and restarted for the change to take effect.