At Zoom, we are hard at work to provide you with the best 24x7 global support experience during this pandemic. As part of this ongoing commitment, please review our updated Support Guidelines.

QoS DSCP Marking Follow


Quality of Service (QoS) DSCP Marking is used to determine traffic classification for network data. This can be used to determine which network traffic requires higher bandwidth, has a higher priority, and more likely to drop packets.

The default Zoom DSCP marking values are 56 for audio, 40 for video, and 40 for screen sharing. You can update audio and video values to allow a network administrator to adjust the priority for Zoom traffic on their network.

If your organization deploys Zoom via an MSI installation, the MSI must be re-deployed after configuring the DSCP markings. If the DSCP markings are ever changed, the MSI will need to be re-deployed.


  • Zoom Desktop Client for Mac, IT Admin deployment (.pkg). 
  • Zoom Desktop Client for Windows, IT Admin deployment (msi)

Note: If Zoom is deployed via the .msi installation, it will need to be run as administrator, for the DSCP Marking to take effect. However, if you are using Group Policy to manage the DSCP marking, the client does not have to run with administrator privileges.  


Enabling DSCP in Zoom

To enable and configure the DSCP marking values for all members of your organization:

  1. Sign into the Zoom web portal as an administrator with the privilege to edit Account settings.
  2. In the navigation panel, click Account Settings.
  3. On the Meeting tab, under In Meeting (Advanced), verify that the setting DSCP marking is enabled.
    If the setting is disabled, click the Status toggle to enable it. If a verification dialog displays, choose Turn On to verify the change.
  4. (Optional) If you want to make this setting mandatory for all users in your account, click the lock icon, and then click Lock to confirm the setting.

Setting DSCP Marking via Group Policy

Due to changes by Microsoft, for the Windows client to be able to utilize DSCP Marking, the Client must be run “as administrator”.

However, the Windows client can now be tracked by Group Policy QoS policies as an alternative method, if the app is not running with administrative privileges. 

  1. First Deploy the Zoom MSI client, with Independent Data Ports enabled either by
    • Adding the variable to the installation string, EnableIndependentDataPort=1.
    • Adding the variable to the Group Policy Object for the Zoom app, “EnableIndependentDataPort”=dword:00000001.
      Note: For more information on deploying the Zoom client with this variable enabled, please see: Mass Installation and Configuration for Windows.
  2. Open Group Policy Management Console (GPMC) and edit your desired Group Policy Object (GPO).
  3. Click on Create new policy....
  4. Name the Policy and set the desired DSCP Value for Zoom traffic.
  5. Click Next.
  6. Set the executable name to Zoom.exe.
  7. Click Next.
  8. Leave the default IP address settings and click Next.
  9. Set the protocol to TCP and UDP. Leave the default port settings and click Finish.
  10. Deploy the new Group Policy and reboot the devices it was applied to.


Once the Zoom Windows client is in a meeting, you should see packets being marked, that are being sent from the client to the Zoom meeting server.