Detection Rules (optional)
Last updated
Was this helpful?
Last updated
Was this helpful?
Applies to: Patch My PC Cloud Custom Apps
If you want to configure Native Detection Rules:
On the Detection Rules tab, click Use Custom to use a custom detection rule, then choose the relevant type of rule from the Rule Type dropdown.
Note
You should only choose to use a custom detection method if our default method of scanning the uninstall registry on the endpoint to find a Display Name matching your Apps & Features Name entry and a Display Version that meets or exceeds the Version in the Configuration tab is unsuitable for this app.
Important
If you configure Detection Rules in the PMPC Cloud portal you:
Cannot deploy the same app in Publisher as Publisher does not support Native Detection Rules.
Should not create and manage detection rules in the Intune admin center as they will not be detected and shown in the PMPC Cloud portal.
Cannot mix our default detection method with custom detection methods for the same Custom App.
Go to Step 8 if you chose the Use Custom Script option.
If you choose the Configure Manually option, click Add Rule.
On the Add Detection Rule screen, select the relevant type of rule from the Rule Type dropdown, then configure the required options as required.
File
Path – The path to the folder you are checking for
File or Folder – The folder containing the file you are checking for
Detection Method – Choose from the list of available checks.
MSI
MSI Product Code – This is the MSI product code extracted from the file you imported.
MSI Product Version Check (optional) – Click this slider to enable this check for a specific version number that matches the options you configure in the Operator and Value fields.
Registry
Key Path – The path to the Registry key
Value name (optional) – The name of a value contained within the specified Key Path that you want to check for
Detection Method – Choose from the list of available checks.
Note
You can only create up to a maximum of 25 rules of all types per deployment. Of these 25, only one can be an MSI detection rule and the rest can be a mixture of File and Registry rules.
See the following Microsoft resources for more information:
If you have created either a File or Registry detection rule, click the Associated with a 32-bit app on 64-bit clients slider to enable it to expand any path environment variables in the 32-bit context on 64-bit endpoints.
Click Add Rule to add the rule.
The rule is added to the list of detection rules.
Note
You can:
Edit a Detection Rule by clicking the pencil icon beside the relevant rule, making the required changes then clicking Save rule to save the changes.
Delete a Detection rule by clicking the red trashcan beside the relevant rule to remove it from the list of rules.
Go to step 10 if you do not want to add a detection rule that uses the Use Custom Script option.
If you choose the Use Custom Script option, click Import Script, then browse to and select the relevant script you want to import.
Note
In the current version:
We only support PowerShell (.ps1) scripts
You can only import a single script
We do not sign your scripts if we use them in one of our deployments. If this is a requirement, you will need to sign the scripts yourself.
A preview of the script is shown in the Script Preview window.
Note
You cannot edit the script in the Script Preview window.
Click the Associated with a 32-bit app on 64-bit clients slider to enable it to expand any path environment variables in the 32-bit context on 64-bit endpoints.
Repeat the steps in this section to add any additional detection rules.
If you are happy you have entered all of the details for the app correctly, click Create to complete the creation of the Custom App. However, we recommend you click Next to move to the Summary tab where you can verify the configuration before saving the Custom App.
Note
You can use the Check Detection Rules process to verify your detection rules have been successfully created in Intune by PMPC Cloud.
