B
bhaf
We have several Windows Server 2012 R2 machines, and we've recently had some problems after reboots that I traced to the network adapters not being assigned the "Domain Authenticated" profile by the Network Location Awareness (NLA) service. It seems the NLA service runs too soon after booting and the machine is not fully connected to the domain yet, so it assigns it to the "Private" profile. If I wait a few minutes and restart the NLA service, it correctly assigns the Domain profile.
So I changed the startup type of the NLA service to delayed start, and have tried up to 5 minute delays, but the service still seems to start within 1:30 of boot up time. In our setup, the Network List Service (NLS) is shown as dependent on the NLA service, so I'm thinking that maybe the NLS starts the NLA service by itself when the NLS starts. But the NLS is set to "Manual" startup type, so I'm not sure what causes the NLS to start.
In summary, I need to delay the start of the NLA service, but I'm not sure how to do this since using the delayed start option isn't working, and I'm not sure what is starting the chain of actions that results in the NLA service getting started early. Anyone have any thoughts on this?
I'm considering setting up a scheduled task to run after bootup to restart the NLA service, but I would like to avoid this workaround if there is a better solution.
Thanks,
bhaf
Continue reading...
So I changed the startup type of the NLA service to delayed start, and have tried up to 5 minute delays, but the service still seems to start within 1:30 of boot up time. In our setup, the Network List Service (NLS) is shown as dependent on the NLA service, so I'm thinking that maybe the NLS starts the NLA service by itself when the NLS starts. But the NLS is set to "Manual" startup type, so I'm not sure what causes the NLS to start.
In summary, I need to delay the start of the NLA service, but I'm not sure how to do this since using the delayed start option isn't working, and I'm not sure what is starting the chain of actions that results in the NLA service getting started early. Anyone have any thoughts on this?
I'm considering setting up a scheduled task to run after bootup to restart the NLA service, but I would like to avoid this workaround if there is a better solution.
Thanks,
bhaf
Continue reading...