Forum Discussion
Windows Server 2022 Unable to restart 'Network Location Awareness' Service
Testing server 2022 (core) GA on two machines; one physical, one virtual. When I attempt to restart the network location awareness service using the command: restart-service -Name NlaSvc -For...
Plus one. New Intel server with an X710 quad SFP NIC. Set up with a basic fixed IP4 and DHCP IP6 config on one port for the initial stages of building the server. Win 2022 sees the local network as Unidentified instead of the domain. Cant restart the NLA/NL services only kill them.
Couldn't get any joy with adding the domain suffix to the IP4 config. Switching IP6 off or on works so I've added a scheduled task with a delayed Powershell script to do that on bootup. A workaround rather than a fix.
Thanks for your posts. Helpful to know its a general problem and not just me. Cheers.
Couldn't get any joy with adding the domain suffix to the IP4 config. Switching IP6 off or on works so I've added a scheduled task with a delayed Powershell script to do that on bootup. A workaround rather than a fix.
Thanks for your posts. Helpful to know its a general problem and not just me. Cheers.
Hello,
Could you try this ? Setting/Creating the DWORD registry key "AlwaysExpectDomainController" located in "HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters" to 1, on top of adding DNS suffix on your NIC.
Could you try this ? Setting/Creating the DWORD registry key "AlwaysExpectDomainController" located in "HKLM\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters" to 1, on top of adding DNS suffix on your NIC.
- Hi, I went back to the initial config including removing the DNS suffix and disabling the startup IP6 off/on Powershell script. I tried your registry entry to make NLA persist with domain detection and did some test restarts. So far so good. Thanks for the tip.
Googling 'AlwaysExpectDomainController' I see this is recommended in several forums. Of interest is this one which describes a couple more registry entries to prevent incorrect network info being cached. I may experiment with these too if the current situation starts going pear-shaped:
https://learn.microsoft.com/en-us/answers/questions/400385/network-location-awareness-not-detecting-domain-ne
Cheers.- AlwaysExpectDomainController registry entry fixed me. So far so good.
- This has been an issue since Server 2012 and Microsoft cannot fix a fundamental part of a network configuration on boot up. Adding the domain name to the DNS and a delayed start on the Network Location Awareness service didn't fix the issue. For christ sake MS fix this **bleep**. Rebooting a server after an update should not be doing this. You've had 10 years or more to sort this crap out.
NickFranklin Agree.. I have at least 6 servers that do this and there is no rhyme or reason as to why these servers do it and others don't. I've not found a permanent fix, it ALWAYS comes back at some point.
Dave
