Windows 7 - Firewall
Stuppored
Member Posts: 152 ■■■□□□□□□□
Windows Firewall settings were exported to a .wfw file.
The settings take effect if I manually import them through gpedit.msc and click to import the file.
What I really want to have happen is a batch file executes the following: netsh advfirewall import c:\firewall.wfw
For some reason using this command says it executes correctly with an OK... but the settings fail to take effect... this computer is not on a domain... it's odd that manually clicking through allows the file to make the settings take effect... but running the command does not...
Can anyone assist? Is there a registry hack for this?
The settings take effect if I manually import them through gpedit.msc and click to import the file.
What I really want to have happen is a batch file executes the following: netsh advfirewall import c:\firewall.wfw
For some reason using this command says it executes correctly with an OK... but the settings fail to take effect... this computer is not on a domain... it's odd that manually clicking through allows the file to make the settings take effect... but running the command does not...
Can anyone assist? Is there a registry hack for this?
Comments
-
Stuppored Member Posts: 152 ■■■□□□□□□□I need to import the wfw file into the gpedit.msc program so it works.... I need a command prompt command that allows me to do that... I can only seem to add them manually with clicking... need a command to do that please
-
Asif Dasl Member Posts: 2,116 ■■■■■■■■□□That netsh command works for me, it restores all the firewall rules I deleted when I tried it...
-
Stuppored Member Posts: 152 ■■■□□□□□□□Using MDT 2012. Once the desktop rolls out MDT pushes GPO policy out as the final step in deployment. I simply disabled that last step. Now I'm wondering how do I create my own custom GPO for local settings that MDT can push out for clients?
The netsh advfirewall import filename command only works if the firewall is not protected by local group policy. Still wondering how I can push in my own policy by command prompt too.