Forum Discussion
Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"
Used the following for reference: https://learn.microsoft.com/en-us/answers/questions/400385/network-location-awareness-not-detecting-domain-ne
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters
Name: NegativeCachePeriod
Type: REG_DWORD
Value Data: 0 (default value: 45 seconds; set to 0 to disable caching)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters
Name: MaxNegativeCacheTtl
Type: REG_DWORD
Value Data: 0 (default value: 5 seconds; set to 0 to disable caching)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters
Add a DWORD parameter :AlwaysExpectDomainController
Set value to:1
After reboot - Get-NetConnectionProfile returns DomainAuthenticated
Adding the AlwaysExpectDomainController key on 2022 fixed this issue for me. I just put in a GPO for my DC OU to do this going forward, was quite a pain
Still having this issue even after setting these keys 2025 DC. =(
I gave up using Server 2025, in my view it's way buggy. I won't push a client toward it.
Not working on 2025, it works on 2019 and 2022, only the disabling/enabling of the network interface after the boot is working on 2025...
Use of a 2025 as DC is hell, even as RDP server is hell...
While that may work for some to get it working, the consensus is the "bandaid" is to restart the NIC after bootup. Unfortunately, neither of these are considered fixes for an out of the box product, that's broken... out of the box. I did hear back from my Microsoft team, and it has been escalated again. They expect a fix in the coming months (an actual fix)
