Windows 2012: change network profile


  • Hi i have a query, how to change network profile to public from domain in a server on Windows 2012?

    Best regards


    Best Regards Edgar

    Wednesday, September 12, 2012 8:26 PM


All replies

  • Hi,

    Thanks for your post.

    If the server is domain joined, when it starts to detect the network location, the machine will contact a DC via port 389. If this detection successful, it will get the domain profile. And we cannot change it. If the domain was not found or process failed, NLA will let you to determine which firewall profile will be used, private or public.

    For more information about Network Location Awareness, you may refer to the following article. It also applies to Windows 2012.

    Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles

    Best Regards,


    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Aiden Cao

    TechNet Community Support

    • Marked as answer by EDGAREF Wednesday, September 19, 2012 4:46 AM
    Thursday, September 13, 2012 7:29 AM
  • Hi,

    How are things going? I just want to check if the information provided was helpful. If there is any update or concern, please feel free to let us know.

    Best Regards,

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Aiden Cao

    TechNet Community Support

    Tuesday, September 18, 2012 1:48 AM
  • Experiencing same issue where my Hyper-V Role Windows 2012 Standard Parent is setting itself up using the Network Location Profile of PUBLIC and shows 'not connected' for 'Domain' which is what it should be since this is a domain connected server.  This is causing disruption with related networking elements that require the Windows Firewall to perform in the domain.  A hosted VM running Windows 2008 R2 is one of two domain controllers in the current build environment where the second is a standalone Windows 2003 R2 installation with its Windows Firewall completely off.  I've restarted the Win2012 NLA service without change.

    Dale Unroe

    BTW ...I can ping the VM by IPV4 and can ping using the NETBIOS name (IPV6 responses) but not the FQDN
    • Edited by Dale DU-IT Tuesday, September 18, 2012 7:49 PM
    Tuesday, September 18, 2012 7:42 PM
  • Hello

    I just set up a server 2012 with Hyper-V, configured a Server 2012 VM and added AD DS on it.

    After the configuration of AD DS I can ping the NetBIOS Domain name and the FQDN. The VM has an internal Network connection only.

    So I am logged on a well working domain controller (the first in the network).

    But it will get the "Guest or public networks profile" only.

    The "domain profile" was enumerated first after configuring a fixed IPv6 Adress on the DC.

    So the conclusion for Windows Server 2012:

    The IPv6-connectivity is important for the detection of the domain network.

    Best Regards


    Tuesday, October 16, 2012 10:42 AM
  • You can also click on the Network icon on the desktop Tray, right click on the "Network" and click "Turn Sharing On or Off." Click "Yes turn on sharing and connect to devices." Your network will change from profile public to private...


    Thursday, May 02, 2013 5:07 PM
  • Thanks Hellmuth

    Got the same issue on a Windows Server 2012 DC. I re-activated the IPV6 checkbox in network settings and the network profile moved from public to Domain network.

    Laurent Lesle

    • Proposed as answer by melayuusa Wednesday, June 18, 2014 11:56 PM
    Tuesday, May 07, 2013 12:45 PM
  • I had the same issue and took it that my machine may have been taking too long on bootup to correctly define the profile.  As a small test I restarted the Network Location Awareness service (irrespective of whether IPv6 was selected or not) and the correct profile was selected.

    I then set the service to Automatic (Delayed Start) and the correct firewall profile was selected on bootup

    Tuesday, November 12, 2013 2:06 PM
  • Excellent and thank you. This has solved the issue for me immediately with my Windows Hyper-V Server 2012R2 as I had the exact same problem .
    Friday, December 20, 2013 4:26 PM
  • Hi all, the root cause for this appears to be if you have a DC in your environment which has either its primary or secondary DNS pointing to an external ip address, EG:

    DNS server IPs on any Domain controller should always point to itself or another domain controller, and Forwarders can be configured in the DNS Management Console to point to external DNS like

    This should resolve your issue. Checking then unchecking IPv6 will help you with a temporary fix until it happens to more servers later. 

    • Proposed as answer by melayuusa Wednesday, June 18, 2014 11:56 PM
    Tuesday, June 10, 2014 2:21 AM
  • **believe in my case the root cause was an IP address conflict

    Dale Unroe

    Thursday, June 19, 2014 1:05 AM
  • no you can  not in server 2012

    lan admin

    Tuesday, October 13, 2015 5:44 PM
  • This is not acceptable. There should be a manual way to change the profile. For example, I have a member server which is in "public" mode which is joined to a domain, and even sitting on the same subnet.. and yet its "public" instead of domain.

    Microsoft really has not been helping the people who install and manage their products, and its really starting to show. You need to escalate this to the highest levels of development inside Microsoft and get them to understand this.

    Thursday, November 10, 2016 10:33 PM
  • Hi Guy,

    You can follow below screenshot to change network profile in Windows Server 2012 using MS PowerShell.

    > Get-NetConnectionProfile

    > Get-NetConnectionProfile | Set-NetConnectionProfile -NetworkCategory Private

    Hope this will help.



    Wednesday, February 01, 2017 9:26 AM
  • Well I also had a issues with a domain joined Windows 2012 R2 Hyper-V Server setting it's self to public network at times ...??? Reboot would not always fix.... :(

    Today i did what someone siad here... "Enabled IPv6"


    Well guess what? Instant fix... enabled IPv6 and presto... Host NIC shows status of Domained joined!

    No reboot reqired.

    I'm confused ??

    Thxs Guys.

    Thursday, April 06, 2017 10:45 PM
  • This is exactly what has happened to me. I think I installed SP on both servers and then rebooted them. I would guess server 2 restarted before server 1 and selected the wrong profile. Need to pay more attention to how I restart my servers.


    Thursday, August 31, 2017 2:58 PM
  • Thank you!  That's the best advice.  Restart NLA service and set it to delayed start if it takes a while for your network to load after reboot

    Daniel Smith

    Wednesday, September 06, 2017 5:50 PM