Has anyone got into the weeds on Teams VDI QoS policies at all? Looks like the commands are different for normal Teams QoS vs the optimized/slimcore Teams QoS, due to the actual process. For Teams VDI endpoint QoS rules they want you to apply the QoS to "MsTeamsVdi.exe". For Non VDI endpoint QoS they want you it applied to "ms-teams.exe". From what i'm seeing you can't apply QoS to both processes. They want you to separate them based upon endpoint use case, which doesn't work in all scenarios where a device is shared b/t multiple suers that may use Teams inside Citrix/VDI, or the local Teams install. https://learn.microsoft.com/en-us/microsoftteams/vdi-2

How are you applying the QOS? I did this with DSCP markings in regular old Windows, and QOS'd it on the firewall/router.

yep, that's correct from what i can see, need the DSCP markings/ID, and the firewall router config. There's a GPO you apply to the endpoint that identifies the process name, protocolor, source/dest port, source/dest IP, etc...

You can mark them with different DSCP values, but QOS them in the same policy.

i thought the DSCP value was how it identified the streams, aka 46 is for audio, 34 is for video....

doing it by process would not break out audio/video, it would simply QOS the entire process. There would need to be some engine to break it out. Like the old Mulit-Stream ICA stuff, you could break it out to 4 different DSCP values.

ah, for some reason i thought it was more like a reg key, where if you defined two processes with the same DSCP value, one would overwrite the other. So basically just create the 3 additional QoS polices iwth the exact same DSCP value, but use the new msteamsvdi.exe process.

i have an old article that may explain it better? Multi-Stream ICA and Cisco QOS » Citrixirc.com. BUT, technically, you could also just mark both process with the same DSCP value, and just have 1 QOS policy. yes.

yeah exactly, like here's an example of an existing one for native Teams. We could just add 3 more, with the same settings, but just swap the process out and use msteamsvdi.exe

Are those ports default? If they are, you don't even need to set DSCP, you can just QOS based on the ports?

interesting, yeah, the -AppPathNameMatchCondition parameter doesn't appear to be a required param

Where did those ports come from?

https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams-clients the VDI reference is https://learn.microsoft.com/en-us/microsoftteams/vdi-2

This is so poorly written. Are we to assume that when you "enable QoS globally in the Teams Admin Center", this is what enables the ports in the application?

from the Teams Admin Center, it looks like you have the option to configure the port ranges, https://learn.microsoft.com/en-us/microsoftteams/meetings-real-time-media-traffic

it's like... for multi-stream ICA, that was only enabled when you turned it on.

i thought the DSCP was actually targeting the specific audio/video channel, but it's more a 'priority' or 'class' as they call it.

DSCP is just a marker. it's a tag. It will TAG all "audio" traffic that matches ms-teams.exe and ports blah-blah with DSCP 46, then your router/firewall can shape/prioritize/limit traffic based on that value

yeah, that makes more sense now, thanks, I think we have a ticket open to confirm with microsoft that this will work, which based upon what i'm finding and what you said, it should

you're welcome. I have done a lot of QOS since I'm half network engineer. If you have any more questions, i'm happy to help. Sorry if it was confusing. QOS is quite confusing, to be fair.