Managing ConfigMgr (Formerly called as System Center Configuration Manager) Package Deployment Data

AdminStudio 2020 R2 SP1 | 20.01 | Application Manager

Edition:Application Manager is included with AdminStudio Professional and Enterprise Editions.

AdminStudio displays deployment data for all of an application’s packages (deployment types) in a multi-tabbed, organized format that is easy to navigate through and to update.

When a package is imported into the Application Catalog, Application Manager mines package elements for deployment data such as detection methods, dependencies, and requirements. You can view and modify this data and add new data by editing the properties on the subtabs of the Deployment Data tab and by using the easy-to-use wizards provided on the Detection Methods, Requirements, Dependencies, and Supersedence subtabs.

Using the subtabs of the Deployment Data tab of the Home Deployment Type View, you can perform the following tasks:

Specifying Package Content Deployment Data
Specifying Package Programs Deployment Data
Specifying Package User Experience Deployment Data
Specifying Package Detection Methods Deployment Data
Viewing Detection Methods for a Windows Store Application or MSIX Package
Viewing a Windows Store Application's Framework Customizations
Specifying Package Requirements Deployment Data
Specifying Package Dependencies Deployment Data
Specifying Package Supersedences Deployment Data
Viewing and Editing Return Codes
Changing the Priority of Deployment Types

Deployment Data and ConfigMgr (Formerly called as System Center Configuration Manager)

The data displayed on the Deployment Data tab of the Home Deployment Type View is used by ConfigMgr (Formerly called as System Center Configuration Manager) when deploying packages. This data corresponds to the application model data stored for applications and packages in Microsoft System Center 2012 Configuration Manager and later. When packages are published from the Application Catalog to ConfigMgr (Formerly called as System Center Configuration Manager), this data is also published, which helps to ensure successful deployment.

Importing external packages—When a package is imported into the Application Catalog, Application Manager mines package elements for this Microsoft System Center 2012 Configuration Manager application model deployment data.
Importing packages from Microsoft System Center 2007 Configuration Manager—When a package is imported from System Center 2007 Configuration Manager into the Application Catalog, Application Manager also imports detailed deployment data from Configuration Manager. This data will be useful to have when migrating this package to a System Center 2012 Configuration Manager application.

You can view and modify this deployment data and add new data by editing the properties on the subtabs of the Deployment Data tab and by using the wizards provided on the Detection Methods, Requirements, Dependencies, and Supersedence subtabs.

Setting Application Model Properties

When a package is imported into the Application Catalog, AdminStudio inserts default values for various Microsoft System Center 2012 Configuration Manager application model properties which cannot be extracted from the imported package. There are several ways to set the default values for application model properties that are assigned during application import. You can also edit the application model properties for packages already in the Application Catalog. For more information, see Setting Application Model Properties.

See Also