Configuration
To read and edit the configuration settings, the user must have the required permissions, see Authentication and Authorization and Effective Permissions Authentication and Authorization and Effective Permissions.
Configuration settings
Intune
In this area Intune tenanta can be added, edited and deleted.
MECM
In this area Configuration Manager sites can be added, edited and deleted.
General
This area is used to configure (mandatory) defaults for creating applications from setup sources.
This includes naming conventions, return codes, and detection rule templates.
For each supported setup source (MSI, exe, ps1, cmd and vbs) different defaults can be defined.
General settings
| Marker |
Meaning |
| 1 |
Setup source selection. |
|
Activates/deactivates the edit mode. |
|
| Naming convention for the display name.
All available placeholders (built-in und Custom Properties) can be used. |
|
|
Command line for the installation. All available placeholders (built-in und Custom Properties) can be used. |
|
|
Command line for uninstallation. All available placeholders (built-in und Custom Properties) can be used. |
|
| Configuration of the return codes to be used. |
|
| Add Return Code. |
|
| Remove return code. |
|
| Selection of the detection rule template to be used. |
|
| 10 |
Can be either enabled or disabled for each configuration setting. If the setting is enabled, the default is mandatory for the user and the corresponding field in the Create from Setup Wizard is read-only. If the setting is disabled, the field is pre-filled in the Create from Setup Wizard, but the value can still be adjusted by the user. |
Placeholder
Placeholders can be used within the Display name, Install commandline and Uninstall commandline fields:
Intune Manager supports the following placeholders:
- {Language}
- {ProductCode}
- {Product]
- {Publisher}
- {SetupFile}
- {Version]
Additional placeholders can be defined via Custom Properties.
Script Search Patterns
Script Search Patterns can be configured for script setup sources (cmd, ps1 and vbs).
All available placeholders (built-in und Custom Properties) can be preset by specifying a Regular Expression.
Detection Rule Templates
Detection Rule Templates can be configured as defaults for creating applications from setup sources.
Mutliple templates can be defined and assigned individually to a setup co-configuration (see General).
A template always consists of a name and can contain n many recognition rules:
Supported detection rules
- MSI
- Registry
- Filesytem
All available placeholders (built-in und Custom Properties) can be used within detection rules.
Examples
MSI Rule:
Registry Rule:
Filesystem Rule:
Content Source Paths
When creating applications from setup sources , the sources must be selected from preconfigured file paths:
This area is used to configure these file paths.
File paths can be specified as local paths or UNC paths and must be accessible from the Intune Manager server.
The file paths are accessed in the context context (identity) of the Intune Manager pool
Custom Properties
When creating applications from setup sources, Intune Manager works with properties that are read from the source files. If these properties are not sufficient for naming, additional user-defined properties can be defined and used afterwards.
A good example of this is the Architecture property (32 bit or 64 bit). This property does not exist within an MSI file. However, if this property is defined, it automatically appears in the Create from Setup Wizard under the App information item, of an application or package.
Custom properties consist of the following values:
| Value |
Meaning |
| Type |
Defines which values may be entered:
|
| Name |
Display name |
| Placeholder |
Placeholder |
| Default value |
Default value |
Example of adding or editing a custom property of type Lookup:
Administrative Categories
In this section you can add, edit and delete administrative categories.
An application can be assigned to multiple administrative categories.
Status
In this area, status can be added, edited and deleted.
An application can be assigned exactly one status.
Publishers
In this section you can edit the list of known manufacturers.
Manufacturers can be added, edited or deleted.
This list is used as soon as the reading of the manufacturer from the source file is completed. Afterwards, an attempt is made to find a suitable manufacturer in this list, e.g. to correct incorrect specifications such as "Microsft" in "Microsoft".
Languages
In this area language-value pairs (key and replacement value) can be edited.
Language value pairs can be added, edited or deleted.
Intune Manager recognizes the stored language when importing source files (best for MSI files). Based on this list, e.g. German (Germany) becomes German.
