Revision Summary Date Revision History Revision Comments 9/23/2011 1.0 New Released new document. 12/16/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 3/30/2012 2.0 Major Updated and revised the technical content. 7/12/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Updated and revised the technical content. 11/14/2013 4.0 Updated and revised the
technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 9/24/2015 6.0 Major Significantly changed the technical content. 10/16/2015 6.0 None No changes to the meaning, language, or formatting of the technical content. 9/26/2016 7.0 Major Significantly changed the technical content. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content.
Ensure that policy setting management can be delegated as described in . Alter the default processing of policy settings. Configure a number of computers to execute administrator-specified code at computer start, computer shut-down, user logon, or user logoff, as described in . Preconditions: The Group Policy client is able to access the Group Policy server. Main Success Scenario The main success scenario can be summarized as follows: Trigger: Computer startup, user logon, or the periodic timer (sections and ) trigger this use case. When a trigger occurs, the Group Policy client successfully connects to the Group Policy server. The Group Policy client can query for applicable policy configuration settings from the Group Policy server. The Policy client successfully retrieves the policy information that is based on the results from queries. The Group Policy client applies the policy settings. Extensions Based on WMI filters, the Group Policy client decides whether to apply a specific GPO. Based on the policy source mode, as described in [MS-GPOL] sections 3.2.1.2 and 3.2.1.3, the Group Policy client obtains a set of GPOs that apply to itself. Administering Group Policy — Administrative Tool Context of use The initiates a task that is defined in the goal for this use case. Goal The goal of this use case is to create, update, and delete content. Actors Administrative tool: A tool that the Policy administrator uses to manage . This is the primary actor. The primary interests of the are to: Discover the . Ensure read and access to the Group Policy server. Manage Policy. Group Policy Server: A implementing that contains a database of GPO that Group Policy administrators can read and write to. The Group Policy server responds to requests from the Group Policy administrator. The primary interests of the Group Policy server are to: Support Administrative tool operations, such as creating, retrieving, modifying, and deleting GPOs that to groups of domain user and computer accounts in Active Directory Store and attributes configured by the Group Policy administrator Stakeholders
Index A 63 Administering group policy — administrative tool 57 44 Applying group policy — group policy client 55 Architecture 53 49 58 24 security ( 61, 63) 44 53 53 C 58 83 Coherency requirements 61 60 60 49 5 Considerations 63 61 D 53 57 55 53 54 E 49 58 64 Extensibility Microsoft implementations ( 64, 82) 58 F Functional architecture 53 49 58 24 security ( 61, 63) 44 53 24 G 17 H 58 I Implementations - Microsoft ( 64, 82) 61 22 53 61 5 M Microsoft implementations ( 64, 82) N 60 O Overview 44 24 5 P 53 82 R 22 61 Requirements coherency 61 60 60 58 24 53 S Security considerations ( 61, 63) 49 58 44 24 System use cases 57 55