Share via


2.5.3.1 Configure Update Server - Server Management Tool

Goal: To configure the update server according to the deployment requirements.

Configuration options include:

  • Determining from where the USS receives updates.

  • Whether a DSS receives only updates from the USS or update deployments also.

  • Whether DSSs send detailed reporting data 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 synchronization is manually triggered by the WSUS administrator 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 Actor: 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:

  1. The server management tool identifies the relevant configuration elements that have changed.

  2. The configuration is modified according to input from the WSUS administrator.

  3. 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 based 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.