Re: Windows Firewall Turned on Automatically
From: Torgeir Bakken \(MVP\) (Torgeir.Bakken-spam_at_hydro.com)
Date: 09/26/05
- Next message: Muss: "USB Detection Error"
- Previous message: Lanwench [MVP - Exchange]: "Re: Windows Firewall Turned on Automatically"
- In reply to: Dave Petzel: "Re: Windows Firewall Turned on Automatically"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 26 Sep 2005 18:27:56 +0200
Dave Petzel wrote:
> Windows Firewall Has Two Profiles Domain and Standard. This allows you to
> have different configurations depending if the computer is on its home domain
> or not. GPO is ineffective as a result of this because we want the firewall
> on for the standard profile and off for the domain profile. With the machine
> not detecting the correct profile it renders GPO useless.
>
Hi,
Note that is some cases the Standard Profile will be used even
if the computers are connected to the domain. This will happen
if last-received Group Policy update DNS name does not match any
of the connection-specific DNS suffixes of the currently connected
connections on the computer. In this case, the non-domain settings
will be used.
From
The Cable Guy - May 2004
Network Determination Behavior for Network-Related Group Policy Settings
http://www.microsoft.com/technet/community/columns/cableguy/cg0504.mspx
<quote>
To apply this behavior to Windows Firewall settings:
() If the connection-specific DNS suffix of a currently connected
connection on the computer that is not PPP or SLIP-based (such as
an Ethernet or 802.11 wireless network adapter) matches the value
of the
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Group
Policy\History\NetworkName registry entry, Windows Firewall uses
the domain profile.
() If the connection-specific DNS suffix of a currently connected
connection on the computer that is not PPP or SLIP-based does not
match the value of the
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Group
Policy\History\NetworkName registry entry, Windows Firewall uses
the standard profile.
You can determine the connection-specific DNS suffixes of the
currently connected connections on the computer from the display
of the ipconfig command issued from a command prompt.
</quote>
Read the Cable Guy article for more about this.
-- torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway Administration scripting examples and an ONLINE version of the 1328 page Scripting Guide: http://www.microsoft.com/technet/scriptcenter/default.mspx
- Next message: Muss: "USB Detection Error"
- Previous message: Lanwench [MVP - Exchange]: "Re: Windows Firewall Turned on Automatically"
- In reply to: Dave Petzel: "Re: Windows Firewall Turned on Automatically"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|