06 Implementing A Group Policy Infrastructure
06 Implementing A Group Policy Infrastructure
in
Module Overview
Understand Group Policy Implement GPOs Deeper Look at Settings and GPOs Group Policy Preferences Manage Group Policy Scope Group Policy Processing Troubleshoot Policy Application
www.technocorp.co.in
A centralized approach to applying one or more changes to one or more users or computers Group Policy: The framework for configuration management in an AD DS domain
Setting: Definition of a change or configuration Scope: Definition of the users or computers to which the change applies Application: A mechanism that applies the setting to users and computers within the scope Tools for management, configuration, and troubleshooting
Overview of Policies
www.technocorp.co.in
Divided between
User Configuration ("user policies") Computer Configuration ("computer policies")
Define a setting
Not configured (default) Enabled Disabled
Container for one or more policy settings Managed with the GPMC Stored in Group Policy Objects container Edited with the GPME Applied to a specific level in AD DS hierarchy
GPO Scope
www.technocorp.co.in
Scope
Definition of objects (users or computers) to which GPO applies
GPO Links
GPO can be linked to multiple sites, domain, or organizational unit (OU) (SDOU) GPO link(s) define maximum scope of GPO
Preference Targeting
How GPOs and their settings are applied Group Policy Client retrieves ordered list of GPOs GPOs are downloaded, and then cached Components called CSEs process the settings to apply the changes
One for each major category of policy settings: Security, registry, script, software installation, mapped drive preferences, and so on Most CSEs apply settings only if the GPO as a whole has changed Improves performance Security CSE applies changes every 16 hours GPO application is client driven ("pull")
User Configuration
Logon Every 90-120 minutes Triggered: GPUpdate command
Tools to report the settings that were applied and which GPO "won" in the case of conflicting settings Tools to model the effects of changes to the Group Policy infrastructure or to the location of objects in Active Directory
Implement GPOs
www.technocorp.co.in
Local GPOs Domain-Based GPOs Demonstration: Create, Link, and Edit GPOs GPO Storage Demonstration: Exploring Group Policy Settings
Local GPOs
www.technocorp.co.in
Local GPO
One local GPO in Windows 2000 Server, Windows XP, Windows Server 2003 Multiple local GPOs in Windows Vista and later Local GPO: Computer settings and settings for all users Administrators GPO: Settings for users in Administrators Non-administrators GPO: Settings for users not in Admins Per-user GPO: Settings for a specific user
If domain members can be centrally managed using domain-linked GPOs, in which scenarios might local GPOs be used?
Domain-Based GPOs
www.technocorp.co.in
www.technocorp.co.in
GPO Storage
GPO
www.technocorp.co.in
GPT
Stored in SYSVOL on domain controllers (DCs) Contains all files required to define and apply settings .ini file contains Version
In this demonstration, you will explore some of the thousands of settings in a Group Policy object
Policy settings in the Administrative Templates node make changes to the registry HKCU\Software\Microsoft\ Windows\CurrentVersion\ Policies\System
DisableRegeditMode 1Regedit UI tool only 2Also disable regedit /s
Administrative templates
Managed policy setting User interface (UI) is locked; user cannot make a change to the setting Changes are made in one of four reserved registry keys Change and UI lock are "released" when the user/computer falls out of scope Unmanaged policy setting UI not locked
Preferences
Effects vary
Administrative Templates
www.technocorp.co.in
.ADMX
.ADML
Registry
Central Store
www.technocorp.co.in
.ADM files
Stored in the GPT Leads to version control and GPO bloat problems
.ADMX/.ADML files
Retrieved from the client Problematic if the client doesn't have the appropriate files
Central Store
Create a folder called PolicyDefinitions on a DC Remotely: \\contoso.com\SYSVOL\contoso.com\Policies\ PolicyDefinitions Locally: %SystemRoot%\SYSVOL\contoso.com\ Policies\PolicyDefinitions Copy .ADMX files from your %SystemRoot%\PolicyDefinitions Copy .ADML file from language-specific subfolders (such as en-us)
Back Up all settings, objects, links, permissions (access control lists [ACLs]) Restore into same domain as backup Import Settings into a new GPO in same or any domain
Migration table for source-to-destination mapping of UNC paths and security group names
Replaces all settings in the GPO not a "merge"
What Are Group Policy Preferences? Differences Between Group Policy Preferences and Settings Demonstration: Configure Group Policy Preferences
www.technocorp.co.in
operating system and application settings that were not manageable using Group Policy
www.technocorp.co.in
Are written to the normal locations in the registry that the application or operating system feature uses to store the setting
Strictly enforce policy settings by writing the settings to areas of the registry that standard users cannot modify
Do not cause the application or Typically disable the user interface operating system feature to disable for settings that Group Policy is the user interface for the settings managing they configure Refresh preferences by using the same interval as Group Policy settings by default Are not available on local computers Refresh policy settings at a regular interval Are available through local Group Policy
In this demonstration, you will see how to configure some Group Policy Preferences
GPO Links
www.technocorp.co.in
GPO link
Causes policy settings in GPO to apply to users or computers within that container Links GPO to site, domain, or OU (SDOU) Must enable sites in the GPM console GPO can be linked to multiple sites or OUs Link can exist but be disabled Link can be deleted, but GPO remains
The application of GPOs linked to each container results in a cumulative effect called inheritance
Default Precedence: Local Site Domain OU OU (LSDOU) Seen on the Group Policy Inheritance tab
www.technocorp.co.in
OU
OU
At user logon, user settings from GPOs scoped to computer object are applied
Create a consistent user experience on a computer Conference rooms, kiosks, computer labs, VDI, RDS, and so on
Replace mode
User gets none of the User settings that are scoped to the user and gets only the User settings that are scoped to computer
Merge mode
User gets the User settings scoped to the user, but those settings are overlaid with User settings scoped to the computer. The computer settings prevail.
Detailed Review of Group Policy Processing Slow Links and Disconnected Systems Identify When Settings Take Effect
1. Computer starts; RPCSS and MUP are started 2. Group Policy Client starts and obtains an ordered list of GPOs that are scoped to the computer
Local Site Domain OU Enforced GPOs
4. 5. 6. 7.
User logs on Process repeats for user settings Every 90-120 minutes after startup, computer refresh Every 90-120 minutes after logon, user refresh
Group Policy Client determines whether link to domain should be considered slow link
By default, less than 500 kilobits per second (kbps) Each CSE can use determination of slow link to decide whether it should process Software CSE, for example, does not process
Disconnected
Settings previously applied will continue to take effect Exceptions include startup, logon, logoff, and shutdown scripts
Connected
Windows Vista and newer operating systems detect new connection and perform Group Policy refresh if the refresh window was missed while the system was disconnected
User must logoff or logon or the computer must restart for the settings to take effect Manually refresh: GPUpdate [/force] [/logoff] [/boot] Most CSEs do not reapply settings if GPO has not changed
Configure in Computer\Admin Templates\System\Group Policy
Resultant Set of Policy Generate RSoP Reports Perform What-If Analyses with the Group Policy Modeling Wizard Examine Policy Event Logs
Inheritance, filters, loopback, and other policy scope and precedence factors are complex RSoP
The "end result" of policy application Tools to help evaluate, model, and troubleshoot the application of Group Policy settings
RSoP analysis
The Group Policy Results Wizard The Group Policy Modeling Wizard GPResult.exe
Requirements
Administrative credentials on the target computer Access to WMI (firewall) User must have logged on at least once
RSoP report
Can be saved View in Advanced mode Shows some settings that do not show in the HTML report View Group Policy processing events GPResult.exe /s ComputerName /h filename
System log
High-level information about Group Policy Errors elsewhere in the system that could impact Group Policy
Application log
Events recorded by CSEs