Domain server starts with wrong network profile

Always recommended to have at least two domain controller for high availability and for disaster mitigation. Simple solution is to delay restart NLA service via Task scheduler.

--please don't forget to Accept as answer if the reply is helpful--

Well, it didn't work upon the morning restart. With what's going on in my lab today I'll be restarting it several times I know. Got a reminder note taped to it to check the active profile upon each restart. We'll see what happens as that morning restart may have just been a fluke.

it didn't work upon the morning restart.

Make sure configuration for NLA dependencies and DNS suffix for this connection are right when you find it didn't work.

I see someone add Netlogon, DNS, and NTDS as a dependency to NLA and it works.

You might do a test: sc config nlasvc depend=NSI/RpcSs/TcpIp/Dhcp/Eventlog/DNS/NTDS/Netlogon

If above steps still doesn't work, we need to trace and monitor logs to analyze the cause. Tool such as Network Monitor and Process Monitor can be considered .However, analysis of log is beyond our forum support level and due to forum security policy, we have no such channel to collect user log information. So we recommend you open a case with MS Professional tech support service, they will help you open a phone or email case to Microsoft, so that you would get a technical support on a one-to-one basis while ensuring private information.

Here is the link:

https://support.microsoft.com/en-us/gp/customer-service-phone-numbers

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Bottom line is that it's not working. So I give up and have reverted back to the task scheduler with a 2 minute delay to restart NLASVC on startup.

You may want to consider a reactive restart rather than a timed one.
By using PowerShell to check the network profile your scheduled task can act without delay if it needs to, and just sit quietly if it's not needed.

{ I just ran into this the first time myself, so the code below doesn't have much field testing. Depending on the environment and root cause other services could be relevant. }

<# Make sure the Connection Profile has correctly established as DomainAuthenticated #>
$NetConnection = Get-NetConnectionProfile

($NetConnection.NetworkCategory -ne 'DomainAuthenticated')
{
    get-service NlaSvc | restart-service    
}