3 Deployment Type is Superseded
Display the history of application revisions
1. In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Applications node. Then choose the application that you want. 2. On the Home tab of the ribbon, in the Application group, select Revision History. This action opens the Application Revision History window.
Delete an application revision
1. In the Application Revision History window, select an application revision, and then select Delete. 2. Select Yes to confirm.ImportantYou can only delete the current application revision after you retire theapplication and it has no references.
Decide whether to upgrade or replace an application
The type of supersedence depends on whether you select the Uninstall option: * If you want to update to a newer version of the same application with the same application ID, don’t select Uninstall. * If you want to change to a different application with a different application ID, select Uninstall. You need to remove the superseded version of the application.
Fix Application Not Available to Select in SCCM Task Sequence Install
Application List Successfully Tested On: Microsoft System Center Configuration Manager versions 2012 – 1910If you are unable to see an application in the list to select when setting upthe Install Application step in an SCCM task sequence, there are a few commonreasons why.
1 – Application is not set as allowed to install
Each SCCM application has an explicit setting that allows it to be used duringtask sequences. This setting is found under the application’s Properties onthe General Information tab.The setting is called “Allow this application to be installed from the InstallApplication task sequence action without being deployed“:This setting is required specifically when install applications according todynamic variable list.
2 – Deployment Type requires a login
An application’s deployment types must be set to install the applicationwithout being logged in. If an application has multiple deployment types, thismust be true for every deployment type.This is controlled by two settings which are found under the deployment type’sProperties on the User Experience tab:The installation behavior must be one of the “Install for system” options, andthe logon requirement set to either “Whether or not a user is logged on” or“Only when no user is logged on“.The Installation behavior cannot be set to “Install for user” since thisforces the logon requirement to be “Only when a user is logged on”. Tasksequences install these applications outside of logins, so the applicationwill not show as available with the settings this way.
3 – Deployment Type is Superseded
An application deployment type that is superseded by another application willnot be available to install. Check for this by selecting an application andchecking the Deployment Types tab along the bottom, specifically looking atthe Superseded column: As always, be careful changing these settings if you’re unsure of what you’redoing as it could break the application.
If the application is the box, then the deployment type is the set of contentsin the box. An application needs at least one deployment type, as itdetermines how to install the app. Use more than one deployment type toconfigure different content and installation program for the same application.For example, your company has a line-of-business application called Astoria.The application developers provide the following ways of installing the app: * Windows Installer package for full functionality on Windows 10 devices * An App-V package for use in the terminal server farm * An web app for mobile usersYou create a single application for Astoria in Configuration Manager. Theapplication defines the high-level metadata about the app that’s common acrossall installation methods and platforms. You then create three deployment typesfor the available installation methods, and deploy the application to allusers. Based on the requirements and other configurations on the deploymenttypes, Configuration Manager determines the right method in each use case.For more information, see Create deployment types for the application.
A deployment action specifies whether you want to install or uninstall theapplication you’re deploying. Not all deployment types support the uninstallaction.For more information, see Deploy applications.
The deployment purpose specifies whether the deployment app is Required orAvailable: * The client automatically installs a required deployment according to the schedule that you set. If the application isn’t hidden, a user can track its deployment status. They can also use Software Center to install the application before the deadline. * If you deploy the application to a user as available, they see it in Software Center, and can request it on demand.For more information, see Deploy applications.
What application types can you deploy?
Configuration Manager lets you deploy the following app types: * Windows Installer (msi) * Windows app package and app bundles (appx, appxbundle, msix, msixbundle) * Windows app package in the Microsoft Store * Script installer for third-party installers and script wrappers * Microsoft App-V v4 and v5 * macOS * A non-OS deployment task sequence for complex appsAdditionally, when you manage devices through Configuration Manager on-premises device management, manage these further app types: * Windows Phone app package (xap) * Windows Phone app package in the Microsoft Store * Windows Installer through MDM (msi) * Web application
Get started creating an application
If you want to jump right in and create an application, you’ll find awalkthrough in the Create and deploy an application article.If you’re familiar with the basics and looking for more detailed referenceinformation about all the available options, start to Create applications.