Setting this property filter to Yes causes the editor to show only managed Administrative Template policy settings, hiding all unmanaged Administrative Template policy settings.
Setting this property filter to No causes the editor to show only unmanaged Administrative Template policy settings, hiding all managed Administrative Template policy settings. Click Filter Options. Click OK to apply the new filter settings, and close the Filter Options dialog box. You can configure Administrative Template policy settings to one of three states: Not Configured , Enabled , and Disabled.
Not Configured is the default state for all policy settings. Policy settings set to Not Configured do not affect users or computers. Enabling an Administrative Template policy setting activates the policy setting. When Enabled , the action described in the title of the policy setting applies to the user or computer.
When Disabled , the opposite action described in the title of the policy setting applies to the user or computer. Usually Not Configured and Disabled policy settings produce the same results. The difference is that Not Configured policy settings do not apply to the user, but Disabled policy settings apply to a user.
Each Administrative Template policy setting provides detailed information about its Enabled , Disabled , and Not Configured states. You can view this information in the Help pane of each Administrative Template policy setting.
Or, you can view this information for the selected policy setting in the Extended View of the editor. The Configured property filter has three states: Any , Yes , and No. Setting this property filter to Any causes the Local Group Policy Editor to display all Administrative Template policy settings and is the default setting for this filter. Setting this property filter to Yes causes the editor to show only configured Administrative Template policy settings, hiding not configured policy settings.
Setting this property filter to No causes the editor to show only not configured Administrative Template policy settings, hiding configured policy settings.
Each Administrative Template policy setting has a comment property. The Commented property allows you to enter text associated with a specific policy setting. The Commented property filter has three states: Any , Yes , and No. Setting this proper filter to Yes causes the editor to show only commented Administrative Template policy settings, hiding policy settings without comments. Setting this property filter to No causes the editor to show only Administrative Template policy settings without comments, hiding commented policy settings.
Click OK to apply the new filter settings and close the Filter Options dialog box. Filters are inclusive, so select items you want to display rather than items you want to be removed. By default, the editor displays all policy settings. However, you can use keyword filters to change how the Local Group Policy Editor displays Administrative Template policy settings. Type one or more keywords in the Filter for word s box, and click the appropriate filter:.
Any : The filter includes any of the words in the Filter for word s box. All : The filter includes all of the words in the Filter for word s box.
Exact : The filter includes exact matches of the words in the Filter for word s box. Policy Setting Title : The filter includes searching the title of the policy setting. However, you can use requirement filters to change how the Local Group Policy Editor displays Administrative Template policy settings.
In the Select the desired platform and application filter s list, click the appropriate filter:. You can click Select All to select all of the items in the list, or you can click Clear All to clear all of the items in the list. If an alternative location is specified, this alternative location takes precedence. As part of the GPT, the Adm subfolder is replicated to all domain controllers in the domain.
Two policy settings area available to help with management of ADM files. These settings make it possible for the administrator to tune the use of ADM files for a specific environment. This setting may be applied to any Group Policy-enabled client.
This is a new policy setting. It may be successfully applied only to Windows Server clients. The setting may be deployed to older clients, but it will have no effect on their behavior.
If this policy setting is enabled, the Turn off automatic updates of ADM files policy setting is implied. In some environments, policy settings may have to be presented to the user interface in different languages. For example, an administrator in the United States may want to view policy settings for a specific GPO in English, and an administrator in France may want to view the same GPO by using French as their preferred language.
To work around this, use the "Turn off automatic updates of ADM files" policy setting. This makes it possible for the French administrator to view policy settings by using the ADM files that are installed locally on his or her workstation French , regardless of the ADM file that is stored in the GPT.
Also, consider standardizing on the latest operating system from Microsoft for administrative workstations in a multi-language administrative environment. If Windows workstations are being used, use the "Turn off automatic updates of ADM files" policy setting for administrators and consider the ADM files in the GPT to be the effective language for all Windows workstations. Each operating system or service pack release includes a superset of the ADM files provided by earlier releases, including policy settings that are specific to operating systems that are different to those of the new release.
For example, the ADM files that are provided with Windows Server include all policy settings for all operating systems, including those that are only relevant to Windows or Windows XP Professional. This means that only viewing a GPO from a computer with the new release of an operating system or service pack effectively upgrades the ADM files. As later releases are typically a superset of previous ADM files, this will not typically create problems, assuming that the ADM files that are being used have not been edited.
In some situations, an operating system or service pack release may include a subset of the ADM files that was provided with earlier releases. This has the potential to present an earlier subset of the ADM files, resulting in policy settings no longer being visible to administrators when they use Group Policy Object Editor.
However, the policy settings will remain active in the GPO. Only the visibility of the policy settings in Group Policy Object Editor is affected. Any active either Enabled or Disabled policy settings are not visible in Group Policy Object Editor, but remain active. Because the settings are not visible, it is not possible for the administrator to view or edit these policy settings. To work around this issue, administrators must become familiar with the ADM files that are included with each operating system or service pack release before using Group Policy Object Editor on that operating system, keeping in mind that the act of viewing a GPO is enough to update the ADM files in the GPT, when the timestamp comparison determines an update is appropriate.
The "Always use local ADM files for Group Policy editor" policy is typically used with this policy, when it is supported by the operating system from which Group Policy Object Editor is run. Also, frequent editing of GPOs can result in a significant amount of replication traffic. Using a combination of the "Turn off automatic updates of ADM files" and "Always use local ADM files for Group Policy editor" policy settings can greatly reduce the size of Sysvol folder and reduce policy-related replication traffic where a significant number of policy edits occur.
If the size of the Sysvol volume or Group Policy-related replication traffic becomes problematic, consider implementing an environment where the Sysvol does not store any ADM files. Or consider maintaining ADM files on administrative workstations. This process is described in the following section. When you use the "Always use local ADM files for Group Policy editor" policy setting, make sure that each workstation has the latest version of the default and custom ADM files.
If all ADM files are not available locally, some policy settings that are contained in a GPO will not be visible to the administrator.
0コメント