Superseding Applications
Use supersedence when you move to a new revision of a product. For example, you have FooApp version 1.0, and are currently deploying to multiple collections. When FooApp 2.0 releases, create a new application for FooApp 2.0. After you have verified success, you can supersede FooApp version 1.0 with FooApp version 2.0. Note that supersedence does not automatically execute an evaluation and installation. The new application must be deployed to a target collection to upgrade the application.
However, if an application was previously deployed as required, that software may automatically re-install. Notice that Figure 12.43 shows the Uninstall check box enabled. This instructs ConfigMgr 2012 to uninstall the previous version ...
Get System Center 2012 Configuration Manager Unleashed now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
