Server 2019 Network Profile, Network Location Awareness and RADIUS issues

I'm presently checking out Serve 2019 in the lab. Did a clean install of Server 2019 and installation went flawless. Set up as PDC and for now this is the only DC on the network and as of yet no work...

windows server

pvlier
Nov 17, 2020
Carl1959 Maybe a bit late but for all others having this problem:

NLA uses dns to see what kind of network it is. If DNS is not fully functional at the time NLA starts, it cannot determine the domain existence. Simple fix: make nla dependant on DNS server

start regedit
navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc
Edit 'DependOnService
Add new line with "DNS"

This fixes the problem for me so network profile is always 'domain' after a reboot

pvlier

Copper Contributor

Nov 17, 2020

Carl1959 Maybe a bit late but for all others having this problem:

NLA uses dns to see what kind of network it is. If DNS is not fully functional at the time NLA starts, it cannot determine the domain existence. Simple fix: make nla dependant on DNS server

start regedit

navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc

Edit 'DependOnService

Add new line with "DNS"

This fixes the problem for me so network profile is always 'domain' after a reboot