Change Windows Server 2008 or 2012 Network Profile

Sometimes a Windows server is assigned to the incorrect network profile. It can cause applying the wrong Windows Firewall rules. Here is how to change its network profile.

For standalone server

• Can change the profile to public or private; but cannot set to domain
• For Windows Server 2012
• Open PowerShell as administrator
• Get-NetconnectionProfile | Set-NetconnectionProfile -NetworkCategory [Private | Public]
• For Windows Server 2008 or 2012
• gpedit.msc, Computer Configuration, Windows Settings, Security Settings, Network List Manager Profiles
• Select the network name, Properties, Network Location
• Under Location Type, select Private or Public

For domain joined server

• Cannot change the profile manually
• It’s determined by Network Location Awareness (NLA) service (see “Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles”)
• If the network profile is incorrect,
• verify the server can contact a DC via UDP port 389
• restart the Network Location Awareness service on the server

Best Practices for DNS Client Setting in Windows Server Domain Controller with DNS Installed

Assume at least two domain controllers with DNS installed in the domain.

• Configure the remote DNS server set as Preferred DNS server
• Configure 127.0.0.1 as Alternate DNS server

Reference:

• http://support.microsoft.com/kb/825036
• http://technet.microsoft.com/en-us/library/ff807362(WS.10).aspx

Windows Server 2008 DHCPv6 Stateless and Stateful Mode

Windows Server® 2008 supports stateless and stateful DHCPv6 server functionality. DHCPv6 stateless mode clients use DHCPv6 to obtain network configuration parameters other than the IPv6 address, such as DNS server addresses. Clients configure an IPv6 address through a non-DHCPv6 based mechanism such as IPv6 address auto-configuration (based on the IPv6 prefixes included in router advertisements), or static IP address configuration.

In DHCPv6 stateful mode, clients acquire both the IPv6 address as well as other network configuration parameters through DHCPv6.

Reference: http://technet.microsoft.com/en-us/library/cc753493.aspx