Forum Discussion
Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"
I just came across this problem and my solution was to make a ps script that disables and re-enables the Ethernet Adapter. Then I scheduled a task delayed by 1 min at startup, so that at least I don't have to do it manually every time I reboot.
- AlwaysExpectDomainController does not work with Server 2025.
Re-enables the Ethernet Adapter sounds like a workaround.
When can we expect a solution?Stefan_Voigt this is still a problem, even on the latest build of Server 2025. I have tried every suggestion, and the only thing that works is a scheduled task that does restart-netadapter * - that is not a solution. Microsoft needs to really focus on this. It's only when it becomes a DC that it does this. I really really really hope they don't let this bug roll into RTM, I've been following it since early vNext, and it's still lingering.
The bug is already in production in the annual server build channel on 23H2. I've tried raising this issue multiple times, reported it in the feedback hub and nothing. Microsoft really doesn't care about this bug.
People often suggest registry keys and changing the dependencies on services surrounding the issue but none of them work.
