Creating a Client QoS Policy

After modifying the Lync clients and servers to use specific port ranges, QoS policies must be created for the servers and clients to add the appropriate DSCP value to traffic originating from each port range. The steps required to use policy-based QoS through Group Policy are similar, but the port ranges used for servers and clients will likely differ. Create at least two separate policies: one for servers and one for clients. To create a new policy, perform the following steps:

1. Open a new Group Policy object.

2. Expand Computer Configuration, Windows Settings, and then click Policy-Based QoS.

3. Right-click Policy-Based QoS and select Create New Policy.

4. Enter a name for the policy, such as Lync Audio.

5. Enter a DSCP value, such as 46, and click Next.

6. For the client policy, limit the tagging only to Lync clients by selecting Only Applications with This Executable Name, and enter lync.exe. Do not specify an executable for the server policies. Click Next.

7. Allow the policy to apply to Any Source IP Address and Any Destination IP Address.

8. In the Select the Protocol This QoS Policy Applies To area, select TCP and UDP.

9. In the Specify the Source Port Number section, select From This Source Port Number or Range, and enter the range used for audio traffic, such as 50020:50039.

10. Click Finish to complete the policy.

11. Repeat these steps for each type of media using a unique port range, which should be tagged differently. Figure 14.5 demonstrates what a policy with separate audio and video settings looks like.

Image

Figure 14.5. Policy-based QoS.


Note

The A/V Edge Service behaves a bit differently. First, because it typically is not part of the domain, it might be necessary to create the policies locally on each server. Second, the port range used to define each service should be specified as a destination port instead of source port. This ensures that traffic passed between the Edge Server and the Front End pool is marked correctly. The defined port range used for the Front End or clients will always be a destination port range from the Edge Server’s perspective.


..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset