Skip to main content

How make sure the Firewall rules for both Public and Private networks are the same

Originally this question was “How to force all new wireless networks to be Public.”  I had very little luck with this one.  I started looking into a PowerShell option for this, but that code was turning into a complex process.  It then hit me, just make the two profiles the same in the firewall.

 

To do this, we are going to use the firewall on a Windows 7 client. 

 

Open the Windows Firewall with Advanced Security.

Right click Windows Firewall with Advanced Security and then click Export Policy.

image

 

Save the policy to a network location.

 

Open Group Policy Management on a Windows 2008 R2 server or a Windows 7 Client with RSAT installed.

 

Create a new GPO, or used one that is scoped to reach all of your clients.  I named my GPO Firewall.

 

Edit the GPO and expand Computer Configuration / Policies / Windows Settings / Security Settings / Windows Firewall with Advanced Security / Windows Firewall with Advanced Security.

 

Right click Windows Firewall with Advanced Security and select Import Policy.

 

image

 

Click Yes at the warning.

 

Import the policy that you exported with the previous steps.

 

Now, go through the inbound and outbound rules.  Anywhere you see the profile as only listing Private, mark it as also being set for Public.  To do this, double click on a setting that is only set for Private.

 

image

 

Click the Advanced tab.

 

Check Public and then click OK.

 

image

 

Do this for all the inbound and outbound rules.

 

Now apply the GPO to the clients and the Public firewall profile will be just as restrictive as the Private profile.  Should your user accidently click Private, no problem.  They will have the same settings as the Public profile.

 

You will need to use this GPO to make any future firewall updates and remember to apply any changes to the Public profile to also include the Private profile.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.