Thursday, February 27, 2014

Change the Network Location in Server 2012 R2

I needed to configure a Windows 2012 R2 server for some services to test, but didn’t want to domain join it.  By default, the network location was listed as public.
As such, firewall rules were not being followed.
To change the network location, open gpedit.msc (Local Group Policy Editor), and navigate to Computer Configuration / Windows Settings / Security Settings / Network List Manager Policies.
Double click the Network name of network that you would like to change the location.
Select the Network Location tab, and set the location to relevant setting.
Click OK, and close Local Group Policy Editor.  The network location has now changed to the location you set.

10 comments:

  1. Thanks for posting this. I used the PowerShell approach previously but this works as well and not all things GUI are bad.

    ReplyDelete
  2. I found a link on how to do the same thing by Powershell:
    http://blogs.msmvps.com/russel/2013/12/29/set-network-location-to-private-in-windows-8-1server-2012-r2/

    ReplyDelete
  3. This is better then powershell for many mixed networks on server :)

    ReplyDelete
  4. Thanks, I agree ... sometimes for a one off change on one machine, the GUI can be quicker and easier.

    ReplyDelete
  5. Does not work for me

    ReplyDelete
  6. This comment has been removed by a blog administrator.

    ReplyDelete
    Replies
    1. This comment has been removed by a blog administrator.

      Delete
  7. Since the last batch of Windows Security Updates Nov\Dec 16' I have the following issue:
    The Network Profile via the GUI or PowerShell shows DomainAuthenticated\Domain Network.
    The problem is that Windows Firewall Profiles show Public for the only connection I have...the domain one.
    When I attempt the Network List Manager Policies for my domain in Local Group Policy, there is no Network Location tab.
    So even though I'm clearly on a domain and being authenticated and can reach a domain controller and Forest PDC via 389, my Windows Firewall stays set at the more restrictive Public profile.
    I've restarted NLA and also set it to Delayed Start with no effect.
    Help?

    ReplyDelete
  8. Sorry, but this is not helpful since servers have ALWAYS to be joined to Domains. Waste of time in many blogs.

    ReplyDelete