About the "Configurations" tab of a Patch My PC Cloud Deployment
Applies to: Patch My PC Cloud
The Configurations tab of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure various configuration settings (explained below) for how you want the app to be deployed.
The most common settings are displayed by default. You can configure additional, optional settings by either scrolling down the page until you find the relevant section or by clicking the relevant section heading.
Note
The icons beside each Tool's name have the following meaning:
Grey tick - Some values have been pre-configured by PMPC
Green tick - You have configured some values
Radio button - Neither you or PMPC have configured any settings.
The common settings you can configure on this page are:
Apply Template
This button allows you to apply a Template of pre-configured settings to this deployment.
Install Parameters
The Install Parameters section allows you to configure various installation parameters and arguments.
Install Parameter Summary
Shows any default installation parameters.
NOTE These cannot be modified or removed.
Additional Argument
Allows you to provide additional arguments to be appended to the installation command line. These can override the Patch My PC arguments in some cases (typically for MSI arguments). NOTE This field is limited to a maximum of 2,048 characters. See Supported Variables in Publisher and PMPC Cloud for a list of the variables we support in this field.
Conflicting Process
The installation of some apps cannot be completed if the app:
is currently running
uses a shared process that needs to be closed, but in doing so, could impact that process and other apps using it.
The Conflicting Process section lets you manage those conflicting processes (also known as "Conflicting Process"), and control what happens in such scenarios using one of the following options.
To manage the conflicting process for a Deployment:
Click the Conflicting Process tool.
Configure the required settings as detailed below.
Perform the installation
This is the default option for software that can install, update, or uninstall, even when conflicting processes are running.
Auto-close conflicting application process before installation
Automatically closes the app/process causing the conflict to allow this app to be installed.
Important
This can result in data loss, so use it with care.
Skip installation when conflicting processes are in use
The installation is skipped until the conflicting process is no longer in use. This will generate a 1602 error in the PatchMyPC-ScriptRunner.log and AppWorkload.log on the client side. In Intune, the status will shows as follows when you look under the Device/User Install Status blade of the package:
The user cancelled the app installation. (0x80070642)
Note
If the user snoozes/defers the update, Intune reports the installation as a failure and retries 24 hours later.
See Win32app Retry Interval – Demystified for more information about the retry behavior of Win32 packages in Intune.
This option can be configured with either of the following options:
Don't notify users - The user is not notified that the installation has been skipped because the app is open.
Notify user to close the app after trying silently for x days - The user will be notified to close the app after the app install is tried silently for the configured number of days (x), which can be from 1 to 100 days.
Notify the user to close the application
This is the default option for software that cannot successfully install, update, or uninstall when conflicting processes are running. The user sees a notification requesting they close the app, which is preventing this install. These apps will leverage your Branding.
Note
If the user snoozes/defers the update, Intune reports the installation as a failure and retries 24 hours later.
Tip See Manage Conflicting Processes when Updating Third-Party Applications - Patch My PC for a list of products we know will generally fail to update if they are in use.
Conflicting Process - Settings
Clicking the Settings button allows you to configure the following Advanced Settings for Conflicting Processes.
Notify Timeout Configuration
How long in minutes (5 by default and up to a maximum of 1,380 minutes with a 60-minute buffer) before the notification times out.
Notification Policy
Notification behavior if the application running and focus assist is enabled
How the notification behaves if the app is currently running and Focus Assist is enabled:
Discard the Notification (default)
Always show the notification
Show the notification if the deferred policy is reached
Do not allow user deferral
The user cannot defer the installation. The app will close and update when the timeout expires.
Allow the user to defer the installation
When an installation is postponed, Intune interprets the installation as a failure and automatically retries it 24 hours later.
Using this option, the user can defer the installation:
Indefinitely – If selected, Intune will retry the installation forever, giving the user the option to postpone it every 24 hours.
Up to X times - The user can postpone the installation for the configured number of times with a 24-hour gap between retries. Intune will retry the installation every 24 hours until the user has no more deferrals. At this point, the notification will appear, but without the option to Defer / Snooze.
First notification displayed – If a conflicting process is detected, the notification is shown immediately. The user can defer the installation or update up to the maximum number of days set in this option. During that period, Intune retries the installation about every 24 hours. If a conflicting process is still detected at a retry, the notification is shown again. Once the maximum deferral period is reached, the user can no longer postpone, and the installation will proceed.
If the timeout expired and no action is taken
Two options exist for this setting:
Defer the installation on behalf of the user (default)
Close the application and perform the update
Note
The Close the application and perform the update settings is incompatible with Modern (PSASDT) branding.
Prevent the application from being opened while it is updating
Prevents the app from opening whilst it is being updated.
Note
See the Update in progress section of Manage Conflicting Processes when Updating Third-Party Applications for more information about this option.
Conflicting Process - Conflicting Process
Clicking the Conflicting Process button lets you see any conflicting processes we have identified that will prevent an app from updating.
You can also add or remove entries to suit your environment.
Manage Return Codes
The Return Codes section allows you to configure Return Codes for a deployment (a Return Code is a numerical code an app typically logs and reports once it has completed running its installer).
You can manage Return Codes from within the properties of a:
Deployment
Custom App
Note
See the Configuration section of Create a Custom App for details on how to configure Return Codes within the properties of a Custom App.
Also, macOS apps also do not support Return Codes.
To manage Return Codes for a Deployment:
Click the Return Codes tool.
Note
The number beside the Return Codes tool shows the number of return codes currently configured for the app being deployed.
The default Return Codes defined for the app are shown, plus any defined for the app if this is a Custom App.
Note
If a vendor supplies a list of Return Codes for their app, we include it. If they don’t, we automatically populate the list of Return Codes with industry-standard codes.
If you do not want to add a new Return Code, proceed to Step 5.
To add a new Return Code for this deployment, enter the numerical value in the Return Code field, select its meaning from the Code type dropdown, then click Add.
The new Return Code is added to the list.
If you do not want to edit a Return Code, go to Step 9.
To edit a Return Code, click the pencil icon beside it.
Make any required changes.
Click the green tick to save your changes.
The Code type field is updated.
To delete a Return Code, click the red trash can beside the relevant code.
Note
You cannot delete either the default Return Codes for a deployment or any that have been added as part of the Custom App’s configuration. However, you can edit them.
If you add a Return Code to a deployment, you will be able to edit or delete it from the deployment if required.
Important
If the Return Codes you define in a deployment differ/conflict with those defined for a Custom App, the Return Codes defined on the deployment take precedence.
The code is deleted from the list.
App Info
The App Info section enables you to define default values for items that will be included in the app’s metadata when it is packaged to Intune.
Any values set for the following items will appear in the app’s properties when viewed in the Intune admin center:
Vendor* - The vendor of the app.
Owner – The name of the owner of this app.
Description* - A description of the app.
Notes – Notes about the app that we send to Intune when we create a deployment.
Information URL - Link to a website or documentation that has more information about the app.
Privacy URL - A link for people who want to learn more about the app's privacy settings and terms
Developer – The name/contact details of the developer as this is a plain text field.
Set App as Featured - If checked, allows this app to appear as a featured app in the Company Portal. Once the app has been deployed, the Show this as a featured app in the Company Portal setting on the app’s properties should be set to Yes in the Intune admin center.
* denotes a required field
Tip
If you make a mistake and want to reset the information in this section, click Reset to Default followed by OK on the Are you sure you want to reset to the default values? dialog box.
Also, if the App Info section has been configured, you can view it as part of the app’s properties in the Microsoft Intune admin center.
To manage the App Info for a Deployment:
Click the App Info tool.
Configure the settings as required.
Note
We pre-populate this screen with the information received from the vendor/added by us.
Desktop Shortcut
Remove Desktop Shortcut
If checked, will remove the desktop shortcut created as part of the app installation.
To configure this setting:
Click the Desktop Shortcut tool.
Configure the settings as required.
Built-in Auto Updates
If an app supports built-in auto-updates, this tool will be available, but the Disable Self-Update checkbox will be selected by default, disabling any auto-updates.
Note
Although some apps may have built-in auto-updates, they may not support controlling updates by using this or a registry value. In such a scenario, this option will be unavailable.
To manage the settings for the Built-in Auto Updates tool:
Click the Built-in Auto Updates tool.
Configure the required settings.
Available Uninstall
Allow Available Uninstall
If checked, allows Intune Apps to uninstall the app if the Company Portal installed it.
To configure this setting:
Click the Available Uninstall tool.
Configure the settings as required.
Requirements
Important
This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change.
Once this feature is released, it will be announced, and this banner will be removed.
The Custom Requirement Rules section lets you configure custom requirement rules.
OS Architecture Requirements
The OS Architecture Requirements section lets you specify which operating system (OS) architectures the app can be deployed to.
Note
The available checkboxes are determined by the Architecture setting on the General Information tab of the deployment.
For example, if on the General Information tab, the Architecture is configured:
As 64-bit, the 32-bit checkbox under the OS Architecture Requirements tool will be unchecked and cannot be checked.
As 32-bit, the 32-bit checkbox under the OS Architecture Requirements tool will be checked and cannot be unchecked. As this is a 32-bit app, the 64-bit checkbox is checked by default, but it can be checked.
You also cannot uncheck the checkbox on the OS Architecture Requirements tool that corresponds to the selected Architecture on the General Information tab.
The ARM checkbox on the OS Architecture Requirements tool can always be checked/unchecked, regardless of the Architecture configured on the General Information tab.
To manage the architectures for the Deployment:
Click the OS Architecture tool.
Click the checkboxes to select the relevant OS architectures for this deployment.
Next Steps
If you do not want to configure any additional settings, click Next to move to the Assignments tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
Last updated
Was this helpful?