In Windows Server 2012 environment, Windows will auto detect and assign network profile to the particular network adapter.
Below are the brief description for each network profile:-
- Private: Used for computers on a private or home network. This allows you to see computers and devices, while making your computer discoverable.
- Public: Used for computers on a pubic network such as a coffee shop or internet café. Designed to keep your computer from being visible to other computers around you and to help protect your computer from any malicious software from the Internet.
- Domain: Used for computers that belong to enterprise network.
Some of the System Admin might not border on the profile assignment as long as no issue on the network connectivity. But they might facing issue when they want to implement Windows Firewall as Windows Firewall will protect network according to network profile. On that kind of situation, you have to manually change the network location configuration of a Windows 2012 R2 Servers network connection.
There are two common approaches to this, either by Local Group Policy or PowerShell. In this post I will be stepping through how to implement it using PowerShell command. Continue reading