We had an issue where our domain controller lost its domain network profile after a reboot. When it came back up it was set to public instead of domain.

The problem occurred only when Windows NIC teaming (switch-independent) was used in combination with two network adapters in the team. As soon as one network adapter was disabled from the team (while the other remained active), the network profile (domain) was recognized correctly.

This behavior appears to be caused by the Network Location Awareness (NLA) service starting before the physical NICs are fully initialized and before the domain is available. What helped us is to add the DNS and core NTDS service as a dependency to the NLA service. You could use the following PowerShell command to add these two services.

sc.exe config nlasvc depend=NSI/RpcSs/TcpIp/Dhcp/Eventlog/DNS/NTDS

Note that this command will replace existing dependencies.

We also noticed that Windows Server 2025 no longer has the NLA service enabled. It seems that the behavior has changed after Windows Server 2022.