Import Options / General Tab

AdminStudio 2024 R2 | 28.0 | Application Manager | Options Dialog Box

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

On the Import Options / General tab of the Options dialog box, you can configure several options that affect how packages are imported into the Application Catalog.

You can configure the following options:

Import Options / General Tab Properties

Property

Description

Application Name

You can define a format for naming the applications upon their import into an application catalog. You can leverage a list of pre-defined placeholders to define a naming format. The placeholder properties will be filled in automatically based on the value that AdminStudio extracts from the package during import.

This field is enabled only when you select Apply this naming format to all the applications while importing into the catalog check box.

By default, [ProductName]_[Version] naming format will be selected. You can make edits to change the default naming format.

You can add the following placeholders to define a custom name for the Application:

• [ProductName]
• [Vendor]
• [Version]
• [Platform]
• [SetupType]
• [Language]

Note:Enter the valid place holders and alpha-numerics in underscore-separated format with no gap:

For Example:

[ProductName]_[Vendor]_[Language]_Admin

[ProductName]_[Platform]_[Version]_[SetupType]_123

Note:If you use any other delimiter than underscore, a warning message will be shown and no action will be performed.

Apply this naming format to all the applications while importing into the catalog

If this option is selected, the defined application name format will be applied to all the applications while importing into the Application Catalog. You can define the application naming format in the Application Name field.

Note:When importing an application using the Import from Distribution system option, the ability to define a custom name is not supported.

Add custom detection script for Intunewin packages converted from EXE

When legacy package types (MSI/EXE) are converted to the Intunewin package, the detection methods from legacy packages are copied over to the Intunewin packages. If this option is selected, a custom PS1 script will be added as a detection rule to the Intunewin packages converted from legacy packages, especially EXEs, that do not already have detection methods. This PS1 script is customizable to meet your detection rules requirements.

By default, this check box will be selected.

Automatically Execute Tests After Import

If this option is selected, Application Manager will automatically test packages against all selected compatibility, best practices, and risk assessment tests as part of the import process. All of the tests selected on the Select Tests to Execute dialog box (other than those in the Application Conflicts category) will be run. By default, this option is not selected.

While having this option selected will mean longer import times for each application, packages will have all testing details populated immediately after import. However, if you are concerned with the length of import time, you may not want to select this option.

Note:If this option is not selected, no tests will be performed on a package immediately following import. To manually run the tests, select the package (or select the group that contains the package) and then click the Execute Tests button in the ribbon on the Analyze tab.

Note:In AdminStudio 2016, the Automatically Execute Tests After Import option was selected by default; in AdminStudio 2016 SP1, this option is no longer selected by default. Therefore, for users upgrading from AdminStudio 2016 to 2016 SP1, you will inherit the new default selection, which means that, by default, this option will not be selected and no testing will be performed immediately after import. To have the same user experience as you did in AdminStudio 2016, you need to select this option. In versions of AdminStudio prior to 2016, this option was not selected by default.

Integrate InstallScript Headers into Application Model Data

Extract the data in the imported package’s InstallScript header files. The InstallScript header data is used to help populate the basic application and package metadata (such as product code, product name, etc.).

Ignore Tables list

The Ignore Tables list displays all of the tables that will be ignored during import (not imported into the Application Catalog). You can select tables and delete them from the list, or you can add new tables to the list by clicking Add, which opens the Add Ignore Table dialog box.