Windows Server 2022 — QoS DSCP marking policy not honored on outbound traffic — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

QoS DSCP marking policy not honored on outbound traffic on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the networking subsystem is in use, typically following configuration drift or recent updates.

Get-NetAdapterAdvancedProperty | Where DisplayName -like '*Priority*'
gpresult /h C:Tempgp.html

Root Cause Analysis

The defect stems from misaligned qos policies settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

Get-NetQosPolicy -PolicyStore ActiveStore
Get-NetQosTrafficClass

Step-by-Step Diagnosis

Walk the networking stack from configuration to runtime, collecting logs and counters that point at the failing component.

Get-NetQosPolicy | Select Name,DSCPValue,IPProtocol
Get-NetAdapterQos -Name 'Ethernet0' | Format-List *

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the qos policies component re-initialises cleanly.

New-NetQosPolicy -Name 'SQL-DSCP' -IPDstPortMatchCondition 1433 -DSCPAction 46 -NetworkProfile All
Enable-NetAdapterQos -Name 'Ethernet0'
Set-NetQosPolicy -Name 'SQL-DSCP' -PolicyStore ActiveStore

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

Set-GPRegistryValue -Name 'QoSPolicy' -Key 'HKLMSoftwarePoliciesMicrosoftWindowsQoSSQL-DSCP' -ValueName 'DSCP Value' -Type String -Value '46'
gpupdate /force

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

netsh trace start capture=yes scenario=NetConnection
Get-NetQosPolicy | Where DSCPValue -eq 46

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

Remove-NetQosPolicy -Name 'SQL-DSCP' -Confirm:$false
Disable-NetAdapterQos -Name 'Ethernet0'

Prevention & Hardening

Bake the validated qos policies configuration into baseline GPOs or DSC and add a monitoring check for early detection.

Get-NetQosPolicy | Export-Clixml C:Backupqos.xml
Set-NetQosDcbxSetting -Willing $false

Related Errors & Cross-Refs

Related: other networking failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.