Once the Update Lists are created, you need to set up the deployments. This is where you select the various deployment options and schedule. As explained in the Creating Update Lists section, Configuration Manager provides many ways to set up an update deployment. These sections reflect one way that I think should work well for many organizations. They will provide a good basis for understanding the process and make the alternative procedures clear. You should experiment in a lab setup to determine which is best for you.
- Expand the Update Lists section of the console, right click on the desired list, and choose Deploy Software Updates
- Select to create a new deployment package, and enter a name consistent with your standards
- If you have an existing Deployment Template that's appropriate, select it - otherwise select Create a new deployment definition
- The following steps assume you are creating a new definition, which can be saved as a template
- Select the collection to receive this deployment
- Select if users should be notified of the updates
- Select whether to base schedule on client local time or GMT time (default is GMT)
- Select the default postponement period, which can be overridden for any particular deployment
- Specify if restarts are allowed or suppressed for servers and workstations, and whether to allow restarts outside of the maintenance windows
- If you use MS Operations Manager, select actions you want taken - this is normally relevant only for updates to servers, and can enhance management reporting
- Set client download settings, just as in an SMS 2003 advertisement. Note that the default is not to install over slow or unreliable networks
- If desired, save these settings as a template using an appropriate name and description
- Use of templates allows the preceding steps to be skipped and guarantees use of consistent settings
- Create a Deployment Package or update an existing one
- This is what's copied to your DPs and deployed to the clients
- Normally you select Create a new deployment package
- Select a package name consistent with your naming standards
- For the package source point to an existing share on any server where you want the downloaded files stored, with the name of the Deployment package appended as a sub-folder. ConfigMgr will create that sub-folder, but the share must already exist
- Select enable binary differential replication if desired. This shouldn't hurt, but also is unlikely to normally be of use with supdates
- Select distribution points if desired. For large packages you may want to select just the location where they will be tested, and distribute to other DPs later
- Select to download updates from the Internet if deploying from your central site server, otherwise point to the share location on the server containing the updates
- Select the desired languages for the updates
- Set the deployment schedule
- Clients will begin downloading updates from their DPs at the Time Available
- If a deadline is set, updates will be applied automatically at that time if not scheduled earlier. If no deadline is set, updates will never be applied without user action
- Enable Wake On LAN if your organization uses it and if it's appropriate for this deployment under your standards
- Choose to ignore maintenance window if you want to override the deployment template setting
- Review the summary to be sure all actions are correct
- Updates are downloaded
- When the wizard is complete it reports success, warning or errors. Review and correct any warnings or errors as needed