Skip to main content

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

By

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.

Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more