today I experienced a Windows Server 2012 issue which puzzled me for a couple of hours.
After deploying a DC, I went on and disabled IPv6 (by adding the "DisabledComponents"-Key to my Registry):
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters /v DisabledComponents /t REG_DWORD /d 0xffffffff
After rebooting the System, I noticed the Network Location Awarness-related "Domain" Profile wasn't loading (I noticed it 'cause I was unable to successfully Remote-Desktop-login to the DC since the "Public" Profile was ON!).
To preventy this from happening again, I went through the following Ace Fekay's article over the net: https://msmvps.com/blogs/acefekay/archive/2010/05/27/how-to-disable-rss-tcp-chimney-feature-and-ipv6.aspx
- …and I choose to setup my Registry to "Prefer IPv4 over IPv6":
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters /v DisabledComponents /t REG_DWORD /d 0×20
By so doing, during my next reboot, my DC successfully loaded the NLA "Domain" Profile (&& I was able to successfully login to it thru RDP…).