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

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.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the ma...