Custom Apps "Configuration" tab

Applies to: Patch My PC Cloud Custom Apps

The Configuration tab is where you configure various properties for the Custom App.

Note

Mandatory fields are denoted by an asterisk ("*").

Install Context

The Install Context setting (if available) configures the context in which the app is installed, either System or User.

"Install Context" setting

Architecture

The Architecture setting (if available) configures the app's architecture.

"Architecture" setting

Note

Detection uses this field to determine whether to look in the 32-bit or 64-bit registry keys:

HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall

or

HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall

Version

In the Version field, enter the version number for this app.

"Version" setting

Note

The number entered in this field is the version of the app as shown in Add or remove programs.

Detection uses this field to determine if the app is installed by looking for a matching DisplayVersion entry in the following registry key:

HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall

Language

In the Language field, either type the language for this app or select it from the dropdown list.

"Language" setting

Apps & Feature Name

In the Apps & Feature Name field, type the name of the app as it appears in Add or remove programs.

"Apps & Features Name" setting

Note

Detection uses this field to determine if the app is installed by looking for a matching DisplayName entry in the following registry key:

HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall

As this field allows a "%" wildcard (which matches on any string of characters), consider replacing the version number with this wildcard if the version number is in the Apps & Features Name.

This will allow App Detection and Update Requirement rules to detect older versions of the app on your endpoints.

Conflicting processes

In the Conflicting processes field, type a comma-separated list of executables that may interfere with the installation of this app. This field populates the list for the Manage Conflicting Processes right-click feature.

"Conflicting processes" setting

Silent Install Parameters

In the Silent Install Parameters field, enter the command-line arguments (up to a maximum of 2,048 characters) used to install the app silently (i.e. the user is not aware of the installation occurring).

"Silent Install Parameters" setting

Note

Providing msiexec.exe /i for MSI installations is not required. Using /qn will be adequate for most MSI installations.

Also, see Supported Variables in Publisher and PMPC Cloud for a list of the variables we support in this field.

MSI Product Code

In the MSI Product Code field, enter the MSI product code for this app which is used for detection.

"MSI Product Code" setting

Note

This setting only applies to MSI installers.

If the MSI Product Code for your installer does not update between versions, the Custom Apps Detection and Applicability rules will:

  • Not detect any changes and no updates will not be installed.

  • Detect the MSI app, even if an older version is installed.

To work around this issue, change the MSI Product Code to all 0's (00000000-0000-0000-0000-0000) when creating the Custom App. This forces the detection and applicability scripts to fall back to DisplayName and DisplayVersion detection.

Uninstall Command

By default, the Auto Discovered option is selected, which means we automatically generate the uninstall command by extracting the uninstall script from the app's PS1 file.

You can also add any additional parameters to use during the uninstall by entering them in the Additional Silent Uninstall Parameters field.

"Auto Discovered" setting

Return Codes

A Return Code (also referred to as an exit code), is a numeric value a program, process or function passes back to the calling entity (such as the operating system or another program) to indicate the outcome of the operation.

If you do not want to modify the Return Codes for this app, go to Next Steps.

Note

See the Return Codes (optional) section of Deploy an App for details on managing the Return Codes for a Deployment.

Also, if a Return Code defined in a Custom App has the same value but a different Code type to that defined in the deployment, the settings in the deployment take precedence.

Add A New Return Code

If you do not want to add a new Return Code, proceed to Edit a Return Code.

Adding a new Return Code

To add a new Return Code for this Custom App, enter the numerical value in the Return Code field, select its meaning from the Code type dropdown, then click Add.

Note

A Return Code must be a unique integer up to 10 digits long. You can add as many Return codes as your app supports. In the current release, you cannot edit or specify your own Code type as these are managed in Intune.

The new Return Code is added to the list.

New Return Code added to the list.

Edit a Return Code

If you do not want to edit a Return Code, go to Delete a Return Code.

Clicking the pencil icon beside a Return Code to edit it.

To edit a Return Code, click the pencil icon beside it, then choose the correct Code type for this Return Code from the dropdown list.

Choosing the correct “Code type” from the dropdown list

Next, click the green tick to save your changes.

Clicking the green tick.

The Code type field is updated.

“Code type” field updated.

Delete a Return Code

If you do not want to delete a Return Code, go to Next Steps.

Deleting a Return Code

To delete a Return Code, click the red trash can beside the relevant code.

The code is deleted from the list.

Code deleted from the list

Next Steps

If you want to configure Native Detection Rules for this app, click Next to go to the Detection Rules tab. If you do not want to configure Native Detection Rules, click Next twice to go to the Summary tab.

Last updated

Was this helpful?