Windows Defender firewall profile wrong after docking

Minimal guidance for messy support realities.

Scenario

A laptop on the corporate network still applies the Public firewall profile after docking, breaking internal management tools.

Recommended Resolution Path

  1. Confirm the network location awareness service can identify the domain profile on docked Ethernet.
  2. Check DNS suffix, domain controller reachability, and whether Wi-Fi remains preferred.
  3. Update dock, NIC, and chipset drivers if the interface binding changed recently.
  4. If the profile flips only with one dock model, standardize firmware before broader policy changes.

Technician Notes

Document what changed, what confirmed the fix, and whether the issue points to a broader standards gap worth addressing for the client.

Subjects