Revision Summary Date Revision History Revision Class 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 3.1 Minor Clarified the meaning of the
technical content. 2/13/2014 4.0 Major Updated and revised 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. 10/16/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/26/2016 6.0 Major Significantly changed the technical content. 6/1/2017 6.1 Minor Clarified the meaning of the technical content. 12/15/2017 7.0 Major Significantly changed the technical content.
Determining from where the receives . Whether a receives only updates from the USS or update deployments also. Whether DSSs send detailed or just a summary of the computers they manage. Whether computer membership is based on groups that are assigned using client configuration or manual membership assignment on the server. Whether is manually triggered by the or set up to run on a schedule. Context of Use: This use case is initiated after the update server installation is complete and before the update server is used to service clients. Direct The direct actor of this use case is the server management tool. Primary Actor: The primary actor is the WSUS administrator. Supporting Actors: None. Stakeholders and Interests: The server management tool's primary interest for this use case is to enable a WSUS administrator to read and update the update server configuration. The primary interest of the WSUS administrator is to customize a Windows Server Update Services deployment to meet the requirements of the organization's environment. Preconditions: The update server is operational. Minimal Guarantees: None. Success Guarantee: If the server configuration is successful, the update server persists configuration changes to the server's local storage. If the server configuration is successful, the server components that depend on the configuration use the updates configuration to determine their behavior. Trigger: The server management tool triggers this use case on behalf of the WSUS administrator. Main Success Scenario: The server management tool identifies the relevant configuration elements that have changed. The configuration is modified according to from the WSUS administrator. The configuration is successfully saved to the data store. Extensions: The USS from which the update server receives updates. Whether the update server receives updates or update deployments from the USS. Whether DSSs of the update server send detailed reporting data or a summary only of the computers they manage. Whether computer membership is on groups that are assigned by using client configuration or by manual membership assignment on the update server. Whether synchronization is manually triggered by the administrator or set up to run on a schedule.
Index A Actors 18 18 31 15 16 21 18 C 28 44 6 Coherency requirements 30 30 30 30 16 17 16 17 with other systems external 17 17 16 17 16 16 Component dependencies external 17 17 17 16 17 17 5 Configure update 24 19 Considerations 31 30 D 7 Dependencies 17 16 17 17 with systems external 17 17 17 17 16 16 Design intent 18 21 configure update 24 19 27 20 22 26 18 23 18 37 6 E 16 29 Examples 37 initial 34 35 39 update 40 synchronization to DSS 33 configuration 34 34 32 33 34 Extensibility 43 28 16 F Failure scenarios 29 29 29 Functional requirements 15 12 overview ( 10, 11) 10 15 13 10 G
7 H 29 I 43 30 9 Initial 34 18 35 18 30 27 5 M 20 43 22 N 30 O Overview 15 12 5 11 5 10 15 16 10 13 5 P 18 43 R 9 30 7 Requirements 15 12 coherency 30 30 30 30 29 11 10 18 15 10 13 39 S 30 Server 6 6 6 5 15 26 18 23 System dependencies with other systems external 17 17 16 failure scenarios 29 29 29 requirements 10 use 18 21 configure update 24 19 27 20 22 26 18 23 16 16 29 16 10 System use cases 18 18 T 16 30 44 U Update 6