MECM Detection Rules

If you are uploading an application with a custom detection method, you can set the detection method as Windows Installer, File attribute check, or Registry key value.

NOTE: The detection method is currently in XML format.

You can also define multiple detection rules by adding different detectionClause sections inside the detectionMethods section and setting the comparison between rules.

Example with two detection rules

In this example, the connector is set as "and", meaning both rules must be met in order for the MECM client to detect the installation.

Windows installer

Modifiable values:

• Connector: If you have multiple detectionClause sections, you can configure the link between detection methods. If you have only one detectionClause section, this value can be either one.
• ExpectedValue of the selected PropertyType. In general, this is the version of the Windows installer.
• ExpressionOperator: Comparison type
• PropertyType of the Windows installer. Recommend leaving as 'ProductVersion'
• ProductCode for the Windows installer

Template

Example 1 (Specific version) 

Example 2 (Any version)

File attribute check

Modifiable values:

• Connector: If you have multiple detectionClause sections, you can configure the link between detection methods. If you have only one detectionClause section, this value can be either one.
• Path to a folder containing your target file
• FileName
• ExpectedValue of the selected PropertyType. In general, this is the Windows installer version.
• ExpressionOperator: Comparison type
• PropertyType of the target file
• Value: Leave this as $true
• Is64Bit: Add this parameter with $true value to indicate that the target is 64-bit path. "This file or folder is associated with a 32-bit application on 64-bit systems." option is selected in detection method if you don't add this value at all.

Template

Example

Registry key value

Modifiable values:

• Connector: If you have multiple detectionClause sections, you can configure the link between detection methods. If you have only one detectionClause section, this value can be either one.
• Hive: Registry hive
• KeyName: Path to a target key
• ValueName: Name of target value
• ExpectedValue: Target value
• ExpressionOperator: Comparison type
• PropertyType of the target value
• Value: Leave this as $true
• Is64Bit: Add this parameter with a $true value to indicate that the target is 64-bit path. "This registry key is associated with 32-bit application on 64-bit systems" option is selected in detection method if you don't add this value at all

Template

Example