- #Windows server 2012 remote desktop pop behind update#
- #Windows server 2012 remote desktop pop behind windows 7#
There might be a way to script this, but it would require enumerating network adapters, so I’ll just do it manually for now. Run ncpa.cpl and do this in the iPv4 and IPv6 properties of the network adapter (see screen shots above). Set the Connection Specific DNS Name to match the domain controller’s local domain. Set the NLA service to “Automatic (Delayed Start)” and only when the network is available:Ģ.
Note that the space after the equal sign (=) is intentional and required. To see Automatic (Delayed Start) from the command line, run: After changing it to “Automatic (Delayed Start)”, this machine also rebooted directly to the Domain profile. Wait, this machine still had NLA service set to Automatic. However on another machine, those two changes weren’t enough. Three more reboots and the machine has come up as Domain each time. Sc triggerinfo NlaSvc start/networkon stop/networkoff
Can’t hurt, right? I ran the following from an administrative command prompt: Is there anything else I can do to help it be more reliable? The only other idea I have at this point is to make the NLA service dependent on having an active network connection. Well, that worked two times out of three. Voila! After a reboot, the machine immediately came up on with a Domain profile: So I added the “mydomain.local” string to both IPv4 and IPv6 profiles of the adapter. I’d already seen (using ipconfig from a command prompt) that this machine is using both IPv4 and IPv6 to talk to the domain controller. However I did not have “DNS suffix for this connection” filled in. This is critical for all kinds of domain-based stuff (group policy, etc.). I had already set a fixed IP address for the primary DNS server, pointing to the domain controller.
#Windows server 2012 remote desktop pop behind update#
However the TechNet article cited above wants us to match Connection-specific adapter settings, hence the update above. The Primary DNS Suffix defaults, sensibly, to the domain name. You can also override that in group policy: Computer Configuration Administrative Templates > Network DNS Client > Primary DNS suffix. When you click the More button, you’ll see this dialog: When set in group policy, it overrides the value set in this dialog, but it is not displayed in this dialog.īy the way, the Primary DNS suffix for the computer is set in System Properties when you specify the computer name. Note that this can also be set in group policy: Computer Configuration > Administrative Templates > Network > DNS Client > Connection-specific DNS suffix. I checked that registry key and it in fact contained the correct value, let’s say “mydomain.local”.īut how/where is the Connection Specific DNS Name set? This article offers guidance: you can set it in the adapter’s DNS properties. The big news to me in that article is this: “If the Connection Specific DNS Name matches the HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Group Policy\History\NetworkName registry key then the machine will attempt to contact a Domain Controller via LDAP.” Then I found this TechNet blog article on how the NLA service works. Today I decided to dig into this further to see if I could come up with a better solution. Using a script allows doing this even when connected remotely, but it’s awkward and you have to customize the interface name for each PC. Netsh interface set interface "Ethernet" enabled Netsh interface set interface "Ethernet" disabled In fact I have script a RestartNetworkAdapter.cmd on many computers to do just that: The only sure way that I have found to force the NLA service to re-detect the domain is to stop and restart the network adapter. That doesn’t work because the Network List Service depends on the NLA service, and the Network List Service, for some reason, can’t be stopped. That’s has not been enough in this environment.Īt least one article suggests restarting the NLA service.
Several articles suggest changing the NLA service to “Automatic (Delayed Start)”. The problem, of course, is that the Network Location Awareness (NLA) service can’t determine that the machine is on a domain, so it falls back to Public:
Some desktops, especially those that have are behind a couple switches, often have problems confirming that they are on the domain, so they come up on the Public network, which messes up RDP connections.
#Windows server 2012 remote desktop pop behind windows 7#
One small client has a Server 2012 R2 Essentials domain controller and a few Windows 7 desktops.
0 kommentar(er)
