Rollout and Update Process

Promoting a new package makes software available to your users. The first time you promote a software package, SDC builds an installer for users. The package configuration, i.e. the access policy, determines if it is available as a bundled or network-based installer, and if it is available from the included software portal web page. After you promote the first time, you can defer building installers for subsequent promotions.

To roll out updates to an existing package, make the desired changes to the package. Run through the testing phase again by verifying, building, installing, and committing to the delivery hub machine. To roll out changes to users, promote the package again, and build the installers. Users of the existing package are notified that an update is available. See End-User Installation & Update Experience for more information.

If you are making changes to a policy, you should commit and promote the policy change before committing and promoting changes to packages that use the policy. When a policy change is committed and promoted, committed and promoted packages that use the policy are automatically added to the Pending Promotion page. Users are not notified of an update when a policy is promoted; it is only after you promote packages that use the policy that users are notified of an update.

Note: If you are using advanced team delegation features to give more package control to team leads, you can learn more in Rolling Out Advanced Team Packages.

Committing vs. Promoting a Package

Committing and promoting each have their own purpose. When you create a package, you are doing so on your local desktop. No one can see it but you. When you get a package configured the way you want, use the Commit button to save the package to the hub machine. Once committed, a package can be seen by other administrators in their local Admin Console. Multiple admins can then collaborate on testing the package, testing on different platforms, for example. Each admin can use the Notes section to sign off on their testing.

After testing is complete, you want to roll out the package to your end users. This is when you use the Promote function. When you promote a new package, all the software components are combined into installers that your users access to install the end product. If you are updating an existing package, users receive notification of an update and can then update their software with your changes. You have the option to defer building new installers when you promote a package update.

Note: When promoting a new on-demand delivery package, no installers are built. These packages are accessed by users from the portal with a drag-to-install or by specifying an update site in Eclipse.