Deploy software updates

Applies to: System Center Configuration Manager (Current Branch)

The software update deployment phase is the process of deploying the software updates. Regardless of how you deploy software updates, the updates are typically added to a software update group, the software updates are downloaded to distribution points, and the update group is deployed to clients. When you create the deployment, an associated software update policy is sent to client computers, the software update content files are downloaded from a distribution point to the local cache on client computers, and then the software updates are available for installation from the client. Clients on the Internet download content from Microsoft Update.

Note

You can configure a client on the intranet to download software updates from Microsoft Update if a distribution point is not available.

Note

Unlike other deployment types, software updates are all downloaded to the client cache regardless of the maximum cache size setting on the client. For more information about the client cache setting, see Configure the Client Cache for Configuration Manager Clients.

If you configure a required software update deployment, the software updates are automatically installed at the scheduled deadline. Alternatively, the user on the client computer can schedule or initiate the software update installation prior to the deadline. After the attempted installation, client computers send state messages back to the site server to report whether the software update installation was successful. For more information about software update deployments, see Software update deployment workflows.

There are two main scenarios for deploying software updates: manual deployment and automatic deployment. Typically, you will start by manually deploying software updates to create a baseline for your client computers, and then you will manage software updates on clients by using automatic deployment.

Manually deploy software updates

You can select software updates in the Configuration Manager console and manually start the deployment process. You typically use this method of deployment to get the client computers up-to-date with required software updates before you create automatic deployment rules that manage ongoing monthly software update deployments, and to deploy out of band software update requirements. The following list provides the general workflow for manual deployment of software updates:

  1. Filter for software updates that use specific requirements. For example, you could provide criteria that retrieves all security or critical software updates that are required on more than 50 client computers.
  2. Create a software update group that contains the software updates.
  3. Download the content for the software updates in the software update group.
  4. Manually deploy the software update group.

For detailed steps, see Manually deploy software updates.

Automatically deploy software updates

Automatic software updates deployment is configured by using an automatic deployment rule (ADR). This is a common method of deployment for monthly software updates (typically known as "Patch Tuesday") and for managing definition updates. When the rule runs, software updates are removed from the software update group (if using an existing update group), the software updates that meet a specified criteria (for example, all security software updates released in the last month) are added to a software update group, the content files for the software updates are downloaded and copied to distribution points, and the software updates are deployed to clients in the target collection. The following list provides the general workflow to automatically deploy software updates:

  1. Create an ADR that specifies deployment settings.
  2. The software updates are added to a software update group.
  3. The software update group is deployed to the client computers in the target collection, if it is specified.

You must determine what deployment strategy to use in your environment. For example, you might create the ADR and target a collection of test clients. After you verify that the software updates are installed on the test group, you can add a new deployment to the rule or change the collection in the existing deployment to a target collection that includes a larger set of clients. The software update objects that are created by the ADRs are interactive.

  • Software updates that were deployed by using an ADR are automatically deployed to new clients added to the target collection.
  • New software updates added to a software update group are automatically deployed to the clients in the target collection.
  • You can enable or disable deployments at any time for the ADR.

After you create an ADR, you can add additional deployments to the rule. This can help you manage the complexity of deploying different updates to different collections. Each new deployment has the full range of functionality and deployment monitoring experience, and each new deployment that you add:

  • Uses the same update group and package which is created when the ADR first runs
  • Can specify a different collection
  • Supports unique deployment properties including:
    • Activation time
    • Deadline
    • Show or hide end user experience
    • Separate alerts for this deployment

For detailed steps, see Automatically deploy software updates

To submit product feedback, please visit Configuration Manager Feedback