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.

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.

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.

Click the Advanced tab.

Check Public and then click OK.

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

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

Where did a User’s Account Get Locked Out?

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...

Jason Yoder, MCT

Search This Blog