In modern enterprise environments, dual-stack IPv4/IPv6 networks often create subtle but frustrating performance degradation: slow internal application loading, intermittent Active Directory authentication timeouts, and VPN split-tunnel DNS leaks. When a workstation attempts to query an IPv6 DNS server on an ISP connection before falling back to corporate IPv4 internal resolvers, users experience 3-to-5 second latency delays.
The Dangerous Mistake: Unchecking IPv6 in Network Properties
Never Completely Disable the IPv6 Protocol Binding
Unchecking the "Internet Protocol Version 6 (TCP/IPv6)" checkbox in network adapter properties breaks core Windows OS components—including Windows Remote Assistance, HomeGroup remnants, DirectAccess, and modern Windows Update mechanisms. Microsoft officially advises against unbinding IPv6.
The Microsoft-Supported Best Practice: Prefer IPv4 over IPv6
The standard enterprise solution is setting the DisabledComponents registry value to 0x20 (Decimal 32). This instructs the Windows networking stack to prioritize IPv4 while keeping the IPv6 stack healthy and operational.
Intune Proactive Remediation: Prefer IPv4 Script
# ==============================================================================
# Intune Remediation Script: Set Prefer IPv4 over IPv6 (DisabledComponents = 0x20)
# ==============================================================================
$regPath = "HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters"
$valName = "DisabledComponents"
$targetVal = 32 # 0x20 in hex
try {
if (-not (Test-Path $regPath)) { New-Item -Path $regPath -Force | Out-Null }
Set-ItemProperty -Path $regPath -Name $valName -Value $targetVal -Type DWord -Force
Write-Host "SUCCESS: Configured DisabledComponents to 0x20 (Prefer IPv4 over IPv6)."
exit 0
} catch {
Write-Error "Failed to set DisabledComponents: $($_.Exception.Message)"
exit 1
}
