Deployment Templates

Deployment templates can store many of the software update deployment properties, and they can be created for consistency, to save time, or to fit your software update procedures. You can create a deployment template in the process of creating a deployment or automatic deployment rule and save the settings in a template. Table  shows the deployment properties that are saved in a deployment template.

Setting	Description
Collection	Indicates the collection that will be targeted for the software update deployment. This setting is optional when you make a deployment template.
Deployment Settings	Configured deployment settings such as Send Wake-up Packets or Verbosity Level are saved in the deployment template.
Deployment Schedule	Sets whether the user will be notified of pending updates, the installation progress for updates, whether the client evaluates the deployment schedule in local or Coordinated Universal Time (UTC), and the timeframe between when an update is available and when it is mandatory on clients.
User Experience	Hides software update installation and notifications. Sets the system restart behavior when an update installs on a client and needs to restart to finish. Also allows a system restart to be completed outside a maintenance window.
Alerts	Sets if alerts are generated for the in-console alerting feature. Sets whether Operations Manager alerts are disabled while updates install and/or send an alert if the install fails.
Download Settings	Sets how clients will interact with the distribution points when they get a software update deployment
Deployment Location	Sets whether to download the software updates from the Internet or a network file share.
Language Settings	Sets the language of the software updates that need to be downloaded and deployed.

Creating deployment templates in advance for typical deployment scenarios in your environment allows you to create deployments using templates that populate many of the properties that are most often static for the particular deployment scenario. Using the deployment template also reduces the number of wizard pages to work through in the Deploy Software Updates Wizard by up to seven pages, depending on what information you have already populated. This not only saves time but also helps to prevent mistakes when setting up a deployment