Windows Firewall: Define inbound program exceptions

Allows you to view and change the program exceptions list defined by Group Policy. Windows Firewall uses two program exception lists: one is defined by Group Policy settings and the other is defined by the Windows Firewall component in Control Panel. If you enable this policy setting you can view and change the program exceptions list defined by Group Policy. If you add a program to this list and set its status to Enabled that program can receive unsolicited incoming messages on any port that it asks Windows Firewall to open even if that port is blocked by another policy setting such as the “Windows Firewall: Define inbound port exceptions” policy setting. To view the program list enable the policy setting and then click the Show button. To add a program enable the policy setting note the syntax click the Show button. In the Show Contents dialog box type a definition string that uses the syntax format. To remove a program click its definition and then press the DELETE key. To edit a definition remove the current definition from the list and add a new one with different parameters. To allow administrators to add programs to the local program exceptions list that is defined by the Windows Firewall component in Control Panel also enable the “Windows Firewall: Allow local program exceptions” policy setting. If you disable this policy setting the program exceptions list defined by Group Policy is deleted. If a local program exceptions list exists it is ignored unless you enable the “Windows Firewall: Allow local program exceptions” policy setting. If you do not configure this policy setting Windows Firewall uses only the local program exceptions list that administrators define by using the Windows Firewall component in Control Panel. Note: If you type an invalid definition string Windows Firewall adds it to the list without checking for errors. This allows you to add programs that you have not installed yet but be aware that you can accidentally create multiple entries for the same program with conflicting Scope or Status values. Scope parameters are combined for multiple entries. Note: If you set the Status parameter of a definition string to “disabled” Windows Firewall ignores port requests made by that program and ignores other definitions that set the Status of that program to “enabled. ” Therefore if you set the Status to “disabled” you prevent administrators from allowing the program to ask Windows Firewall to open additional ports. However even if the Status is “disabled” the program can still receive unsolicited incoming messages through a port if another policy setting opens that port. Note: Windows Firewall opens ports for the program only when the program is running and “listening” for incoming messages. If the program is not running or is running but not listening for those messages Windows Firewall does not open its ports.

Windows Firewall: Allow authenticated IPsec bypass

Allows unsolicited incoming messages from specified systems that authenticate using the IPsec transport. If you enable this policy setting you must type a security descriptor containing a list of computers or groups of computers. If a computer on that list authenticates using IPsec Windows Firewall does not block its unsolicited messages. This policy setting overrides other policy settings that would block those messages. If you disable or do not configure this policy setting Windows Firewall makes no exception for messages sent by computers that authenticate using IPsec. If you enable this policy setting and add systems to the list upon disabling this policy Windows Firewall deletes the list. Note: You define entries in this list by using Security Descriptor Definition Language (SDDL) strings. For more information about the SDDL format see the Windows Firewall deployment information at the Microsoft Web site (http://go. microsoft. com/fwlink/?LinkId=25131).

Set Windows File Protection scanning

This policy setting allows you to set when Windows File Protection scans protected files. This policy setting directs Windows File Protection to enumerate and scan all system files for changes. If you enable this policy setting select a rate from the “Scanning Frequency” box. You can use this setting to direct Windows File Protection to scan files more often. — “Do not scan during startup” the default scans files only during setup. — “Scan during startup” also scans files each time you start Windows XP. This setting delays each startup. If you disable or do not configure this policy setting by default files are scanned only during setup. Note: This policy setting affects file scanning only. It does not affect the standard background file change detection that Windows File Protection provides.

Limit Windows File Protection cache size

This policy setting specifies the maximum amount of disk space that can be used for the Windows File Protection file cache. Windows File Protection adds protected files to the cache until the cache content reaches the quota. If the quota is greater than 50 MB Windows File Protection adds other important Windows XP files to the cache until the cache size reaches the quota. If you enable this policy setting enter the maximum amount of disk space to be used (in MB). To indicate that the cache size is unlimited select “4294967295” as the maximum amount of disk space. If you disable this policy setting or do not configure it the default value is set to 50 MB on Windows XP Professional and is unlimited (4294967295 MB) on Windows Server 2003.

Specify Windows File Protection cache location

This policy setting specifies an alternate location for the Windows File Protection cache. If you enable this policy setting enter the fully qualified local path to the new location in the “Cache file path” box. If you disable this setting or do not configure it the Windows File Protection cache is located in the %Systemroot% -> System32 -> Dllcache directory. Note: Do not put the cache on a network shared directory.

Allow the use of remote paths in file shortcut icons

This policy setting determines whether remote paths can be used for file shortcut (. lnk file) icons. If you enable this policy setting file shortcut icons are allowed to be obtained from remote paths. If you disable or do not configure this policy setting file shortcut icons that use remote paths are prevented from being displayed. Note: Allowing the use of remote paths in file shortcut icons can expose users’ computers to security risks.

Set a default associations configuration file

This policy specifies the path to a file (e. g. either stored locally or on a network location) that contains file type and protocol default application associations. This file can be created using the DISM tool. For example:Dism. exe /Online /Export-DefaultAppAssociations:C: -> AppAssoc. txt For more information refer to the DISM documentation on TechNet. If this group policy is enabled and the client machine is domain-joined the file will be processed and default associations will be applied at logon time. If the group policy is not configured disabled or the client machine is not domain-joined no default associations will be applied at logon time. If the policy is enabled disabled or not configured users will still be able to override default file type and protocol associations.

Start File Explorer with ribbon minimized

This policy setting allows you to specify whether the ribbon appears minimized or in full when new File Explorer windows are opened. If you enable this policy setting you can set how the ribbon appears the first time users open File Explorer and whenever they open new windows. If you disable or do not configure this policy setting users can choose how the ribbon appears when they open new windows.

Start File Explorer with ribbon minimized

This policy setting allows you to specify whether the ribbon appears minimized or in full when new File Explorer windows are opened. If you enable this policy setting you can set how the ribbon appears the first time users open File Explorer and whenever they open new windows. If you disable or do not configure this policy setting users can choose how the ribbon appears when they open new windows.