Group Policy requires a domain controller IIRC, so is not an option for stand alone windows instances.
Hmm, so this technique does not work for ICMP? I guess I was lucky then using putty for testing and not ping...
DSCPs really have no inherent value,the only thing that matters is what your prioritization set-up does with them. For cake diffserv4 and diffserv3 the following mappings hold
diffserv4:
/* Further pruned list of traffic classes for four-class system:
*
* Latency Sensitive (CS7, CS6, EF, VA, CS5, CS4)
* Streaming Media (AF4x, AF3x, CS3, AF2x, TOS4, CS2, TOS1)
* Best Effort (CS0, AF1x, TOS2, and those not specified)
* Background Traffic (CS1)
*
* Total 4 traffic classes.
*/
diffserv3:
/* Simplified Diffserv structure with 3 tins.
* Low Priority (CS1)
* Best Effort
* Latency Sensitive (TOS4, VA, EF, CS6, CS7)
*/
The question which to take is something I would base on how much traffic I expect Teams to require.
Here are the priority rate percentages:
diffserv3:
Low Priority: 6.25%
Best Effort: 100.00%
Latency Sensitive: 25.00%
diffserv4:
Background Traffic: 6.25%
Best Effort: 100.00%
Streaming Media: 50.00%
Latency Sensitive: 25.00%
Assuming that at your lowest shaper setting teams will use a considerable fraction of your capacity, I would use diffserv4 and specifically the "streaming media/video" tin:
static const u8 diffserv4[] = {
0, 1, 0, 0, 2, 0, 0, 0,
1, 0, 0, 0, 0, 0, 0, 0,
2, 0, 2, 0, 2, 0, 2, 0,
2, 0, 2, 0, 2, 0, 2, 0,
3, 0, 2, 0, 2, 0, 2, 0,
3, 0, 0, 0, 3, 0, 3, 0,
3, 0, 0, 0, 0, 0, 0, 0,
3, 0, 0, 0, 0, 0, 0, 0,
};
so CS2/16 would be a decent choice.
If however 25% of minimal shaper rate still works OK I would probably use EF/46 as that would allow to use either diffserv4 or diffserv3.