Network Profiles were first introduced as part of Windows Firewall with Advanced Features in Vista/2008 to allow administrators to configure different firewall profiles based upon what network a user connects to. Administrators could change the profile by navigating to Network and Sharing Center in control panel and selecting the profile which suits their needs.
In Server 2012, Administrators can no longer change the network profile in Network and Sharing Center, they can view just not change.
To change the network profile you must use the new PowerShell cmdlets introduced in PowerShell version 4 in Windows Server 2012.
Please refer to the following screenshots for performing this procedure.
After making this change, it will update in Network and Sharing Center.
The default profile in Windows Server 2012 is public. This changes automatically when you join the server to the domain however in the event your server is not to be joined to the domain, you need to change the profile manually yourself. In this instance I'm setting up a stand alone offline certificate authority which must not be domain joined. As a result I needed to configure this manually.
Hope this has been helpful.
In Server 2012, Administrators can no longer change the network profile in Network and Sharing Center, they can view just not change.
To change the network profile you must use the new PowerShell cmdlets introduced in PowerShell version 4 in Windows Server 2012.
Please refer to the following screenshots for performing this procedure.
After making this change, it will update in Network and Sharing Center.
The default profile in Windows Server 2012 is public. This changes automatically when you join the server to the domain however in the event your server is not to be joined to the domain, you need to change the profile manually yourself. In this instance I'm setting up a stand alone offline certificate authority which must not be domain joined. As a result I needed to configure this manually.
Hope this has been helpful.
Very useful post. Got me out of networking hell. Thanks
ReplyDeleteThank you, great post!
ReplyDeleteExactly what I was looking for.
ReplyDeleteThanks!
Perfect! Thanks a million!
ReplyDeleteThat I was looking for :)
ReplyDeleteThanks sir, you made my day!
ReplyDeleteThank You! It was quick and perfect solution.
ReplyDeleteSameer Vadulekar
You're the Man!!!
ReplyDeleteWould this also have something to do with why when my Imaged machines pick up a 169 address after rebooting?
ReplyDeleteThis setting goes away with a reboot or if the network is disconnected and reconnected. Has anyone found a permanent solution other then using Local Security Policy to set all Unidentified networks as Private?
ReplyDeleteJust wanted to clarify, the setting goes away if you set it on an Unidentified Network.
ReplyDeleteIf you have multiple interfaces be sure to specify which one by using the -InterfaceAlias option in the command
ReplyDeletei'm having issues with the command, Get-NetConnectionProfile : A positional parameter cannot be found that accepts argu
ReplyDeleteAt line:1 char:1
+ Get-netconnectionProfile : Set-NetConnectionProfile NetworkCategory Public
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-NetConnectionProfile], Para
+ FullyQualifiedErrorId : PositionalParameterNotFound,Get-NetConnectionProfile
What if the server is already joined to the domain and this command doesnt work?
ReplyDelete