Our powerful suite that transforms your data into dynamic, visually rich dashboards, offering everything from software and update compliance to detailed hardware and device insights, trend analysis, and threat detection
Contains links to the relevant Release notes page for each product
{% hint style="info" %}
**Note**
If you have any feedback or comments on our docs, please email .
{% endhint %}
# Patch My PC Product Release notes
*Applies to: All Patch My PC Products*
To help you easily locate the Release notes for each Patch My PC (PMPC) product, links to the respective pages are included below:
* [Publisher](/patch-my-pc-publisherv2/release-notes-for-patch-my-pc-publisher)
* [Cloud (includes Advanced/Patch Insights for Intune)](/patch-my-pc-cloud/release-notes)
* [CVE Insights](/patch-my-pc-cve-insights/release-notes)
* [Insights (Advanced and Patch Insights for Configuration Manager)](/patch-my-pc-insights/advanced-insights-release-note)
* [Return on Investment (ROI) Tool](/patch-my-pc-roi-tool/release-notes)
{% hint style="info" %}
Note
The current products do not currently have Release notes:
* [MEM Optimizer](/patch-my-pc-mem-optimizer)
{% endhint %}
# Patch My PC Cloud documentation
Official product documentation for Patch My PC Cloud
Release notes Latest product and feature updates for PMPC Cloud
Preview Features See the list of Preview Features coming soon to PMPC Cloud as we continue to innovate and evolve
About the Portal Learn about the Cloud Portal, the primary interface of PMPC Cloud
App Catalog The App Catalog contains all of the apps we currently support
Deployments Learn how to deploy and manage apps using PMPC Cloud
Update Rings Understand the Update Rings feature and how you can use it as part of your PMPC Cloud deployments
Events Understanding and working with events in PMPC Cloud
Migration Using the Migration feature of PMPC Cloud to migrate from ConfigMgr to Intune
Discovery Learn how you can use the Discovery feature to see which apps in our App Catalog are installed in your environment
Advanced/Patch Insights Learn how this feature of PMPC Cloud allows you to see a wealth of information about your organization that you can use to monitor, maintain, and enhance your environment
Manage How to perform various PMPC Cloud management-related tasks
Binary Free Apps How you can use PMPC Cloud to deploy and manage your paid apps
Custom Apps How you can use PMPC Cloud to deploy and manage your in-house apps
Intune Apps How you can use PMPC Cloud to deploy and manage apps using Intune
ARM Support Learn all about our support for ARM devices in PMPC Cloud
macOS Support Managing the macOS devices in your environment using PMPC Cloud
Troubleshooting When things go wrong in PMPC Cloud, how to fix them
Technical references Various technical reference articles about PMPC Cloud and its features
Product limits Learn about the various product limits of PMPC Cloud based on your subscription type
Glossary Definitions for the various terms and abbreviations we use
{% hint style="info" %}
**Note**
You can access this page from within the portal by clicking the support button () in the header area and selecting **Product Docs**.
{% endhint %}
# Release notes for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Details the production release history for Patch My PC (PMPC) Cloud, the most recent release being shown first.
{% hint style="info" %}
**Note**
We aim to release new features, updates, and fixes at 12:00 CEST every Wednesday.
*Production Release* means we have released that item to our Production environment i.e. customers can access it, although a specific feature maybe in one of the following three production states:
* Private Preview, which is invitation-only.
* Public Preview for which you will need to have [Preview Features enabled](/patch-my-pc-cloud/manage/settings/company-settings/preview-features) in your company to access it.
* General Availability (GA) which is available to everyone.
Please see the relevant docs for a feature for more information which will indicate the state of the feature, plus you can see a list of [Cloud Preview Features](/patch-my-pc-cloud/preview-features) for more information.
You can also access this page from within the Cloud Portal by clicking the support button () in the header area and selecting **Release Notes**.
Release Notes for previous years can be accessed using the following links:
[2025](/patch-my-pc-cloud/release-notes/2025) | [2024](/patch-my-pc-cloud/release-notes/2024)
{% endhint %}
## Week of July 22nd, 2026
**NOTE:** No release Week of July 15th
### Fixes
#### Custom Apps
* Resolved an issue where, after updating an existing script-based Custom App that uses a folder of files by using **Add Version**, the upload became stuck.
## Week of July 8th, 2026
Fixes
#### Portal
* Resolved an issue with Filter names for assignments being truncated.
## Week of July 1st, 2026
Fixes
#### Portal
* Resolved an issue with the Admin Portal where trial customers were incorrectly treated as having an invalid license, which prevented them from running a Full Resync.
#### Custom Apps
* Resolved an issue with a self-healing End-of-Life (EOL) enhancement that incorrectly marked Custom App deployments as EOL after adding a revision, as Custom Apps were not excluded from the EOL evaluation logic.
## Week of June 24th, 2026
Fixes
#### Custom Apps
* Resolved an issue where if a file upload was interrupted and the user started a new upload, background retries from the previous (deleted) file continued running and incorrectly updated the upload state, causing the Custom App to get stuck in an **In progress** state.
#### Intune Apps
* Resolved an issue with Snoozing notifications, where the “Snoozing notifications” days value in a deployment was not propagated to Intune, so the original value continued to be used.
* Resolved an issue where if a deployment failed to create a package, the previous AppId was also lost, preventing the system from tracking and deleting older app versions in Intune.
* Resolved an issue with requirements scripts where the requirement script generated in the Cloud Portal differed from the one sent to Intune.
#### Migration
* Resolved an issue when migrating script-based and PSADT apps, where the system automatically interpreted scripts without clearly informing users, which could lead to mismatches with the original logic.
###
####
## Week of June 17th, 2026
New Features/Improvements
#### Intune Apps
* **Permission Validation –** Improves the user experience by clearly showing which permissions the PMPC Company has/has not been granted in the Cloud Portal. Only the features that can be used with the granted permissions are enabled. All other features will be unavailable to help prevent errors.
#### Custom Apps
* Resolved an issue where if several files were uploaded for a Custom App and one failed, the whole upload failed. Now, if an upload fails, users can retry just the failed files.
* Resolved an issue with Intune failing to detect migrated 64-bit Custom Apps.
#### Intune Apps
* Resolved an issue where updating a custom uninstall script did not trigger regeneration of the deployment package, so the old script continued to be used even after recreating the deployment.
#### PSADT
* Resolved an issue with non-PSADT scripts failing to run if they define commands with the same name as PSADT commands.
## Week of June 10th, 2026
Fixes
#### Intune Apps
* Resolved an issue with deployment sync behavior that could remain stuck during multi-revision scenarios.
* Resolved an issue with category mapping behavior that prevented expected version updates.
* Resolved an error that blocked customers from creating deployments.
* Resolved a forbidden access issue when retrieving customer domains through Intune-connected workflows.
* Resolved a tenant device service error that caused endpoint failures.
#### Migration
* Resolved an issue with storage size messaging so that migration limits are displayed correctly in the UI.
## Week of June 3rd, 2026
New Features/Improvements
#### Intune Apps
* **Warning added to the Deployment Drawer –** If a deployment encounters an error, we now show the error on the deployment drawer (i.e. when you click the deployment).
Fixes
#### Intune Apps
* Resolved an issue where changing the Branding type from Classic to Modern did not display the correct version of the chosen log.
#### Managed Service Provider
* Resolved an issue where the name of the Parent Company was always included in the list of assignments for an App Set, even if the app was not assigned to the Parent Company.
## Week of May 27th, 2026
Fixes
#### Portal
* Resolved an issue where opening **Available Groups** in the Cloud Portal returned **An error occurred while processing your request** notification.
#### Custom Apps
* Resolved an issue where no validation message was displayed if either no value or an incorrect value was entered in the **Value** field when adding a Detection Rule.
#### Managed Service Provider
* Resolved a validation issue where an App Set could be created without an Assignment.
## Week of May 20th, 2026
Fixes
#### Binary Free Apps
* Resolved an issue where apps with partially uploaded binaries could not be deployed for variants that had completed binary uploads. We now allow deployments to proceed correctly when only some variants have been fully uploaded.
#### Custom Apps
* Resolved an issue where the deployment state of a Custom App was not updating correctly in the Cloud Portal.
#### Migration
* Resolved an issue where Custom Apps were assigned a **Failed** status during migration despite completing the process successfully.
* Resolved an issue where scripted Public Apps were incorrectly reclassified as Custom Apps after reanalysis, causing them to lose their assigned category.
## Week of May 13th, 2026
Fixes
#### Custom Apps
* Resolved an issue where the checkmark was not present in the **OS Architecture Requirements** section after updating the architecture for an app.
* Resolved an issue where silent install parameters were not saved after adding an app.
#### Intune Apps
* Resolved an issue handling Continuous Access Evaluation (CAE) claims challenges when connecting to Intune. This resolved connectivity issues for customers using CAE-enabled environments and improved access security validation.
* Resolved an issue where searching for an app name with and without spaces returned inconsistent results.
#### Migration
* Resolved an issue where the **Enable** button under **Enable Migration** remained visible when the **Enable Application Migration** checkbox was unchecked.
## Week of May 6th, 2026
New Features/Improvements
#### Portal
* **Improved Company Recovery process –** We have improved the process for recovering access to a PMPC Cloud Company to cater for more scenarios.
#### Custom Apps
* **Support for Unicode/non-ASCII characters –** You can now use Unicode/non-ASCII characters when creating and working with Custom Apps.
Fixes
#### Portal
* Resolved an issue where, if a Support Request was raised, an event was not written to the **Events** node.
#### Custom Apps
* Resolved an issue where, after creating a Custom App and providing silent install parameters, when you edited the app, these were mistakenly removed.
#### Intune Apps
* Resolved an issue where the **Installation Command line** field on the **Summary** tab of a scripted app appeared empty.
* Resolved an issue where deploying a discovered caused an error on the deployment page.
#### Migration
* Resolved an issue where PSADT apps were not migrated correctly from ConfigMgr.
## Week of April 29th, 2026
Fixes
#### Intune Apps
* Resolved an issue with ScriptRunner+ deployments with a command line exceeding 1,024 characters failed with the error "**CommandLine exceeds maximum allowed length of 1024 characters.**”
#### Managed Service Provider
* Resolved an issue where if an MSP admin impersonates a user account in the Cloud Portal, the remaining access time shown during impersonation does not match the actual granted access duration.
#### Migration
* Resolved an issue where migrating a 32-bit ARM app resulted in the app being migrated as ARM, but the 32-bit option was removed and greyed out.
* Resolved an issue with our AI being unable to process a script containing PSADT commands.
* Resolved an issue where not all ConfigMgr Apps were appearing in Migration.
## Week of April 22nd, 2026
New Features/Improvements
#### Advanced/Patch Insights for Intune
* **Improved Client/Uninstall –** We’ve made several improvements to how you install/uninstall the PMPC Client.
Fixes
#### Portal
* Resolved an issue where a user assigned just the **Report Admin** role was able to connect/enable the Microsoft Defender for Endpoint integration from Intune.
* Resolved an issue where, after a PMPC Cloud trial has expired, it is not possible to uninstall our Client as the **Save** button is disabled.
* Resolved an issue where if a new user (who is part of the customer’s organization) tries signing into Cloud using a custom domain name configured in the Cloud Portal, it fails to authenticate.
#### Custom Apps
* Resolved an issue where, during the Custom Apps creation process, apps that were still uploading (i.e. hadn’t finished being created) were shown in Publisher.
#### Migration
* Resolved an issue where if apps had "**.\\**" at the beginning of the installation file name in the .ps1 script and the AI toggle is enabled, PSADT apps are displayed as **Not Supported**.
* Resolved an issue where the **Display Name** for some apps is not displayed in the **App Update Status**.
* Resolved an issue where a Public app with options had the option to be migrated as an app with multiple matches instead of just a Public app.
## Week of April 15th, 2026
Fixes
#### Custom Apps
* Resolved an issue where after adding an additional script for PSADT to an existing Custom App, when installing the app on a VM, it failed with "**Failed to unzip**".
#### Intune Apps
* Resolved an issue with apps that use different languages for the Add/Remove Program entry, with ScriptRunner not searching for the app based on the RegEx of all possible names.
#### Migration
* Resolved an issue where some properties are not shown on the **Summary** tab during migration.
## Week of April 8th, 2026
Fixes
#### Binary Free Apps
* Resolved an issue where, even though all variants for some apps had been uploaded, the user still saw a prompt to upload a file.
#### Intune Apps
* Resolved an issue where the PMPC read-only script was displayed as unsigned when creating a deployment with an Update-only assignment.
#### Migration
* Resolved an issue where, during the analysis of an app, it was showing as being available for migration even though the analysis had not completed. Now an app will be unavailable for migration until the analysis has been completed.
* Resolved an issue where some properties completed during migration were not shown on the **Summary** page.
## Week of April 1st, 2026
Fixes
#### Portal
* Resolved an issue where adding an image to a support request resulted in an HTTP 500 error.
#### Binary Free Apps
* Resolved an issue where if an app has both binary and binary-free variants, the binary-free logic did not work.
#### Intune Apps
* Resolved an issue where customers were receiving different variants of the app or configurations than the ones they had originally set.
* Resolved an issue that when trying to edit an existing deployment, the following error was shown **Validation error on "getProductInfoByProductIdForDeployments", Expected object, received undefined.**
* Resolved an issue where an app fails to install if the Registry path contains custom requirements such as **HKLM:** or **Registry::**
* Resolved an issue where changing variants in a deployment did not update the list of **Tools** on the **Configuration** tab.
* Resolved an issue where after deleting an assignment for a deployment containing ESP Profiles, the ESP Profiles themselves were not reevaluated, potentially highlighting errors in their configuration.
#### Migration
* Resolved an issue when creating a deployment for an app that was previously migrated, resulting in **An error occurred while processing your request** error.
## Week of March 25th, 2026
New Features/Improvements
#### Intune Apps
* **Custom Requirement Rules –** The new Custom Requirement Rules feature has been released to Public Preview. This feature allows you to configure custom requirement rules directly in the Cloud Portal when deploying applications.
#### Managed Service Provider
* **Multi-variant support in App Sets –** You can now add the same app with different variants to the same App Set.
Fixes
#### Portal
* Resolved an issue where notification emails sent from the Portal either weren’t sent or came through blank.
#### Intune Apps
* Resolved an issue where, if a deployment was initially created without assignments, when editing the deployment, we allowed users to add Update Rings. This conflicted with the intended logic (deployments without assignments may rely on manual Intune assignments, and adding rings later could create inconsistencies). You can no longer add Update Rings when editing a deployment created without assignments.
* Resolved an issue where applying a deployment template to a deployment and then switching the **Installer Type** did not trigger the dialog warning that doing so would cause the values of the deployment to be reset based on the new installer type, potentially resetting those set in the template.
* Resolved an issue where applying a default deployment template cleared all existing form errors, even if the inputs were still invalid.
* Resolved an issue where unsupported deferral-related variables were allowed in various fields for localizations defined in Branding apps. The UI now shows the correct values under each relevant field.
#### Migration
* Resolved an issue where if an app was migrated from one variant to a different ProductId, the deployment could not be edited.
## Week of March 18th, 2026
New Features/Improvements
#### Portal
* **Ability to see your License Key –** Now, on the **Subscription** page, we’ve added an eye icon that lets you view your full license key.
* **“Apps & Feature” updated –** Given that Windows 11 uses the **Installed Apps** applet to view installed software, we have now renamed all instances of **Apps & Feature** in the product to **Installed Apps** instead.
* **Improved Visibility of Trial Limits –** Now on the **Subscription** page, we show you the product limits when you are using a trial account to help you familiarize yourself with the product and our different subscription levels.
Fixes
#### Portal
* Resolved an issue where if we had deployments for both a regular variant of an app and a Binary Free variant, after creating a deployment for the regular variant, validation would fail.
#### Custom Apps
* Resolved an issue where clicking **Add App** or **Add Version** for an existing Custom App resulted in an HTTP 500 error.
#### Managed Service Provider
* Resolved an issue where editing an App Set containing two variants of the same product caused broken deployments.
#### Migration
* Resolved an issue where if there were two updates available for an app, it generated an error. Now only the latest update is shown.
## Week of March 11th, 2026
New Features/Improvements
#### Migration
* **New Multiple Matches category –** Now, all apps with multiple matches in our App Catalog are displayed on the dashboard as **Multiple Matches**, so you know you need to select which app these apps should be migrated to.
* **New Scripted App Matching –** The Migration feature can now match scripted apps from ConfigMgr to a Public App Catalog app to allow you to migrate these apps as Public so you can keep them up-to-date.
Fixes
#### Portal
* Resolved an issue with the Template feature not validating the relationship between Update Ring delays and the Sync Schedule frequency. When the delay between rings was less than the Sync Schedule frequency, no warning was shown, which could lead to ineffective or misleading deployment timing.
#### Custom Apps
* Resolved an issue where clicking either **Add App** or **Add Version** (for an existing Custom App) resulted in an HTTP 500 error.
#### Intune Apps
* Resolved an issue where adding a new Detection Rule resulted in a **Type** of **0** and no content.
#### Managed Service Provider
* Resolved an issue where editing an App Set took an extended amount of time and resulted in an **AbortError:signal is aborted without reason** error.
## Week of March 4th, 2026
Fixes
#### Custom Apps
* Resolved an issue where deployments were not recreated on sync if extra files were present and the installation file was changed.
* Resolved an issue where deployments were recreated incorrectly in scenarios when they should not have been.
* Resolved an issue where a newly created Custom App is not visible in Publisher after it has been deployed.
#### Migration
* Resolved an issue where the failed validation (red ’**x**’) is shown on the **General** tab when migrating an app, instead of the **Files** tab, if the app being migrated has no **Installation Script** defined.
* Resolved an issue where the deployment status for a migration was not updated after a successful migration.
## Week of February 25th, 2026Fixes
#### Binary Free Apps
* Resolved an issue where if a user added a new version of a Binary Free App, any existing deployments could not be updated.
#### Custom Apps
* Resolved an issue where if a Custom App is deployed for the ARM architecture and then edited to uncheck ARM, the ARM option remains unchecked once the deployment is saved.
#### Intune Apps
* Changed the default timeout settings for Conflicting Processes Notifications to a maximum of 1,380 minutes with a 60-minute buffer before the notification times out to improve deployments.
* Resolved an issue where macOS deployments were recreated on the Sync Schedule even if the app that was deployed had not been updated.
* Resolved an issue where editing the deployment for an app and changing the assignment type and variant resulted in the app being recreated with a new revision. Now the app is recreated with the current revision whenever it is edited.
* Resolved an issue where if the **Disable the Patch My PC Recommended scripts** option was selected for a script that used a disallowed filename, the deployment could not be completed.
* Resolved an issue where if a user edits the **Notify Timeout Configuration** value for a deployment, the change does not appear in the **Installation time required** property in Intune.
#### Managed Service Provider
* Resolved an issue where if an app belonging to an AppSet is marked End of Life, any deployments to new customers of that AppSet get stuck **In Progress** and then eventually fail.
#### Migration
* Resolved an issue where the status of a migration was not updated to **Success** upon the successful migration of an app.
## Week of February 18th, 2026No release.
## Week of February 11th, 2026Fixes
#### **Binary Free Apps**
* Various fixes and improvements to how app updates are handled.
#### **Custom Apps**
* Various fixes and improvements to how app updates are handled.
#### **Intune Apps**
* Various fixes and improvements to how app updates are handled.
#### **Migration**
* Improved performance when migrating apps.
* Improved error handling by Publisher when migrating apps.
* Resolved an issue where the most matched app was shown in the middle of the list instead of the top.
## Week of February 4th, 2026Fixes
#### **Binary Free Apps**
* Resolved an issue where adding a new revision to an app did not trigger the email to the user informing them they need to upload the relevant file for the new revision.
#### **Custom Apps**
* Resolved an issue where adding a new revision to a Custom App did not force the associated deployment to be recreated.
#### **Intune Apps**
* Resolved an issue where, if a deployment has been manually recreated in between Sync Schedules, the deployment was recreated again at the next Sync Schedule.
## Week of January 28th, 2026New Features/Improvements
#### **Portal**
* **ConfigMgr to Intune App Migration** - [This feature](/patch-my-pc-cloud/migration) has now been releasd to General Availability.
* **Improved Webhook handling –** Now, if you have multiple Webhooks and one is invalid, the rest will still function. Previously, if one Webhook was invalid, it prevented notifications from being sent by other Webhooks, even if they were valid.
* **Improved Limits Warnings –** Now, when you reach 90% of the limits for your Cloud Company, we will display a banner warning you about this, so you can perform some housekeeping or consider upgrading to a different version with increased storage limits.
#### **Advanced/Patch Insights for Intune**
* [Officially released](/patch-my-pc-cloud/insights-intune) to General availability.
#### **Intune Apps**
* **Improved Intune Disconnection –** To help you better understand the consequences of [disconnecting your Intune connection](/patch-my-pc-cloud/manage/settings/connections/disconnect-connection#disconnect-intune), we now require you to take additional steps before we let you do this.
Fixes
#### **Managed Service Provider**
* Resolved an issue with the processing of App Set status messages in the wrong order, preventing App Sets from being edited.
#### **Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of January 21st, 2026New Features/Improvements
#### **Portal**
* **More Information on Preview Features –** A new [More Info](/patch-my-pc-cloud/preview-features) link has been added to the **Preview Features** section of the **Company** page. This links to our docs, where you can find out more information about each of the features currently in preview.
* **New "Report Admin” User Role –** This new user role only has Read-Only access to the **Reporting** and **Settings** nodes.
Fixes
#### **Portal**
* Resolved an issue where, for some Enterprise Premium customers, trial limits were being incorrectly enforced.
* Resolved an issue where editing a deployment with no assignments and changing the architecture resulted in older versions being removed from Intune. We now no longer support changing the architecture for a deployment with no assignments.
#### **Custom Apps**
* Resolved an issue where editing a Custom App caused the **Max Storage Limit** to be increased even if no additional files were added.
#### **Intune Apps**
* Resolved an issue where an app with several dependencies was not applying the dependencies correctly.
* Resolved an issue where if an app has multiple Windows assignments and a macOS deployment, editing the Windows deployment brings up details for the macOS deployment.
#### **Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of January 14th, 2026New Features/Improvements
#### **Intune Apps**
* **Updates to Public Apps –** Now when we update a public app in the App Catalog, we do not update the deployed version in your PMPC Company until the next Sync Schedule runs in your company.
Fixes
#### **Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of January 7th, 2026
Fixes
#### **Advanced/Patch Insights for Intune**
* Resolved numerous other issues as we continue to develop this feature.
#### **Intune Apps**
* Resolved an issue where editing a macOS deployment resulted in the **pkg** installer type being selected incorrectly instead of the **pkg (LoB)** option for LOB apps.
#### **Migration**
* Resolved numerous issues as we continue to develop this feature.
# 2025 Release notes for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Details the production release history for Patch My PC (PMPC) Cloud during 2025, the most recent shown first.
{% hint style="info" %}
**Note**
See [Release Notes](/patch-my-pc-cloud/release-notes) for details of the releases made throughout the current year.
{% endhint %}
## Week of December 17th, 2025
Fixes
**Advanced/Patch Insights for Intune**
* Resolved an issue where if a user deletes a device, an event is not written to the **Events** node.
* Resolved an issue when deploying version 1.0.54.17 of the PMPC Client being stuck as **In Progress**
* Resolved numerous other issues as we continue to develop this feature.
**Intune Apps**
* Resolved an issue where deleting a deployment with a status of **Retrying** does not delete the win32 app in Intune.
**Managed Service Provider**
* Resolved an issue when an MSP tries adding an AppSet to a customer, they get the **One or more customers do not have a valid Intune connection** error.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of December 10th, 2025
Fixes
**Portal**
* Resolved an issue where a deployment is synchronized and updated, but the wrong version of the app shows in the portal.
**Advanced/Patch Insights for Intune**
* Resolved an issue where displaying more information for a superseded app displayed **No Data** rather than the actual data.
* Resolved numerous issues as we continue to develop this feature.
**Custom Apps**
* Resolved an issue where an error is thrown when attempting to upload new files or new versions of files to an existing Custom App.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of December 3rd, 2025
New Features
**Portal**
* **Multiple Domain Support–** [A new feature now in Public Preview](/patch-my-pc-cloud/manage/settings/company-settings/multiple-domain-support) that allows you to configure multiple Entra ID custom domains for your PMPC Cloud company.
* **Multi-Language Support improvements –** For those apps that provide multi-language installers, we’ve now updated the metadata for those apps in our App Catalog instead of defaulting the language to en-US.
* **PSADT Branding –** A new notification style now in Public Preview that uses Fluent UI dialogs.
Fixes
**Portal**
* Resolved an issue with Discovery showing incorrectly some apps deployed by Publisher as **Unmanaged**.
* Resolved an issue where if you applied filters in the **Events** node and close them, when you re-open the filters the applied filters are no longer present.
**Intune Apps**
* Resolved an issue where, for some apps, there was a difference in versions between the UI and the **PatchMyPC.xml** (cab file).
* Resolved an issue when deploying an app and selecting the **Skip installation when conflicting processes are in use** setting, which was ignored, and the app was installed.
* Resolved an issue where if a macOS LoB PKG was created with **Install as managed** disabled, the deployment failed.
**Managed Service Provider**
* Resolved an issue where Premium subscription features were displayed for MSP license holders.
* Resolved an issue where a user invited to a company gets an error when accepting the invitation and creating a new company.
* Resolved an issue with App Sets not being shown on the **App Sets** page.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
**Reporting (Advanced/Patch Insights)**
* Resolved numerous issues as we continue to develop this feature.
## Week of November 26th, 2025
New Features
**ARM Support**
* Moved to General Availability.
**PSADT Support**
* Moved to Public Preview.
**Migration**
* Moved to Public Preview.
**Reporting (Advanced/Patch Insights)**
* Moved to Public Preview.
## Week of November 19th, 2025
New Features
**Intune Apps**
* **Improved support for macOS LOB deployments –** We have improved support and flexibility when deploying macOS Line-of-Business (LOB) apps.
**PSADT**
* **Improved deployment warning –** If the PSADT Module is enabled during a deployment and then scripts are added that contain PSADT functions, we now display a warning triangle to make you aware of this.
Fixes
**Intune Apps**
* Resolved an issue where clicking **Reset to Default** in a deployment cleared all fields of all values instead of resetting them to their default values.
* Resolved an issue for macOS LOB deployments where the LOB suffix was not shown in all relevant places in the portal.
**Managed Service Provider**
* Resolved an issue where clicking **Edit** to edit a deployed App Set resulted in an error.
**Migration**
* We no longer show apps that are retired in the list of unsupported apps.
**Reporting (Advanced/Patch Insights)**
* Resolved an issue where the **Reporting** node would disappear at the end of a trial.
## Week of November 12th, 2025
New Features
**Managed Service Provider**
* View App Set Details feature is now GA.
Fixes
**Intune Apps**
* Resolved an issue where if a deployment is created without any assignments and the **Copy Forward** option is disabled, when a new version of an app is released, any assignments from the previous version were deleted when the app version was updated. Now the following occurs:
* On the sync of a new version with **Copy Forward** disabled, all assignments for the previous version are kept.
* On the sync of a new version with **Copy Forward** enabled, all assignments for the previous version are removed and re-added to the new version.
* When a deployment is recreated with **Copy Forward** disabled, all assignments are deleted.
* When a deployment is recreated with **Copy Forward** enabled, all assignments are copied.
* Resolved an issue for macOS deployments where you could add macOS scripts even when uninstall assignments were present, leading to invalid deployment configurations.
**Managed Service Provider**
* Resolved an issue with some App Sets being stuck **In Progress**.
## Week of November 5th, 2025
New Features
**Intune Apps**
* **New Update Only Assignment behavior –** Now, when you deploy an app and add an **Update Only** Assignment, rather than hiding this option if it is not supported for the file type selected, we now show it as greyed out, along with a tooltip explaining why.
Fixes
**Portal**
* Resolved an issue with some optional configuration settings for a deployment not showing on the **Summary** tab.
**Custom Apps**
* Resolved an issue with being able to save an Uninstall script even if one hasn’t been entered.
**Intune Apps**
* Resolved an issue with PSADT scripts being incorrectly available for macOS apps.
**Managed Service Provider**
* Resolved an issue with the **Enable PSADT Module** checkbox being unavailable when editing an App Set.
* Resolved an issue where the **Subscription** node was still showing in the portal after the user accepted an invite from an MSP.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
**Reporting (Advanced/Patch Insights)**
* Resolved numerous issues as we continue to develop this feature.
## Week of October 29th, 2025
New Features
**Intune Apps**
* **ARM Support –** Support for ARM devices is now in Public Preview
Fixes
**Portal**
* Resolved an issue with incorrect results when sorting the portal by the **Architecture** column.
**Intune Apps**
* Resolved an issue where the **Scripts** tool was incorrectly shown when deploying a macOS **.dmg** installer.
* Resolved an issue where unsupported **Return Codes** were shown on the **Summary** tab of a macOS deployment.
* Resolved an issue where the **OS Architecture Requirements** tool was shown incorrectly for a macOS deployment.
**Managed Service Provider**
* Resolved an issue where, after a child company is unlinked from the parent, it is still listed at the parent.
* Resolved an issue where a **Validation error** is returned for an App Set after a child company that the App Set is targeted to is removed.
* Resolved an issue where an error notification was returned when attempting to downgrade from an MSP license, instead of the expected **Downgrading from an MSP Plus license is currently not supported** notification.
* Resolved an issue where the **Invitations** tab could not be opened when inviting users to an MSP company.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
**PSADT**
* Resolved an issue where the PSADT module was displayed incorrectly for a macOS app, as macOS does not support PSADT.
## Week of October 22nd, 2025
New Features
**Portal**
* **Increased Number of Templates –** You can create up to 200 templates in the portal.
**Binary Free Apps**
* **Ability to upload MSP Files –** We now support the uploading of **.msp** files for a Binary Free App.
Fixes
**Portal**
* Resolved an issue when setting a date for a Detection Rule, the calendar would close unexpectedly when clicking the back button.
**Intune Apps**
* Resolved an issue where if the **Additional Argument** field for a deployment contained more than 128 characters, it was ignored and the default argument was used instead.
**Managed Service Provider**
* Resolved an issue when inviting a user failed with **An error occurred while processing your request** error.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of October 15th, 2025
Fixes
**Custom Apps**
* Resolved an issue with a new version of a Custom App not being created in the Intune tenant.
**Intune Apps**
* Resolved an issue with the count for an ESP Profile not being updated immediately.
**Managed Service Provider**
* Resolved an issue with App Sets where if the assignments for an app were set to **All Users** and **All Devices** for one company, these same assignments couldn’t be used in different companies for the same deployment.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of October 9th, 2025
New Features
**Portal**
* **New “OS Architecture” Tool –** This new tool allows you to specify which operating system architectures and device types a deployment should be targeted to. Available for regular and MSP App Set deployments, as well as in the Migration Tool.
Fixes
**Portal**
* Resolved an issue with some x64 apps deploying as x86.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of October 1st, 2025
Fixes
**Custom Apps**
* Resolved an issue when editing a Custom App created for an EXE. After adding a Detection Rule for an MSI product code, the app could not be saved.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of September 24th, 2025
New Features
**Portal**
* **Custom Deployment Info -** You can now customize information about the app when creating a deployment.
Fixes
**Portal**
* Resolved an issue with apps in the App Catalog not sorting in the correct order when sorted by the **Last Updated** column.
* Resolved an issue with quote-related actions not appearing in the **Events** section.
**Binary Free Apps**
* Resolved an issue where the **Upload app** button was not shown after receiving a notification that a new version was available.
**Managed Service Provider**
* Resolved an issue where if an MSP uses an email address that doesn’t exist to send an invite, the event is recorded incorrectly in the **Events** section.
* Resolved an issue with **null** being added to the **Install Parameters** field when adding an app to an App Set.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of September 18th, 2025
Fixes
**Managed Service Provider**
* Resolved an issue where creating a new Child Company resulted in a **Validation Error**.
* Resolved an issue with AppSets being hidden after applying an MSP license.
**Migration**
* Resolved numerous issues as we continue to develop this feature.
## Week of September 10th, 2025
Fixes
**Intune Apps**
* Resolved an issue with multiple Teams notifications being received when a new version of an app is added and updated, instead of just a single notification.
* Resolved an issue with the Retention Policy being calculated incorrectly after editing an assignment.
**Managed Service Provider**
* Resolved an issue with an app being removed from an App Set still showing as being managed.
**Migration**
* Resolved an issue with a **.exe** ConfigMgr App with an MSI product code detection rule not being detected.
## Week of September 3rd, 2025
New Features
**Portal**
* **Notifications –** We’ve now added links to the relevant docs when setting up Notifications, based on customer feedback.
Fixes
**Portal**
* Resolved an issue when trying to delete a PMPC Cloud Company resulted in an **Error – Customer has active connections** message.
**Custom Apps**
* Resolved an issue when migrating a 64-bit app Custom App, with it being created with the **Any** architecture instead of **64-bit**.
**Managed Service Provider**
* Resolved an issue where Entra ID Groups were not displayed when creating an App Set using an invitation link for a Child Company.
## Week of August 27th, 2025
New Features
**Portal**
* **End-of-Life Apps –** Any apps that go End-of-Life (EoL) are now removed from our App Catalog.
**Managed Service Provider**
* **Number of Active Devices –** The MSP child customer list now has two columns: one for active devices in the last 21 days and another for active devices in the last year (including active devices in the last 21 days).
Fixes
**Portal**
* Resolved an issue with Microsoft SQL Server Management Studio 21 only supporting the **UpdateOnly** or **Install** assignment types.
## Week of August 20th, 2025
New Features
**Portal**
* **New User Profile feature –** When you click your user name in the top right-hand corner, you will now see a new **Profile** option that allows you to manage the details of your user account.
Fixes
**Portal**
* Resolved an issue with there being two separate entries in the App Catalog for Docker Desktop (one of each type of installer). There is now one combined entry.
* Resolved an issue with some apps not correctly supporting four-character language combinations such as “**fr-FR**” and defaulting to English.
* Resolved an issue when adding assignments for Branding with the “**All Users**” and “**All Devices**” groups not being shown.
## Week of August 13th, 2025
New Features
**Portal**
* **Changes to new trials –** All new trials of Patch My PC Cloud will default to our Premium SKU.
**Binary Free Apps**
* **Improved Error handling –** We’ve improved the error thrown if you try to migrate a Binary Free app and have not uploaded the installer beforehand.
**Intune Apps**
* **Editing a Deployment to use Update Rings –** Now, when you edit an existing deployment and configure it to use Update Rings, we show the start time for the Update Rings.
Fixes
**Portal**
* Resolved an issue where some customers stopped receiving summary emails of app updates.
**Intune Apps**
* Resolved an issue where deploying some specific apps using the English language caused some installers for other languages to be installed on devices.
* Resolved an issue where if a vendor changes an installer’s architecture (e.g., from x86 to Unspecified) in a new revision of their app, the system fails to match existing deployments for that app, which remain stuck on the old version.
**Managed Service Provider**
* Resolved an issue where accepting an MSP invite link did not show the list of Custom Apps relevant to the Child Company.
## Week of August 6th, 2025
New Features
**Portal**
* **Customer Feedback –** Now, when you complete certain workflows for the first time, we give you the option of providing feedback on your experience.
**Managed Service Provider**
* **MSP Invites –** Managed Service Providers (MSPs) can now send invitation links to customers, allowing them to self-register and create their own companies within the system to be managed by the MSP
Fixes
**Portal**
* Resolved an issue where the ConfigMgr version of an app migrated to PMPC Cloud was deployed instead of the newer version in our App Catalog.
**Binary Free Apps**
* Resolved an issue where if a customer uploaded a newer version of an app, an older version was deployed.
## Week of July 30th, 2025
New Features
**Custom Apps**
* **Uninstall Arguments –** We’ve now added the ability for you to specify uninstall parameters for a Custom App.
**Intune Apps**
* **PMPC Scripts –** You can now see and disable any scripts we recommend for an app when you create a deployment.
**Managed Service Provider**
* **App Set Details –** You can now expand an App Set to see a list of the apps it contains and summary information for each app within the App Set.
Fixes
**Portal**
* Resolved an issue with Microsoft SQL Server Management Studio 21, where assignments could only be created to either install or update this app. Now we support both.
**Custom Apps**
* Resolved an issue when creating a Custom App containing files with duplicate names but different extensions (e.g. **setup.exe** and **setup.zip**), generating a duplicate filename error.
**Intune Apps**
* Resolved an issue where attempting to add an assignment to an existing deployment failed with a **400 Bad Request** error.
**Managed Service Provider**
* Resolved an issue where adding a Child MSP company to an App Set containing a Custom App resulted in the app being stuck with a status of **In Progress** on the Child Company.
* Resolved an issue where adding a Child MSP company generated a **Bad request** error.
## Week of July 23rd, 2025
Fixes
**Portal**
* Resolved an issue with some users receiving an “**An error occurred while processing your request**” when working with Branding.
* Resolved an issue with a **Limit** showing as red when it reached 99%, not 100%.
* Resolved an issue with a Discovery data failing to load, sometimes with a **TypeError: Failed to fetch** error.
**Custom Apps**
* Resolved an issue with Custom Apps getting stuck at stage of 3/3 after editing.
**Managed Service Provider**
* Resolved an issue with assignments not being shown correctly for MSP App Sets.
## Week of July 16th, 2025
Fixes
**Portal**
* Resolved an issue where if the macOS trial banner was closed for one PMPC Cloud Company, if you logged into another company, the banner was also disabled.
* Resolved an issue with overlapping elements in the portal if a resolution lower than 1324 x 724px was used.
* Resolved an issue where if you had the **Remember my Selection** checkbox checked on the sign in page, then signed out, and selected a different company to sign into, you were signed into the company that was remembered, not the new one you selected to sign into.
**Custom Apps**
* Resolved an issue with an app’s icon not being displayed in a webhook when the deployment of a Custom App is updated via the Sync Schedule.
**Intune Apps**
* Resolved an issue when running Discovery for a new PMPC Cloud Company generating an error, which was resolved by clicking **Refresh**.
* Resolved an issue with the sorting of apps in Discovery not working correctly.
* Resolved an issue with excluding an Entra ID group from Branding now working.
**Managed Service Provider**
* Resolved an issue with adding a scripts and arguments to an MSP App Sets not being saved, as when you edited the App Set, the script and it’s arguments were missing.
## Week of July 9th, 2025
Fixes
**Portal**
* Resolved an issue with **Company Recovery** being referred to as **Tenant Recovery** in the **Events** section.
## Week of July 2nd, 2025
New Features
**Portal**
* **New “Items per page” options –** We’ve added new values to the **Items per page** dropdown in the portal to allow you to choose to display more items per page in the portal.
* **Increased character limits –** We now support 2,048 characters in the following fields:
* Install Parameters Additional Argument
* Silent Install Parameters
* Additional Silent Uninstall Parameters
**Custom Apps**
* **Version number replaced with “%” –** Now, when you add a Primary Install File that is an MSI, when populating the various properties, if we detect a version number in the **Apps & Features Name** field, we replace it with a "**%**".
Fixes
**Discovery**
* Resolved an issue where if a single Intune discovered app was mapped to two different products from our App Catalog, and one of them was managed and the other was unmanaged, one of them would appear under the **Managed** tab and the other would appear in the **Unmanaged** tab.\
\
Now, if one of them is managed and the other is unmanaged, the managed app is displayed in the **Managed** tab and the unmanaged app is hidden in the **Unmanaged** tab.
**Custom Apps**
* Resolved an issue with a Custom Apps icon not being shown in a webhook when its deployment is updated via Sync Schedule.
**Managed Service Provider**
* Resolved an issue with an MSP not being able to unlink a child customer if their license had expired.
## Week of June 25th, 2025
New Features
**Portal**
* **New "Usage" page –** We now show the usage limits for your PMPC Cloud company and your current usage to allow you to see when what you are using and when you are approaching a limit.
* **New tooltip for MSP deployments –** Now if you select the **.msp** installer when creating a deployment, we pop-up a warning that you will only be able add an Update Only assignment to this deployment and you should select the **.exe** installer if you want to use the other assignment types.
* **New default variant logic –** We’ve now replaced our existing language-only priority when creating a deployment with logic based on language, installation context, architecture, and installer type.
Fixes
**Portal**
* Resolved an issue with Entra ID Groups not being sorted alphabetically in the portal when searching to add them to an assignment.
## Week of June 18th, 2025
New Features
**Portal**
* **Granting PMPC Support Access –** We now provide a dropdown to allow you to choose the number of hours you want to grant our Support Team access to your PMPC Cloud company.
Fixes
**Portal**
* Resolved an issue when sorting by operating system within Discovery not sorting correctly.
## Week of June 11th, 2025
New Features
**Portal**
* **Improved UI for multi-versions –**Now if an app has multiple versions in the App Catalog that can be deployed, we indicate the number of versions available and allow you to select the relevant version you want to deploy from a dropdown on the app’s tile in the App Catalog.
**Intune Apps**
* **Ability to create an "Uninstall Branding" app –** You can now create this app which will create an Intune Win32 app, assigned as required with an uninstall intent, to remove any custom branding files from devices.
Fixes
**Intune Apps**
* Resolved an issue where a user could create a Windows Deployment Template with an ESP Profile and an Update Only Assignment. It should not be able to create such a combination.
## Week of June 4th, 2025
New Features
**Binary Free Apps**
* **Improved validation –** Previously, you could upload one bitness of an app, but attempt to deploy a different bitness. It was only when you got to the end of the Deployment Wizard that we informed you of this mismatch.
Fixes
**Portal**
* Resolved an issue with the text entered in the **Reason for Request** field when requesting access to a PMP Cloud Company not being populated in the portal.
## Week of May 28th, 2025
New Features
**Intune Apps**
* **Improved error handling for deployments when permissions are removed –** We have improved error handling for various deployment-related scenarios when permissions are either removed or amended when managing deployments.
Fixes
**Intune Apps**
* Resolved an issue with the incorrect error message being displayed when Company limits have been reached. We now show the correct error for the relevant cause.
## Week of May 21st, 2025
New Features
**Portal**
* **Templates –** You can now set the default type of Update Rings from within a Template.
* **Templates –** The **Tools** menu has been added to the **Configurations** page of templates to make it easier for you to navigate the various available sections.
Fixes
**Portal**
* Resolved an issue with the list of languages on the **Branding List** page showing the language that was configured first when it should be the default language.
* Resolved an issue where inserting a variable in the middle of text when defining naming standards actually inserted the variable at the end of the field and not at the chosen point in the text.
* Resolved an issue with **Exclude** filters configured on a deployment actually being applied as an **Include** filter.
**Intune Apps**
* Resolved an issue with Scope Tags manually added in Intune not being copied forward.
## Week of May 14th, 2025
New Features
Portal
* **Change to Self-Update template behavior –** Now when you create a Template, we check the **Disable Self-Update** option under the **Built-in Auto Updates** section by default (previously this was unchecked).
* **Change to Company Recovery option –** We’ve changed the language used for the **Company Recovery** section on the **Company** page to make it clearer.
* **New Update rings start time dropdown –** Previously, when creating a deployment, on the **Assignments** page, after clicking **Enable Update Rings** you had the choice of choosing to create either **Delayed** or **Immediate** rings. We’ve now moved the choices under a new **Update rings start time** dropdown, recommending **Delayed** and including tooltips to help guide you.
Fixes
**Custom Apps**
* Various bugs squashed to resolve issues with deployments getting stuck.
* Resolved an issue with the **Custom App Admin** not having access to the **App Catalog** page.
**Intune Apps**
* Resolved an issue with two deployments being created in Intune after a deployment with No Assignments is recreated.
* Various bugs squashed to resolve issues with deployments getting stuck.
## Week of May 7th, 2025
Fixes
**Intune Apps**
* Resolved an issue when adding extra files to an existing deployment (either through editing it or adding a new version) of those files missing from the deployment.
* Resolved an issue with config files larger than 28.6 MB failing to upload.
## Week of April 30th, 2025
New Features
#### Custom Apps
* **Improved error handling for macOS Custom Apps –** Previously, if you uploaded a **.pkg** or **.dmg** file as the primary installer file, we just showed an "**unsupported file**" notification. We now show the following notification:\
"Custom Apps for macOS are not supported at this time. Vote and subscribe to [PMPC Cloud Portal - macOS Custom Apps](https://ideas.patchmypc.com/ideas/PATCHMYPC-I-6056) to receive updates on future development."
Fixes
#### Intune Apps
* Resolved an issue with Detection Rules when configuring the time for a **Date Modified** rule, where if a PM time was selected, it was actually saved as the corresponding AM time.
## Week of April 24th, 2025
Fixes
#### Portal
* Resolved an issue with notifications not being sent to the webhook when deployments with no assignments failed when being created or updated. This issue also affected Slack.
* Resolved an issue with failed deployments not being shown in the Updates Report.
## Week of April 16th, 2025
New Features
#### Portal
* **Recommend App Dependencies now shown –** When you now create an App Dependency, we automatically show a list of recommended apps (if relevant) that you should consider configuring as dependencies for the app being deployed.
Fixes
#### Managed Service Provider
* Resolved an issue with Naming Conventions when adding the “`&`” character as a prefix, it actually being added as "`&`”.
## Week of April 9th, 2025
New Features
#### Portal
* **Additional filters added to help when working with Deployments –** The filter list in the portal now includes new filters to only show which deployments are using Update Rings (enabled or disabled) as well as which deployments have updates paused or not.
## Week of April 2nd, 2025
New Features
#### Portal
* **UI improvements for Deployment Properties –** We’ve improved the UI when looking at the properties of a deployment so as not to truncate entries such as script names.
Fixes
#### Portal
* Resolved an issue with older versions of Apps and Updates not being removed even after the portal syncs and when the older version has made it through update rings.
#### Intune Apps
* Resolved an issue with email addresses being displayed incorrectly when a deployment has a large number of update rings.
## Week of March 25th, 2025
Fixes
#### Binary Free Apps
* Resolved an issue with users not being notified of a new version of an app being available if either the **Notify All Users in Company** or **Notify Specific Users** options are selected.
#### Custom Apps
* Resolved an issue when uploading extra files with the same name but in different folders, the UI didn’t process the folder structure and instead uploaded all of the files as independent files.
## Week of March 19th, 2025
New Features
#### Portal
* **Number of available versions now shown for apps in the App Catalog –** If multiple versions are available for different variants of the same app, App Cat will show the number of available versions. If you hover over the number, you can see the list of variants grouped accordingly. If only one version is available for all variants, only that version will be displayed.
#### Intune Apps
* **Native Detection Rules –** Patch My PC (PMPC) Cloud deployments now support Native Detection Rules.
* **Pre/Post Scripts now support Arguments –** Our Pre and Post Scripts now support additional arguments.
Fixes
#### Custom Apps
* Resolved an issue with the logo defined for a Custom App not appearing in Intune.
## Week of March 12th, 2025
New Features
#### Portal
* **Deployment names don’t have to be unique per OS –** It is now possible to create a deployment with the same name as an existing deployment, provided the operating system being deployed to is different.
* **New “Product Docs” and “Release Notes” options added to the support menu –** Now when you click the Support Menu (**?**) you’ll see links to both the PMPC Cloud **Product Docs** and **Release Notes** to help you find the information you need to work with and keep up-to-date on what we’re doing with PMPC Cloud.
* **Changing certain settings on a deployment now warns you we are resetting other values –** Now if you change settings such as the installer type, architecture or installation context, you’ll be warned that doing so will reset all configurations from the other tabs because some settings are only available for specific options.
Fixes
#### Custom Apps
* Resolved an issue with browser hangs or crashes when uploading a large number of extra files.
* Resolved an issue with a **Reload site** prompt being displayed in error when saving a Custom App.
## Week of March 5th, 2025
No release.
## Week of February 26th, 2025
New Features
#### Intune Apps
* **LOB support added for macOS –** We now support deploying macOS Line-of-Business (LOB) apps.
Fixes
#### Custom Apps
* Resolved an issue with being unable to upload files of 0 bytes using the **Extra Files** feature.
#### Intune Apps
* Resolved an issue when uploading Extra Files using the **Add Folder** option, where if multiple files exist in any subfolder and they have the same hash, you see **Error File with the same hash already exists**.
## Week of February 19th, 2025
Fixes
#### Portal
* Resolved an issue with a Webhook notification showing as "Failed" for an Update Ring that was created successfully.
## Week of February 12th, 2025
New Features
#### Portal
* **Improvements to ESP Profiles workflow**
* You can no longer add an ESP Profile containing 100 or more apps to a deployment.
* If you and a single **Update Only** assignment to a deployment configured to use ESP Profiles, the **Configurations** tab is marked with a red “**X**” to indicate there is an issue.
* **Improved retry mechanism for deployments**
Fixes
#### Portal
* Resolved an issue with the Terms and conditions not being displayed when entering an MSP Plus license key.
* Resolved an issue with a user assigned the **Custom App Admin** role receiving a **Validation Error** when logging into an MSP Customer.
## Week of February 5th, 2025
New Features
#### Portal
* **Uninstall assignment type unsupported on macOS for PKG files –** Now when you deploy a .PKG file to macOS, we do not allow you to use the **Uninstall** assignment type.
#### Custom Apps
* Prevent an app deployment from being deleted from a parent MSP company if it is deployed at any child companies.
Fixes
#### Portal
* Resolved an issue with multiple copies of the daily deployment notification emails being sent with different content. We now check for the status of the deployment before sending the email and don’t include any deployments with a status of “Unknown.”
#### Custom Apps
* Resolved an issue with Custom Apps being unavailable in the App Catalog with users assigned the **Custom Apps Admin** role.
## Week of January 29th, 2025
New Features
#### Portal
* **Custom Pre and Post Scripts naming –** Now, if you upload a custom pre or post script to use in a deployment, we maintain the custom name rather than renaming it to a standard name.
* **Context Sensitive Searching is now supported in Scope Tags –** You can now type in the **Profile Name** field and we’ll automatically return a list of matching Scope Tags.
Fixes
#### Portal
* You can no longer disconnect a child company from an MSP Parent if there is not at least one user granted the **Full Admin with Access Management** role in the child company.
* Resolved an issue with Events not being written when pausing a deployment.
## Week of January 22nd, 2025
Fixes
#### Custom Apps
* Resolved an issue when changing the name of a vendor with mixed case, the name wasn’t saved to the Application Catalog. If the app is subsequently edited, the old, incorrect name is shown.
## Week of January 15th, 2025
New Features
#### Custom Apps
* Ability to upload additional files and folders when creating/editing a Custom App.
Fixes
#### Portal
* Resolved an issue with the **Update Only** App assignment type not being present for Custom Apps.
* Resolved an issue where if the **EnforcedUninstallArgument** was saved in the App Catalog, it was not used when creating an uninstall in a deployment
#### Intune Apps
* Resolved an issue with not being able to upload extra files with no name and just an extension.
## Week of January 8th, 2025
New Features
#### Portal
* **Extra Files –** We now support uploading files with the same name, provided they are in different folders. We also support uploading folders with the same name, provided the selected paths are unique.
## Week of January 2nd, 2025
Fixes
#### Intune Apps
* Resolved an issue with Update Rings where rings with retried deployments were duplicated in the daily notification email.
# 2024 Release notes for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Details the production release history for Patch My PC (PMPC) Cloud during 2024, the most recent release being shown first.
{% hint style="info" %}
**Note**
See [Release Notes](/patch-my-pc-cloud/release-notes) for details of the releases made throughout the current year.
{% endhint %}
### 18th December 2024
#### New Features
#### Portal
* **Entra ID Security Groups -** The ability to use [Entra ID Security Groups](/patch-my-pc-cloud/manage/settings/users/using-entra-id-security-groups) feature is now generally available (GA).
* **App Dependencies -** The [Dependencies ](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/dependencies)feature is now avialble in Public Preview.
#### Fixes
#### Binary Free Apps
* Resolved an issue with the validation for the **Additional Argument** field of a deployment not working correctly.
### 11th December 2024
#### Fixes
#### Portal
* Resolved an issue where an error was displayed when a user with the Read-only Admin role enables Pause Updates.
### 4th December 2024
#### New Features
#### Portal
* **Create a Deployment with No Assignments -** [This feature](/patch-my-pc-cloud/deployments/technical-references/deployment-without-assignments) has now been released.
* **Entra ID Security Groups -** The ability to use [Entra ID Security Groups](/patch-my-pc-cloud/manage/settings/users/using-entra-id-security-groups) feature is now in Public Preview.
* **Extra Files -** The [Extra Files](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/extra-files) feature (also known as *Deployment configuration files*) is now in Public Preview.
#### Fixes
#### Portal
* Resolved an issue with the portal not auto-refreshing the **Status** when creating a new deployment.
### 27th November 2024
#### New Features
#### Portal
* **New Visual Indicator for Public Preview Features –** If you have [enabled Preview Features](/patch-my-pc-cloud/manage/settings/company-settings/preview-features) in your PMPC Cloud company, we now show you how many and which Public Preview features you have enabled.
### 20th November 2024
#### New Features
#### Intune Apps
* **Support for Role Scope Tags -** We now support [Intune Role Scope Tags.](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/role-scope-tags)
* **Ability to enable auto-updates for an app –** If an app supports auto-updates, you can now choose whether to enable this behavior.
* **Script name auto-populated –** Now when you now import a script to a deployment, the **Script Name** field is auto-populated with the script’s name.
#### Fixes
#### Custom Apps
* Resolved an issue where Webhook notifications were not sent for some Update Rings.
### 13th November 2024
#### New Features
#### Portal
* **Restriction on M365x Tenants Starting a Trial -** We no longer allow customers whose Entra ID domain starts with **m365x** to start a Patch My PC (PMPC) Cloud trial. Such customers will not see the option to start a PMPC Cloud Trial and will either need to enter a PMPC Cloud license key or activate their license using their on-premises Publisher license key*.*
#### Fixes
#### Custom Apps
* Resolved an issue with Custom Apps becoming “stuck” or taking a long time to be created.
#### Intune Apps
* Resolved an issue with old versions of apps not being deleted from Update Rings.
* Resolved an issue with being unable to connect to Intune after deleting the connection for a linked MSP company.
### 6th November 2024
#### New Features
#### Portal
* **New service unavailable notification –** If one of our regional services is unavailable, you will now see a banner notification informing you of this.
#### Fixes
#### Portal
* Resolved an issue where enabling email notifications resulted in the first email showing all historical information, not just the relevant notifications.
* Resolved an issue with webhook notifications not being received if the payload exceeds 28kb.
### 30th October 2024
#### New Features
#### Intune Apps
* Various improvements to the daily update report email.
#### Fixes
#### Portal
* Resolved an issue with the **Install and Update App** no assignment type being available incorrectly when deploying a .MSP file.
* Resolved an issue with icons not appearing in AppCat after adding an app.
#### Intune Apps
* Resolved an issue where the **Add Assignment** button is unavailable if the Entra group for an existing assignment has been deleted from Entra. We now display an error and force you to remove the assignment in this scenario.
### 23rd October 2024
#### New Features
#### Intune Apps
* Maximum delay for an Update Ring has been increased to 180 days.
* Improved overall [language support](https://docs.patchmypc.com/installation-guides/patch-my-pc-cloud/deployments/deployment-wizard-reference#language)
#### Fixes
#### Intune Apps
* Resolved an issue where the email and webhook notifications were not received after creating a deployment with no assignments.
### 16th October 2024
#### New Features
#### Portal
* **New .MSP Installer Type added to AppCat –** We now support the .msp installer type in AppCat.
* **New “Read-Only Admin” user role –** This new role can view all pages in the portal but cannot make any changes. This role is intended for audit purposes.
* **New “Tenant Recovery” option –** If enabled, prevents a PMPC Company from being recovered using the [Recover Your Company](/patch-my-pc-cloud/manage/settings/company-settings/recover-company) process.\
*\[**NOTE:** You will need to contact support to get this feature enabled due to the potential consequences of enabling it.]*
* **Deployment method icon shown in Discovery –** When you view the **Managed** tab of Discovery, we show the method used to deploy the app i.e. PMPC Cloud, on-premises Publisher, or both.
* **Cooldown Timer for Company Recovery –** Recovering a company is now limited to three attempts every 12 hours.
#### Intune Apps
* **Warning when changing from Daily Sync Schedule –** We now have a new warning when changing your Sync Schedule from **Daily** as this can affect how Update Rings work.
* **Update Rings Deployment Summary warns if you are not using a Daily Sync Schedule –** When creating or editing a deployment that uses Update Rings, the **Deployment Summary** popup includes a warning against using anything but a **Daily** Sync Schedule with Update Rings.
* **Update Rings now detects the Sync Schedule –** If the Sync Schedule is configured to run on anything but a **Daily** schedule, Update Rings now forces the delay between Update Rings to align with the Sync Schedule.
#### Fixes
#### Portal
* Resolved an issue with the user’s first name and last name fields not being automatically populated on sign-up.
#### Custom Apps
* Resolved the **Unable to deploy. Product data was not found** error.
### 9th October 2024
#### New Features
#### Intune Apps
* **Deployments without assignments –** You can now create a deployment without assignments\
\[***Note:** You need to be using the Update Rings Feature currently in Public Preview to be able to use this functionality*].
* **Update Rings can now be updated at the Ring level –** You can now update a ring to any available version that is higher than the current version.
### 2nd October 2024
#### New Features
#### Portal
* **Discovery now shows the icon for an app –** [Discovery](/patch-my-pc-cloud/discovery) now shows the relevant icon for each app that’s managed/unmanaged.
* **Daily Updates Email Report includes newly created Deployments –** The daily Updates Report now includes the details of any new deployments created in the previous 24 hours \[***Note:** You need to be using the Update Rings Feature currently in Public Preview to receive the report with these improvements*].
### 25th September 2024
#### New Features
#### Portal
* **Discovery now shows Publisher apps –** The **Managed** tab of [Discovery](/patch-my-pc-cloud/discovery) now includes apps deployed by our on-premises Publisher.
* **Recommended default name for the Branding App –** We now provide a recommended default name for the branding app, which you can override.
#### Intune Apps
* **Update Rings \[PUBLIC PREVIEW] -** The [Update Rings](/patch-my-pc-cloud/deployments/update-rings) feature of Patch My PC (PMPC) Cloud allows you to deploy apps and updates in a phased manner across your Intune estate.
* **Increased number of characters for Additional Arguments -** The maximum number of characters you enter in this field has been increased to 500.
#### Fixes
#### Portal
* **Resolved truncating issue with App Cat app names –** When opened, apps with long names are no longer truncated but are displayed in full on the app’s properties page.
#### Binary Free Apps
* **Resolved “No Files Added” bug –** After uploading a new version of the app.
### 17th September 2024
#### New Features
#### Portal
* **Discovery –** The [Discovery ](/patch-my-pc-cloud/discovery)feature is now available in Public Preview. This feature lets you see which apps in our App Catalog are installed in your environment, including any Binary Free Apps or Custom Apps you may have added.
{% hint style="info" %}
**Note**
As this is a preview feature, you must [Enable Preview Features](/patch-my-pc-cloud/manage/settings/company-settings/preview-features) for the **Discovery** node to appear in your portal.
{% endhint %}
* **Folder installation log now shown –** We now show the path to the installation log in the new **Installation Logging** section of the **Summary** tab. We currently do not support changing this.
#### Fixes
#### Portal
* **Sync Schedule –** GMT is no longer shown in the UI of the [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) to avoid confusion.
### 11th September 2024
{% hint style="info" %}
**Note**
No public facing changes were made on the 4th September.
{% endhint %}
#### New Features
#### Portal
* **Company ID shown during recovery –** When you [recover a company](/patch-my-pc-cloud/manage/settings/company-settings/recover-company), we now include the company ID as well as the name of any companies you can recover in the **Company to Claim** dropdown.
#### Fixes
#### Intune Apps
* **Vendor Verbose Logging enabled –** Resolved an issue with vendor verbose logging not being enabled by default for IntuneSync.
* **On Restart Notifications incorrectly configured –** Resolved an issue where if the notifications for a deployment are configured for **On Restart**, the **Show All** option is actually selected on the dropdown, and not **On Restart**.
### 28th August 2024
#### New Features
#### Portal
* **Recover Your Company –** We now provide a facility for you to regain access to your company by using the new [Recover Your Company](/patch-my-pc-cloud/manage/settings/company-settings/recover-company) process.
### 21st August 2024
#### New Features
#### Portal
* **Latest Version added to app properties –** Now when you open an app’s properties, we show the latest version number.
#### Binary Free Apps
* **Link to vendor download –** When you upload the installer, we now provide a link to the official vendor’s website to ensure you download the most recent and official version.
### 14th August 2024
#### Fixes
#### Portal
* **Notifications –** Resolved an issue with emails not being sent for some apps after the daily sync job ran.
* **Users –** Resolved an issue where changing a user’s role resulted in several notification emails being sent instead of one.
#### Intune Apps
* **Naming Conventions –** Resolved an issue where any tag added after a string was not recognized.
### 7th August 2024
#### New Features
#### Portal
* Link to product documentation added to the support menu.
* **Users –** The portal now displays a confirmation if you try deleting yourself.
#### Custom Apps
* **Improved App Icon UI –** We now show the supported file types in the UI for the **App Icon**.
#### Intune Apps
* **Improved language support -** English variants are now exposed. Previously, we only exposed **English** as a language for apps. We now expose all available variants such as **English - Canada**, **English - United Kingdom**, **English - United States**, etc.
### 31st July 2024
#### New Features
#### Intune Apps
* **Update-only assignments for user-based apps –** You can now create update-only assignments/packages with Intune Apps in the same way as you can with our OnPrem Publisher.
#### Fixes
#### Custom Apps
* Resolved an issue with **Silent Install Parameters** not being copied over when adding a new version of an app.
### 24th July 2024
#### New Features
#### Portal
* **Sync Schedule changed to UTC –** To help avoid confusion, the **Sync Schedule** time is now based on [Coordinated Universal Time (UTC)](https://simple.wikipedia.org/wiki/Coordinated_Universal_Time).
#### Fixes
#### Portal
* **Customer Support –** Resolved an issue with being unable to edit a timer with less than 4 hours remaining.
#### Custom Apps
* **Deployments –** Resolved an issue with some Custom Apps being stuck with the status of **Retrying**.
### 17th July 2024
#### New Features
#### Portal
* **Ability to opt-in to Preview Features –** You can now opt-in to automatically gain access to pre-release features we mark as Public Preview.
* **Customer Support feature re-designed –** You can now set a timer to limit the amount of time Patch My Support has access to your environment and the level of access.
* **Test buttons for Notifications –** New buttons to allow you to send test notifications/emails when setting up Notifications to check they are configured correctly.
#### Intune Apps
* **Allow Available Uninstall –** You can now configure a deployment to allow an app installed by the Company Portal to be uninstalled by Intune Apps.
* **Increased upload limits for pre/post scripts –** Previously, the total size of all pre/post scripts for a deployment was limited to 1 MB. This has now been increased to 1 MB per script, with a total size limit of 4 MB.
#### Fixes
#### Portal
* **Deployments –** Resolved an issue with the Edit button not being displayed if an app has already been successfully deployed.
#### Custom Apps
* Resolved an issue with the MSI Product Code being displayed for a Custom App created with an EXE as the primary installer file.
### 10th July 2024
#### New Features
#### **Portal**
* **Improved sorting by column –** Columns can be sorted by more headings in various nodes when working in the portal.
* **Improved user access requests —** Users can now enter a message giving more information about why they are requesting access to a company.
* **Improved access denied flow –** Admins can now provide a reason for declining a user's access request.
* **Revoking Access Management rights warning –** Now if you try to revoke Access Management rights for your account, provided at least one other account has this right, you will still be prompted if you are sure you wish to proceed.
* **Search –** General improvements to search.
* **Sync Schedule –** The new [Sync Schedule](https://docs.patchmypc.com/patch-my-pc-cloud/administration/managing-the-sync-schedule) feature allows you to set a different time and frequency for the sync job to run.
#### Fixes
* **Branding –** Resolved an issue where uploading a new logo with the same name as the existing one shows the old logo.
* **Notifications –** Resolved an issue with Teams and Slack notifications cutting off CVE data and not containing release notes.
* **Update reports –** Resolved an issue with the formatting of file sizes on the deployment email report.
### 3rd July 2024
#### New Features
#### Portal
* **Users –** Now you cannot remove the **Access Management** right for the last admin user in your company. This prevents you from locking yourself out of the portal. If you are the last user and there is at least one other account with this right, if you try revoking it from your account, you are prompted to confirm because of the consequences.
* **Users –** The **Application Deployment Admin** user role has been renamed **Intune App Admin**.
#### Intune Apps
* **Naming Conventions -** You can now use the new [Naming Conventions](/patch-my-pc-cloud/manage/settings/naming-conventions) feature to configure custom naming conventions for all deployments created in Intune Apps for Cloud. This allows you to standardize the naming convention across all your Intune deployments.
#### Fixes
#### Portal
* **Deployments –** Resolved an issue with two Update-only apps being created in Intune if the first one fails. Now, if an app fails to be created in Intune, we delete it.
* **Onboarding –** Resolved a sign-in issue when a user accepts an invitation.
#### Custom Apps
* Resolved an issue with the **Naming** page not being accessible.
### 26th June 2024
#### New Features
#### Portal
* New [Intune App Admin ](https://docs.patchmypc.com/patch-my-pc-cloud/reference/user-roles)user role added.
* **General –** Clicking our logo in the top left-hand corner of the portal returns you to the App Catalog and forces a refresh.
#### Fixes
#### Portal
* **App Catalog –** If the name of an app is truncated, hovering over it now shows the full name as a tooltip.
* **Contact Form –** Resolved a memory exception error when sending attachments to us through the Contact Form in the portal. You can now send up to 25 MB of attachments when using this form.
* **Deployments –** Resolved issues :
* with **Pause Updates** being disabled when editing an existing deployment where **Pause Updates** has been enabled.
* when editing a deployment, any required assignments with an availability date set to **ASAP** are not modified until the next day at 12 AM.
* **Deployment Filters –** When adding a deployment filter to an app deployment, we now only show filters for the **Windows 10 and later** platform, instead of all filters.
* Various improvements to notification messages and tooltips to improve readability.
#### Custom Apps
* Resolved an issue with the user being able to add the same conflicting process multiple times when creating a Custom App. We now do validation to prevent this.
### 19th June 2024
#### New Features
#### Portal
* **Contacting Support –** You can now modify the **From** email address when using the [Contact Support](https://docs.patchmypc.com/patch-my-pc-cloud/contacting-support) form.
* **Environments node –** New [Reconnect ](https://docs.patchmypc.com/patch-my-pc-cloud/administration/managing-your-environments/managing-intune-tenants#reconnecting-an-intune-tenant)button added under the **Intune** connection.
* **Licensing –** If you already have an active license with us and click **Start Trial**, we detect this and use your existing license to activate your portal.
* **Notifications node –** New tooltips have been added so you know when you will receive notifications.
* Primary buttons in the UI re-designed based on user feedback.
#### Fixes
* Various improvements to notification messages and tooltips to improve readability.
### 5th June 2024
#### Fixes
* The “**Prevent from opening an application while the application is updating**” checkbox is no longer checked by default on the **Conflicting Processes** settings pop-up.
* Resolved an issue with the configuration of Conflicting Processes not being honored.
* Various other bugs.
# Preview features of Patch My PC Cloud
*Applies to: Patch My PC Cloud*
The following is a list of Patch My PC (PMPC) Cloud *Preview Features.*
{% hint style="danger" %}
**Important**
You need to have [Preview Features enabled](https://docs.patchmypc.com/patch-my-pc-cloud/cloud-administration/manage-your-cloud-company/enable-cloud-preview-features) in your company in order to access them.
Preview Features may not be fully functional or may contain bugs. By enabling them, you agree to accept that you may encounter some functionality issues and bugs.
Enabling Preview Features on a parent MSP company does not automatically enable them for child customers.
{% endhint %}
Links to the relevant documentation are included when available.
{% hint style="info" %}
**Note**
Once a feature is released to General Availability (GA), it will be removed from the following list as it will be available to everyone.
{% endhint %}
Feature Name
Description
Deployments Bulk Actions
This functionality allows you to perform certain deployment-related tasks on more than one deployment at a time.
Deployments Extra Filtering Options
This update adds several new filters that make it much easier to locate deployments based on their configuration or assignment types.
Msi Source Health Dashboard
A new dashboard.
Multiple Matches Migration
If we match an app being migrated from ConfigMgr to Cloud to more than one app in our catalog, we give you the option to choose which app to migrate it to.
Permissions Validation
Improves the user experience by clearly showing which permissions the PMPC Company has/has not been granted in the Cloud Portal. Only the features that can be used with the granted permissions are enabled. All other features will be unavailable, helping prevent errors.
# Supported configurations for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Patch My PC (PMPC) Cloud supports deploying apps and updates to the following app types and platforms:
* [Binary Free Apps](/patch-my-pc-cloud/binary-free-apps/binary-free-apps-overview)
* [Custom Apps](/patch-my-pc-cloud/custom-apps/custom-apps-overview)
* [Intune Apps](/patch-my-pc-cloud/intune-apps/intune-apps-overview)
* [ARM](/patch-my-pc-cloud/arm-support)
* [macOS](/patch-my-pc-cloud/macos-support/macos-support-overview)
# Prerequisites for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To use Patch My PC (PMPC) Cloud, you need:
* An Internet connection that can access Microsoft Azure services and the Patch My PC (PMPC) Cloud Platform ().
* A Microsoft Entra ID tenant
{% hint style="info" %}
Note
We currently do not support [GCC High tenants](https://learn.microsoft.com/en-us/office365/servicedescriptions/office-365-platform-service-description/office-365-us-government/gcc) for Patch My PC Cloud. You can help us prioritize this [feature](https://ideas.patchmypc.com/ideas/PATCHMYPC-I-4260).
Patch My PC Cloud supports authentication through Microsoft Entra ID only. Direct SSO with third-party identity providers such as Okta or PingFederate is not currently supported.
Patch My PC Cloud does not expose SAML or OIDC endpoints for customer-managed third-party IdP integrations. As a result, third-party IdPs cannot federate directly with Patch My PC Cloud, and Patch My PC Cloud cannot directly consume or validate assertions, tokens, or MFA claims issued by those providers.
{% endhint %}
* An Enterprise Plus, Enterprise Premium, or Managed Service Provider (MSP) Plus subscription.
{% hint style="info" %}
**Note**
With an MSP Plus subscription, you can manage any number of devices. However, there is a minimum monthly charge based on 50 devices per tenant.
{% endhint %}
{% hint style="warning" %}
**Important**
We no longer allow customers whose Entra ID domain starts with "m365x" to start a Patch My PC (PMPC) Cloud trial. Such customers no longer see the option to start PMPC Cloud Trial and will either need to enter a PMPC Cloud license key or activate their license using their on-premises Publisher license key.
See [Features by plan](https://patchmypc.com/request-quote#feature-comparison) for more information on our different subscription levels.
{% endhint %}
* A minimum of two users, who will be granted [**Access Management**](https://docs.patchmypc.com/patch-my-pc-cloud/administration/managing-users/modify-a-user#managing-access-management-privileges-for-a-user) privileges within PMPC Cloud.
# Onboard to Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To sign up for a free trial to PMPC Cloud:
1. Navigate to
2. Click **Sign Up**.
3. On the **Sign in** screen, enter the Entra ID you want to use to onboard to PMPC Cloud or click to select the relevant account from the list of already signed-in accounts. Then click **Next**.
4. Enter the password and click **Sign in**.
5. If the **Permission requested** screen is not displayed, go to Step 7.
6. Review the **Permission requested** screen, clicking **Accept** if you are happy to continue.
{% hint style="info" %}
**Note**
This dialog box is for the Enterprise Application Registration process. We require these permissions to authenticate you.
See [Permissions required for Patch My PC Cloud](/patch-my-pc-cloud/technical-references/cloud-permissions-reference/permissions-required-for-patch-my-pc-cloud) for more details.
You do not need to check the optional **Consent on behalf of your organization** checkbox, which is only visible to Global Administrators or a user with the Privileged Role Administrators role.
However, if you are assigned one of the above roles, and want to accept the request to read the profile for all users in your tenant and prevent this message from being displayed for them, you should check it.
Either way, checking or unchecking this checkbox does not affect PMPC Cloud functionality.
Once you accept the permissions, you will not see this dialog box again on subsequent sign-ins.
{% endhint %}
{% hint style="success" %}
**Tip**
You can click the down arrow beside each permission to get more information.
{% endhint %}
7. If do have previously created a Cloud Company and do not see the **Select the Company You Want to Sign-In To** screen, go to Step 9.
8. On the **Select the Company You Want to Sign-In To** screen, select the relevant option:
1. If you are setting up a new company, click **Create Company** and continue to Step 9.
2. If your email address has already been used to create a user in a PMPC Cloud company, you will see **Select** beside the relevant companies that you can sign in to.
3. If your email address is not associated with a user in a PMPC Cloud company, you can click **Request Access** beside the company you want to join.
\
The **Request Access to join *****\*** popup appears.
8. Enter an optional **Reason for Request** then click **Submit**.\
\
The **Request Access** text changes to **Renotify** and the **Success - Access request sent** notification is shown.
You now need to wait for a user with the **Full Admin with Access Management** role to review and approve your request.
{% hint style="success" %}
**Tip**
You can click the **Remember my Selection** checkbox to on the **Select the Company You Want to Sign-In To** screen to save your choice to save you having to chose the company you want to sign into each time.
{% endhint %}
{% hint style="info" %}
**Note**
Users will receive an email from the mailbox advising whether their request to join a company was accepted or rejected.
{% endhint %}
9. On the **Company Info** screen, click **Select** for the location where your company’s data will be stored.
10. In the **Company Name** field, type your company’s name.
{% hint style="danger" %}
**Important**
You cannot use the AT symbol (**@**), forward slash (**/**) or plus (**+**) symbols in your Company Name.
{% endhint %}
11. Select your company’s country from the **Country** dropdown.
12. Click **Continue**.
13. On the **User Info** screen, verify your **First Name** and **Last Name** are correct, amending as required.
14. Enter a valid email address in the **Contact Email** field.
15. Click the **Terms and Conditions** link to see these for using PMPC software and services.
The **Terms and Conditions** page is displayed. Once you’ve reviewed them, click the **X** in the top right-hand corner to close this window.
16. If you agree with our terms and conditions, check the **Accept all Terms and conditions** checkbox.
{% hint style="info" %}
**Note**
You cannot proceed with the onboarding without checking this checkbox.
{% endhint %}
17. Click **Continue**.
The PMPC Portal loads, showing the **App Catalog** page.
{% hint style="info" %}
**Note**
The first time you sign into a new PMPC Cloud Company, you will see the following message at the top of your screen:
**You currently have only one user with Access Management privileges. To prevent access issues in the future, please add a second user with Access Management privileges.**
This is warning you that you only have one user who can control access to this company and that we recommend you create at least another user in this company with the [Full Admin with Access Management user](/patch-my-pc-cloud/manage/settings/users/user-roles-reference) role. See [Add a Cloud User](/patch-my-pc-cloud/manage/settings/users/add-user) for more information.
{% endhint %}
## Next Steps
Now that you've finished onboarding to PMPC Cloud, you should consider:
* Connecting Publisher by following the [Add a Publisher Connection](/patch-my-pc-cloud/manage/settings/connections/add-connection#add-a-publisher-connection) process.
{% hint style="info" %}
**Note**
You only need to connect Publisher if you are using the Custom Apps or other features that require our On-Premises Publisher. If you are just using PMPC Cloud, you do not need to connect to Publisher.
{% endhint %}
* Connecting your Intune tenant by following the [Add an Intune Connection](/patch-my-pc-cloud/manage/settings/connections/add-connection#add-an-intune-connection) process.
* [Activate your license](/patch-my-pc-cloud/manage/settings/subscription/license/license-key#activate-a-new-license) if you have already purchased a PMPC Cloud license.
{% hint style="info" %}
**Note**
If you decide to activate a license without first connecting your PMPC Company to your Intune tenant, you will be unable to start a trial directly from the portal. If you are using an Enterprise Plus license, you will be able to [Sign up for an Enterprise Premium Trial from Enterprise Plus](/patch-my-pc-cloud/manage/settings/company-settings/sign-up-enterprise-premium-trial), once you have [connected your company to your Intune tenant](broken://pages/RoXhXa1jcXhIcPcKJk05#connecting-to-an-intune-tenant).
{% endhint %}
# About the Patch My PC Cloud Portal
*Applies to: Patch My PC Cloud*
All Patch My PC (PMPC) Cloud management-related tasks are performed through the *Cloud Portal*, which is browser-based and is what you see when you sign in at
The Cloud Portal is split into two key areas:
1. **Navigation pane -** Allows you to navigate through the different nodes
2. **Details pane -** Changes based on the selected node and available actions.
The Navigation pane consists of the following nodes:
## App Catalog
The *App Catalog* node (selected by default) contains links to the various catalogs of apps supported by PMPC Cloud.
From the **App Catalog** you can:
* Search for a specific app.
* Create a new [Custom App](/patch-my-pc-cloud/custom-apps/create-a-custom-app) by clicking **Add App**.
* Modify your view of the App Catalog and whether you see it as a grid view (the default view) or a list view.
* Sort the App Catalog by App Name (both forward and reverse sort) and the date apps were Last Updated (both forward and reverse sort).
* Apply Filters to help you refine the results you see.
* [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app).
{% hint style="info" %}
**Note**
See the [App Catalog](/patch-my-pc-cloud/app-catalog) section for more details.
{% endhint %}
## Deployments
Clicking the *Deployments* node lets you view all your current deployments and their status.
{% hint style="info" %}
**Note**
See [Deployments](/patch-my-pc-cloud/deployments/overview) for more information.
{% endhint %}
## Events
Clicking the *Events* node lets you view and manage all of the Cloud-related Events created by the various tasks performed from the Cloud Portal.
{% hint style="info" %}
**Note**
See [Events](/patch-my-pc-cloud/events/overview) for more information.
{% endhint %}
## Migration
Clicking the *Migration* node allows you to migrate items from a Microsoft Configuration Manager (ConfigMgr) hierarchy to your PMPC Cloud Company.
{% hint style="info" %}
**Note**
See [Migration](/patch-my-pc-cloud/migration/overview) for more information.
{% endhint %}
## Discovery
Clicking the *Discovery* node lets you see which apps in our App Catalog are installed in your environment, including any Binary Free Apps or Custom Apps you may have added.
{% hint style="info" %}
**Note**
See [Discovery](/patch-my-pc-cloud/discovery/overview) for more information.
{% endhint %}
## Advanced/Patch Insights
Clicking the *Advanced/Patch Insights* node lets you view a wealth of information about your organization to monitor, maintain, and enhance your environment.
{% hint style="info" %}
**Note**
See [Advanced/Patch Insights](/patch-my-pc-cloud/insights-intune/overview) for more information.
{% endhint %}
## Settings
Clicking the *Settings* node lets you perform various administrative tasks related to how your PMPC Cloud Company is set up and configured.
{% hint style="info" %}
**Note**
See [Administration](/patch-my-pc-cloud/manage) for more information.
{% endhint %}
# App Catalog in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
The **App Catalog** node of the Patch My PC (PMPC) Cloud Portal contains links to the various catalogs of apps supported by PMPC Cloud.
It is split into the following sections:
Catalog
Contains...
Patch My PC
The PMPC catalog of apps curated, vetted, and maintained by us.
Custom
Any Custom Apps you have created and added to your PMPC Cloud Company through the Cloud Portal.
External
Apps from other external resources such as WinGet (a community-driven package manager that allows users to install apps and download them from a public repository on GitHub that contains metadata about the installers).
{% hint style="danger" %}
**Important**
The **External** catalog is currently in private preview so it is not generally available.
{% endhint %}
{% hint style="info" %}
**Note**
See [WinGet](https://learn.microsoft.com/en-us/windows/package-manager/) for more information about WinGet and [Managing External Apps](/patch-my-pc-cloud/app-catalog/external-apps) for more details on managing external apps with PMPC Cloud
{% endhint %}
# Managing External Apps in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
This feature is currently only available through an invitation-only Private Preview, as both it and the documentation are under development, incomplete, and subject to change.
Please do not share links to these docs with others outside of the Private Preview.
Once this feature is released, it will be announced, and this banner will be removed.
{% endhint %}
The **External** child node of the **App Catalog** node in the Patch My PC (PMPC) Cloud Portal lets you create a catalog of external apps that can be managed and deployed using PMPC Cloud.
{% hint style="danger" %}
**Important**
Any apps managed by the External catalog are not curated, vetted, and maintained by PMPC. You are responsible for all due diligence of such apps and their ongoing support. We merely provide the mechanism to use them with PMPC Cloud.
{% endhint %}
## Current Limitations
In the current release, the **External** catalog has the following limitations:
* Only apps in the Public WinGet repository can be managed using the External catalog. Apps in private Winget repositories are unsupported.
* Other catalogs/repositories may be added in the future, based on customer demand.
* WinGet Apps available in the Patch My PC curated catalog cannot be added or deployed. In this scenario, you will be pointed to deploy the app from the Patch My PC Catalog.
* The following app types cannot be added:
* APPX
* MSIX
* Portable
* PWA
* This feature is not available in Managed Service Provider (MSP) App Sets.
* MSPs will have to add and deploy external apps for each individual company.
* The Migration feature of PMPC Cloud does not support migrating WinGet applications from Microsoft ConfigMgr applications to Intune.
* The Discovery feature of PMPC Cloud does not check WinGet apps. This may change in future iterations based on customer demand.
* All WinGet apps are created with the official Microsoft brown folder with a white arrow. It is possible to change this when deploying the app.
### Using the External Catalog
To be able to manage an app using the **External** catalog, you need to:
* [Enable the External Catalog](/patch-my-pc-cloud/app-catalog/external-apps/enable-external-catalog)
* [Add the External App](/patch-my-pc-cloud/app-catalog/external-apps/add-external-app)
* [Deploy the External App](/patch-my-pc-cloud/app-catalog/external-apps/deploy-external-app)
{% hint style="info" %}
**Note**
You can also [Delete an External App](/patch-my-pc-cloud/app-catalog/external-apps/delete-external-app).
{% endhint %}
# Enable the External Catalog in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
This feature is currently only available through an invitation-only Private Preview, as both it and the documentation are under development, incomplete, and subject to change.
Please do not share links to these docs with others outside of the Private Preview.
Once this feature is released, it will be announced, and this banner will be removed.
{% endhint %}
To enable the **External** catalog in Patch My PC (PMPC) Cloud:
1. From the PMPC Cloud Portal, navigate to **App Catalog | External**
\
The **External** catalog page is displayed.
2. On the **External** page, read the warning displayed about using apps from external sources. If you accept the risk, check the **I understand and accept the risks of using external catalogs** checkbox, followed by **Confirm**.
\
The **External** catalog page refreshes.
{% hint style="info" %}
**Note**
The permanently visible yellow warning triangle next to the catalog title displays a tooltip that reminds you of the risks of adding and deploying apps to the **External** catalog.
{% endhint %}
## Next Steps
Now that the **External** catalog has been enabled, you [add an app to it](/patch-my-pc-cloud/app-catalog/external-apps/add-external-app).
# Add an External App to Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
This feature is currently only available through an invitation-only Private Preview, as both it and the documentation are under development, incomplete, and subject to change.
Please do not share links to these docs with others outside of the Private Preview.
Once this feature is released, it will be announced, and this banner will be removed.
{% endhint %}
To add an app to the **External** catalog in Patch My PC (PMPC) Cloud:
1. From the PMPC Cloud Portal, navigate to **App Catalog | External**
2. On the External catalog page, click **Add App**
\
The list of apps in the public WinGet repository is displayed.
{% hint style="success" %}
**Tip**
Use the **Search** box and filters to help you more easily find the app you want to add.
{% endhint %}
{% hint style="info" %}
**Note**
If an app is already in the PMPC catalog, it will be shown with **PUBLIC APP** beside it, and you will be unable to re-add it. This is because it is better for you to use the curated version we maintain in the **Patch My PC** catalog Vs a non-curated version. Just hover over **PUBLIC APP** and click **Go to App** to open the app in our catalog.
Also, if an app is shown as **N/A**, it means this app is currently unsupported by the **External** catalog.
{% endhint %}
3. Click **Add** beside the required app.
**ADDED** appears next to the app, along with the **Success – External app added** notification.
4. Keep clicking **Add** beside any other apps you want to add.
5. Once you have finished adding all the required apps, click the **X** in the top-right corner.
The External catalog is redisplayed with the added app(s).
## Next Steps
Now you have added an app(s) to the **External** catalog, you can [deploy it](/patch-my-pc-cloud/app-catalog/external-apps/deploy-external-app).
# Deploy an External App to Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
This feature is currently only available through an invitation-only Private Preview, as both it and the documentation are under development, incomplete, and subject to change.
Please do not share links to these docs with others outside of the Private Preview.
Once this feature is released, it will be announced, and this banner will be removed.
{% endhint %}
Once an app has been added to the **External** catalog of Patch My PC (PMPC) Cloud, it can be deployed like any other app, but with some subtle differences.
To deploy an app from the **External** catalog:
1. From the PMPC Cloud Portal, navigate to **App Catalog | External**
2. On the **External** catalog page, locate the required app and click it to open its properties.
3. Click **Deploy** to start the Deployment Wizard.
4. On the **Risk of External App** dialog box, read the warning about deploying an external app, and if you accept the risks, click **Confirm**
5. Follow the [Deploy an App using Patch My PC Cloud](/patch-my-pc-cloud/deployments/deploy-app) process to complete the deployment.
{% hint style="info" %}
**Note**
The first time any customer deploys an external app that has not previously been deployed using PMPC Cloud, we download the installer to our storage. If this occurs, you will see the **Downloading Installer** dialog shown below, which will automatically close once the download has completed.
{% endhint %}
# Delete an External App from Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
This feature is currently only available through an invitation-only Private Preview, as both it and the documentation are under development, incomplete, and subject to change.
Please do not share links to these docs with others outside of the Private Preview.
Once this feature is released, it will be announced, and this banner will be removed.
{% endhint %}
To delete an app from the **External** catalog of Patch My PC (PMPC) Cloud:
1. From the PMPC Cloud Portal, navigate to **App Catalog | External**
2. On the **External** catalog page, click the app you want to delete to open it's properties.
3. On the app’s properties page, click **Delete**
4. On the **Are you sure you want to delete *****\*** dialog box, click **Yes**
The **External** catalog page is redisplayed, showing the app has been deleted along with the **Success – Application deleted** notification.
# End-Of-Life Apps in Patch My PC Cloud
*Applies to: Patch My PC (PMPC) Cloud*
There are times when we need to remove a product from the Patch My PC (PMPC) App Catalog, primarily because the product either:
* Goes End-Of-Life (EOL) and is no longer supported or maintained by the vendor.
* Other compatibility issues related to silent install or versioning.
{% hint style="info" %}
**Note**
See [How Products are Handled at End-Of-Life (EOL) or Become Incompatible](https://patchmypc.com/kb/how-products-are-handled-end/) for more information about how we handle EOL apps in general, other reasons for removing apps from our App Catalog, and a searchable [List of Products Removed due to End-of-Life or Compatibility Issues](https://patchmypc.com/kb/how-products-are-handled-end/#h-list-of-products-removed-due-to-end-of-life-or-compatability-issues).
{% endhint %}
In PMPC Cloud, when an app goes EOL:
* The app no longer appears in App Catalog.
* Any existing deployments of the app will be flagged with the **EOL** indicator in the **Deployments** node.
* If the app has been discovered by PMPC Cloud Discovery and is currently being managed, the app itself will be flagged with the **EOL** indicator on the **Managed** tab of the **Discovery** node.
If an app that is part of an MSP App Set is marked as EOL:
* Any existing deployments of the app will be flagged with the **EOL** indicator in the App Set.
{% hint style="danger" %}
**Important**
* If an app includes multiple variants and only certain variants are marked as EOL, the other non-EOL variants continue to function normally and are not marked as EOL.
* Any existing deployments of EOL apps can still be edited, recreated, etc., but you will be unable to create a new deployment of the EOL app. This also applies to EOL apps that are part of an existing App Set. EOL apps will not appear in the **Select Application** dropdown when creating a new App Set.
* If an existing App Set contains a deployment for an EOL app, new assignments can be added to the deployment for new Child Companies managed by the MSP Parent Company.
{% endhint %}
## Examples of EOL Apps
The following examples show how EOL will appear in the Cloud Portal:
* [Deployments](#deployments)
* [Discovery](#discovery)
* [App Set](#app-sets)
### Deployments
An existing deployment of an EOL app will be shown as follows.
### Discovery
A managed app in **Discovery** that is EOL will be shown as follows.
### App Set
An EOL app deployment that is part of an existing App Set will be shown as follows.
# Deployments in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Welcome to the Deployment section for Patch My PC (PMPC) Cloud.
{% hint style="danger" %}
**Important**
You need to [Onboard to Intune Apps](/patch-my-pc-cloud/intune-apps/onboard-to-intune-apps) before you can use the Deployments feature.
{% endhint %}
# Overview of Deployments in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Patch My PC (PMPC) Cloud supports the following methods for deploying apps:
* [Deploying an App we can auto-update from our App Catalog](#deploying-an-app-we-can-auto-update-from-our-app-catalog)
* [Deploying an App we cannot auto-update from our App Catalog](#deploying-an-app-we-cannot-auto-update-from-our-app-catalog)
* [Using Custom Apps to deploy a custom EXE or MSI](#using-custom-apps-to-deploy-a-custom-exe-or-msi)
## Deploying an App we can auto-update from our App Catalog
The PMPC App Catalog contains apps for which there is a publicly accessible download of the installer that we can deploy and update. In the majority of cases, you should use the [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app) process to deploy your apps.
## Deploying an App, we cannot auto-update from our App Catalog
Some apps do not publish a publicly accessible download. These are typically apps:
* You need to pay for.
* The installer is behind a paywall that requires an individual login and password.
* The vendor uses a compressed file for its installer.
We refer to such apps as *Binary-free apps* and you should follow the [Create a Binary Free App](/patch-my-pc-cloud/binary-free-apps/deploy-a-binary-free-app) process.
{% hint style="info" %}
**Note**
See our [Products that Require Manual Download to the Local Content Repository](https://patchmypc.com/local-content-repository-for-licensed-applications-that-require-manual-download) for a list of such apps that we’ve built and maintain.
{% endhint %}
## Using Custom Apps to deploy a custom EXE or MSI
If you have your own installer (EXE or MSI) that you want to deploy, then you should follow the [Create a Custom App](/patch-my-pc-cloud/custom-apps/create-a-custom-app) and [Publish a Custom App](/patch-my-pc-cloud/custom-apps/publish-a-custom-app) processes.
# Deploy an App using Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Patch My PC (PMPC) Cloud can be used to deploy apps using Microsoft Intune.
{% hint style="info" %}
**Note**
You can also:
* [Deploy the same App with multiple configurations](/patch-my-pc-cloud/deployments/technical-references/deploy-same-app)
* [Create a Deployment with No Assignments](/patch-my-pc-cloud/deployments/technical-references/deployment-without-assignments).
{% endhint %}
To deploy an app using PMPC Cloud:
1. Sign in to the portal at
2. Locate the required application on the **App Catalog** page.
{% hint style="success" %}
**Tip**
Use the **Search** field to help you locate the app.
{% endhint %}
{% hint style="info" %}
**Note**
If an app (for example, the Windows version of Slack) has multiple versions available for different variants/installer types, the App Catalog shows the total number of available versions. If you hover your mouse over this, you can see the list of variants grouped accordingly. Only that version will be displayed if a single version is available for all variants.
{% endhint %}
3. Click the app to open its properties.
4. Click **Deploy** to start the Deployment Wizard.
{% hint style="info" %}
**Note**
If the app you are deploying is also supported for macOS, you will see a separate **Deploy** option for **macOS** and you should follow the [Deploy a macOS app](/patch-my-pc-cloud/macos-support/deploy-macos-app) process.
Also, if the app you are deploying is already published by our on-premises Publisher, you will see the **This app is already deployed** warning dialog stating that deploying the same app through both Publisher and PMPC Cloud can cause potential issues if there are differences between the deployment configurations. We therefore strongly recommend you only deploy an app through either Publisher PMPC Cloud to avoid such issues.
{% endhint %}
The [General Information](/patch-my-pc-cloud/deployments/deploy-app/general-information-tab) tab is displayed, which needs to be completed.
{% hint style="info" %}
**Note**
Once the Deployment Wizard starts, the **Apply Template** button becomes available, which allows you to apply any [Deployment Templates](/patch-my-pc-cloud/deployments/use-template) you have created that contain preconfigured settings to your deployments.
{% endhint %}
# About the "General Information" tab of a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **General Information** tab of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure various general settings (explained below) for how you want the app to be deployed.
{% hint style="info" %}
**Note**
If an app has multiple variants with different version numbers, you will see a yellow triangle with an exclamation mark next to the **Version** number. This is a warning to you to double-check that you are deploying the correct version.
{% endhint %}
Once you have finished configuring the relevant options, go to [Next Steps](#next-steps).
## Apply Template
Allows you to apply a [Template](/patch-my-pc-cloud/deployments/use-template) of pre-configured settings to this deployment.
{% hint style="danger" %}
**Important**
If you apply a Template to a Deployment and a setting in the Template conflicts with a setting configured in App Catalog, you will see an error.
For example, you have configured a Requirement Rule in a Template and then applied the Template to a deployment. If the setting in App Catalog conflicts with that in the Template, you will see an error indicating the minimum acceptable value to which it should be configured. You will need to change the relevant setting to dismiss the error before you can continue.
{% endhint %}
## Connection
Shows the type of connection. Currently, we only support connections to Intune.
## Display Name
The unique name for this deployment. This is also the name of the app as it will appear on the target devices.
{% hint style="info" %}
**Note**
This **Display Name** has to be unique per operating system. For example, you can have two deployments for the same app if one is targeted to macOS and the other Windows. You cannot have two deployments with the same name if they are both targeted to either macOS or Windows.
{% endhint %}
## Language
Multiple language entries will be present if the vendor offers separate installers for that language. For example, an EXE installer for en-US, de-DE, etc. The majority of installers are multi-language (one installer, multiple languages), and the software can be configured in different languages by:
* Specifying additional installation parameters
* Configuring .config or .xml files
* Setting registry values.
In such cases, it is the vendor that determines the level of support and the behavior.
## Architecture
The architecture of the installer to be deployed:
* 64-bit installers can only be installed on 64-bit devices
* 32-bit installers can typically be installed on either 32-bit or 64-bit devices.
* Unspecified installers typically contain install logic for both architectures.
## Install Context
The context in which to install the application:
* **System –** Available to all users.
* **User –** Available only to the specific user.
## Installer Type
The available installer types you can choose from to install this app.
### **Windows Installer Types**
We currently support the following Windows installer types:
* .exe
* .msi
{% hint style="info" %}
**Note**
If the **.msi** option is greyed out, it's probably because this is a [Binary Free](/patch-my-pc-cloud/binary-free-apps/binary-free-apps-overview) app, i.e. you need to manually download the installer from the vendor and create it in PMPC Cloud as a [Binary Free App](/patch-my-pc-cloud/binary-free-apps/deploy-a-binary-free-app) (the "**Upload the required installer via 'Manage Files' to enable selection of this variant**" message indicates this).
{% endhint %}
* .msp
{% hint style="info" %}
**Note**
As per the tooltip, if you select the **msp** installer type, you will only be able to create a deployment with an **Update Only** assignment. If you want to create a deployment using the other assignment types, you will need to select the **exe** installer.
{% endhint %}
### **macOS Installer Types**
We currently support the following macOS installer types:
* .dmg
* .pkg
## Next Steps
Once you have finished configuring the relevant options, click **Next** to move to the [Configurations ](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab)tab.
# 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 grouped into sections known as *Tools.*
These tools allow you to configure various settings for the deployment.
These are two types of Tools:
* [Standard Tools](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools) included in every deployment as they contain the most common settings.
* [Additional Tools](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools) that can be optionally added to a deployment.
# Standard Tools in Patch My PC Cloud Deployments
*Applies to: Patch My PC Cloud*
Patch My PC (PMPC) Cloud deployments include the following standard tools :
* [Install Parameters](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/install-parameters)
* [Conflicting Processes](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/conflicting-process)
* [Return Codes](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/return-codes)
* [App Info](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/app-info)
* [Desktop Shortcut](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/desktop-shortcut)
* [Built-In Auto Updates](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/built-in-auto-updates)
* [Available Uninstall](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/available-uninstall)
* [Requirements](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/standard-tools/requirement-rules)
You can configure settings by either scrolling down the page until you find the relevant section or by clicking the relevant tool heading.
{% hint style="info" %}
**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.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Install Parameters in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **Install Parameters** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure various installation parameters and arguments.
| Option | Description |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 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).
|
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Conflicting Process in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
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** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to 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:
1. Click the **Conflicting Process** tool.
2. 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.
{% hint style="danger" %}
**Important**
This can result in data loss, so use it with care.
{% endhint %}
### 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)`
{% hint style="info" %}
**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](https://patchtuesday.com/blog/tech-blog/win32app-retry-interval/) for more information about the retry behavior of Win32 packages in Intune.
{% endhint %}
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](/patch-my-pc-cloud/manage/settings/branding).
{% hint style="info" %}
**Note**
If the user snoozes/defers the update, Intune reports the installation as a failure and retries 24 hours later.
{% endhint %}
{% hint style="success" %}
**Tip**\
See [Manage Conflicting Processes when Updating Third-Party Applications - Patch My PC](https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications#topic4) for a list of products we know will generally fail to update if they are in use.
{% endhint %}
## 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)
{% hint style="info" %}
**Note**
When selected, the notification closes after the timeout expires, and the deferral is automatically applied on the user's behalf. This counts toward either the configured deferral count or deferral time window. If a deferral limit is reached (such as 5 missed notifications when the deferral count is set to 5), the application will be closed, and the update will proceed automatically.
{% endhint %}
* Close the application and perform the update
{% hint style="info" %}
**Note**
When selected, the notification closes after the timeout expires and the installation begins immediately.
This setting is incompatible with **Modern (PSADT) branding**. When **Modern (PSADT) branding** is used, this option behaves the same as **Defer the installation on behalf of the user**. If the timeout expires and the user takes no action, the installation is deferred on the user's behalf. Once all allowed deferrals have been exhausted, the application is closed and the installation proceeds automatically.
{% endhint %}
#### Prevent the application from being opened while it is updating
Prevents the app from opening whilst it is being updated.
{% hint style="info" %}
**Note**
See the [Update in progress](https://patchmypc.com/kb/manage-conflicting-processes-when-updating/#h-update-in-progress) section of [Manage Conflicting Processes when Updating Third-Party Applications](https://patchmypc.com/kb/manage-conflicting-processes-when-updating/) for more information about this option.
{% endhint %}
### 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.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Return Codes in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **Return Codes** tool of the Patch My PC (PMPC) Cloud deployment wizard 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
{% hint style="info" %}
**Note**
See the [Configuration ](/patch-my-pc-cloud/custom-apps/create-a-custom-app/custom-apps-configuration-tab)section of [Create a Custom App](/patch-my-pc-cloud/custom-apps/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.
{% endhint %}
To manage Return Codes for a Deployment:
1. Click the **Return Codes** tool.
{% hint style="info" %}
**Note**
The number beside the **Return Codes** tool shows the number of return codes currently configured for the app being deployed.
{% endhint %}
The default Return Codes defined for the app are shown, plus any defined for the app if this is a Custom App.
{% hint style="info" %}
**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.
{% endhint %}
3. If you do not want to add a new Return Code, proceed to Step 5.
4. 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.
5. If you do not want to edit a Return Code, go to Step 9.
6. To edit a Return Code, click the pencil icon beside it.
7. Make any required changes.
8. Click the green tick to save your changes.
The **Code type** field is updated.
9. To delete a Return Code, click the red trash can beside the relevant code.
{% hint style="info" %}
**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.
{% endhint %}
{% hint style="danger" %}
**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.
{% endhint %}
The code is deleted from the list.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure App Info in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **App Info** tool of the Patch My PC (PMPC) Cloud deployment wizard allows 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
{% hint style="success" %}
**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.
{% endhint %}
To manage the App Info for a Deployment:
1. Click the **App Info** tool.
2. Configure the settings as required.
{% hint style="info" %}
**Note**
We pre-populate this screen with the information received from the vendor/added by us.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Desktop Shortcut in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **Desktop Shortcut** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to control whether a desktop shortcut of the app being deployed is created.
### Remove Desktop Shortcut
If checked, will remove the desktop shortcut created as part of the app installation.
To configure this setting:
1. Click the **Desktop Shortcut** tool.
2. Configure the settings as required.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Built-in Auto Updates in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
If an app supports built-in auto-updates, the **Built-in Auto Updates** tool will be available in the Patch My PC (PMPC) Cloud deployment wizard, but the **Disable Self-Update** checkbox will be selected by default, disabling any auto-updates.
{% hint style="info" %}
**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.
{% endhint %}
To manage the settings for the **Built-in Auto Updates** tool:
1. Click the **Built-in Auto Updates** tool.
2. Configure the required settings.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Available Uninstall in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **Available Uninstall** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to control whether Intune Apps can uninstall the app if the Company Portal installed it.
If checked, allows Intune Apps to uninstall the app if the Company Portal installed it.
To configure this setting:
1. Click the **Available Uninstall** tool.
2. Configure the settings as required.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Requirement Rules in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **Requirements** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure custom optional requirements (including requirement rules) that must be met for the app to be deployed to the target audience.
This includes:
* [Standard Requirements](#standard-requirements)
* [OS Architecture Requirements](#os-architecture-requirements)
* [Additional Requirements Rules](#additional-requirements-rules)
Configure these settings as required and detailed below.
{% hint style="danger" %}
**Important**
If you are deploying a Custom App created with Requirement Rules, some of the fields in this section will be prefilled. Although you can modify the fields as required, you will be unable to specify a value that is lower than that configured in the properties of the Custom App.
{% endhint %}
## Standard Requirements
### Minimum operating system
From the **Minimum operating system** dropdown, select the minimum operating system required by this app.
{% hint style="info" %}
**Note**
The default **Minimum operating system** value is set to match the first value in the dropdown, which corresponds to the oldest version of Windows still supported by Microsoft. As Microsoft deprecates a Windows version, this value and the values in the dropdown list will automatically update to the oldest version still supported by Microsoft.
{% endhint %}
{% hint style="success" %}
**Tip**
We recommend leaving the **Minimum operating system** dropdown at its default unless you need to configure a specific value. If an app/deployment is configured for a specific Windows version, when Microsoft retires that version, you will no longer be able to deploy the app unless you update this field to a supported Windows version.
{% endhint %}
### Min RAM memory (MB)
Configure the minimum amount of RAM required to run this app.
### Minimum CPU speed (MHz)
Configure the minimum CPU speed required to run this app.
### Minimum number of logical processors
Configure the minimum number of logical processors required to run this app.
## OS Architecture Requirements
The *OS Architecture Requirements* section lets you specify which operating system (OS) architectures the app can be deployed to.
By default, the relevant checkbox is checked based on the value configured in the **Architecture** field.
{% hint style="info" %}
**Note**
For example, if **Architecture** is configured:
* As **64-bit**, the **32-bit** checkbox under **OS Architecture Requirements** will be unchecked and cannot be checked.
* As **32-bit**, the **32-bit** checkbox under **OS Architecture Requirements** 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 in the **OS Architecture Requirements** section that corresponds to the selected **Architecture**.
The **ARM** checkbox in the **OS Architecture Requirements** section can always be checked/unchecked, regardless of the configured **Architecture**.
{% endhint %}
Configure the relevant settings as required.
## Additional Requirements Rules
Using the **Additional Requirements Rule** section, you can create up to 10 optional requirement rules based on the following:
* File
* Registry
* Script
To configure an Additional Requirement Rule:
1. Click **Add** in the **Additional Requirements Rules** section.
2. On the **Add Requirement Rule** screen, select the relevant type of rule from the **Rule Type** dropdown, then configure the required options as required.
{% hint style="info" %}
**Note**
To configure a script-based Requirement Rule requires the PowerShell script to already exist.
{% endhint %}
Rule Type
Available Options
File
Path – The path to the folder you are checking for.
File or Folder – The folder containing the file you are checking for.
Property – Various options, such as whether the item exists or does not, the date it was created, modified, etc.
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.
Registry key requirement – Various options, such as whether the key exists or does not, comparisons, etc.
Script
Script Name – The name of the script, which you can leave blank if you want to use the name of the script you are going to import.
Import Script – Allows you to browse to an existing PowerShell script to import.
NOTE If the script is unsigned, you will see the Script was detected as unsigned warning.
Script – Shows the script’s content.
NOTE You cannot modify the script in the Script window.
Select output data type - Various options, such as type, version, etc.
3. Configure the following additional options based on the type of rule you are creating.
Rule Type
Additional Options
File or Registry
Associated with a 32-bit app on 64-bit clients – If enabled, allows the rule to expand any path environment variables in the 32-bit context on 64-bit endpoints.
Script
Run script as 32-bit process on 64-bit clients – If enabled, allows the script to be run in a 32-bit process on 64-bit clients. If disabled, the script runs in a 64-bit process on 64-bit clients and in a 32-bit process on 32-bit clients.
Run this script using the logged on credentials - Run the script using the credentials signed in to the device.
Enforce signature check – If enabled, verifies that the script is signed by a trusted publisher, allowing the script to run without warnings or prompts. The script will run unblocked. If disabled, will require the end user to confirm they are happy for the script to run, but without signature verification.
NOTE If the script imported is unsigned, you will be unable to enable this option.
{% hint style="info" %}
**Note**
In terms of Scripts, in the current version:
* We only support PowerShell (.ps1) scripts
* You can only import a single script per Requirement Rule.
* 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.
{% endhint %}
4. Click **Add Rule** to add the requirement rule.
The rule is added to the list of requirement rules.
{% hint style="info" %}
**Note**
You will notice that a default **Script** Requirement Rule is added to the deployment, which cannot be edited or deleted. This is only actually used if you add an **Update Only** assignment to this deployment. Previously, we automatically added this script in the background in this scenario. We now highlight this so you can see the contents of this script.
Also, you can:
* Edit a Requirements Rule by clicking the pencil icon beside the relevant rule, making the required changes, then clicking **Save Rule** to save the changes.
* Delete a Requirements Rule by clicking the red trash can beside the relevant rule to remove it from the list of rules.
{% endhint %}
{% hint style="success" %}
**Tip**
You can click the eye icon beside the **Script** rule to open the **View Requirement Rule** screen, where you can see the content of the script.
{% endhint %}
5. Repeat the steps in this section to add any additional requirement rules.
{% hint style="info" %}
**Note**
[Editing a deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit) and changing any Requirement Rules will apply any changes in Intune immediately after the deployment is updated successfully in Intune.
{% endhint %}
{% hint style="danger" %}
**Important**
Using **Add Version** will not update the original deployment with any changes made to the Requirement Rules. If you edit the original deployment, you will see errors highlighting where settings with higher values for the new version have been configured compared to those in the original deployment.
If you configure Requirement Rules in both the Cloud Portal and Intune, the rules in the Portal will overwrite those in Intune. Likewise, if you have configured requirements in Intune and not in the Cloud Portal, we will not copy these to the Portal and will copy these requirements forward.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Additional Tools in Patch My PC Cloud Deployments
*Applies to: Patch My PC Cloud*
Patch My PC (PMPC) Cloud deployments include standard default settings. However, you can also add additional settings.
These optional settings are grouped into a series of related *Additional Tools*, which can be added (and, if needed, removed) to a deployment.
To add one or more optional Additional Tools to a deployment, click **Add** in the **Additional Tools** section, then select the relevant tool from the pop-up to add it to the list of **Additional Tools**.
{% hint style="success" %}
**Tip**
You can check the checkboxes beside multiple tools to add them to the list of **Additional Tools**. You can also click the **X** beside an additional tools you want to remove from the list.
{% endhint %}
Any settings you configure for a deployment will be used for the current deployment and automatically applied to any new versions of the deployment as it's updated.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Role Scope Tags in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **Role Scope Tags** tool is optional.
{% endhint %}
The **Role Scope Tags** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to leverage Intune Role Scope Tags (Scope Tags) in your deployments to help control which Intune admins can manage a specific deployment.
{% hint style="warning" %}
**Important**
Before you can use a Scope Tag in a PMPC Cloud deployment, it must have already been created in the Intune admin center. Follow the [To create a scope tag](https://learn.microsoft.com/en-us/mem/intune/fundamentals/scope-tags#to-create-a-scope-tag) process of [Use role-based access control (RBAC) and scope tags for distributed IT](https://learn.microsoft.com/en-us/mem/intune/fundamentals/scope-tags) for more details and information on Scope Tags.
If you manage Intune using PMPC Cloud, you should avoid performing any actions in the Intune admin center that can be performed in PMPC Cloud, as doing so will cause unwanted behavior.
{% endhint %}
To add Role Scope tags**:**
1. Add the [**Role Scope Tags** tool](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab#adding-additional-tools).
2. Click the **Role Scope Tags** tool.
3. In the **Profile Name** field, either:
1. Start typing the name of the relevant Scope Tag, then click the checkbox beside it to select it.
2. Click the dropdown to see a list of existing Scope Tags and click the relevant checkbox(es) to select it.
{% hint style="success" %}
**Tip**
You can click the **X** beside a Scope Tag in the **Profile Name** field to delete it.
{% endhint %}
{% hint style="info" %}
**Note**
See [Check Scope Tag Assignments](/patch-my-pc-cloud/technical-references/intune-reference/check-scope-tag-assignments-in-intune) for details on how to check within Intune that the Scope Tags defined in the deployment have been assigned correctly.
{% endhint %}
The number of profiles selected is shown beside the **Role Scope Tags** tool.
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **Scripts** tool is optional. However, if you deploy a Custom App where the **Installer Type** is set to **Installation Script**, the **Scripts** tool is automatically added to your deployment. See the [Deploying Scripted Custom Apps](#deploying-scripted-custom-apps) section in this article for more information.
{% endhint %}
The **Scripts** tool in the Patch My PC (PMPC) Cloud deployment wizard allows you to configure settings for install and uninstall scripts.
This includes regular PowerShell (.ps1) scripts as well as PSADT scripts, which can be specified directly in our Portal without having to upload the required PSADT module files separately.
{% hint style="info" %}
**Note**
Although we support both PSADT v3 and V4, we recommend using V4 whenever possible.
Also:
* Scripts will be run in the same context as the application.
* Each install script is limited to 1 MB per script, with a total size limit of 4 MB for all scripts.
* There is a limit of 50,000 characters per script.
We currently support the following script types:
* .BAT
* .CMD
* .PS1
* .VBS
{% endhint %}
{% hint style="danger" %}
**Important**
Currently, scripts containing `"${env:ProgramFiles(x86)}"` or `"${env:ProgramFiles}"` cannot be uploaded as Cloudflare is falsely identifying them as a false positive related to Log4j exploits. We are actively working with them to resolve this, but as this is outside our control, we cannot provide an estimated resolution time.
To work around this issue, see the [Resolution](/patch-my-pc-cloud/troubleshoot/deployments/typeerror-failed-to-fetch-error-when-trying-to-upload-a-pre-or-post-script-in-cloud#resolution) section of ["TypeError: Failed to fetch" error when trying to upload a Pre or Post Script](/patch-my-pc-cloud/troubleshoot/deployments/typeerror-failed-to-fetch-error-when-trying-to-upload-a-pre-or-post-script-in-cloud).
{% endhint %}
To add a script:
1. Add the [**Scripts** tool](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab#adding-additional-tools).
2. Click the **Scripts** tool.
{% hint style="info" %}
**Note**
If the app includes our recommended scripts, you will see the **Customer Scripts | PMPC Scripts** toggle shown above the **Install Scripts** section.
See [PMPC Scripts](/patch-my-pc-cloud/deployments/technical-references/use-pmpc-scripts) for more details on the options you have for managing these scripts.
{% endhint %}
3. Click **Add** beside the relevant script option to add a script, then configure the required settings as per the relevant articles:
* [Pre-Install Script](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts/pre-install-scripts) - a script that can be run before the installer runs.
* [Post-Install Script](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts/post-install-scripts) - a script that can be run after the installer runs.
* [Pre-Uninstall Script](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts/pre-uninstall-scripts) - a script that can be run before the uninstaller runs.
* [Post-Uninstall Script](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts/post-uninstall-scripts) - a script that can be run after the uninstaller runs.
{% hint style="info" %}
**Note**
If you upload [Extra Files](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/extra-files) as part of your Patch My PC (PMPC) Cloud Deployment, you can reference those files in any of the [Scripts](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts) in the same deployment by building a path relative to the script's current location. See [Referencing Extra Files in Scripts](/patch-my-pc-cloud/deployments/technical-references/reference-external-scripts) for more information.
Also, if any PSADT commands are detected in any of the scripts configured in the **Scripts** section, a warning is displayed about ensuring that any devices to which this deployment is assigned have at least .NET Framework 4.7.2 installed.
If this warning appears, check the **Enable PSADT Module** checkbox (available only if PSADT commands are detected), which will ensure the PSADT Toolkit is uploaded to Intune when this deployment is created.
If this warning is not displayed, you should not check the **Enable PSADT Module** checkbox.
{% endhint %}
{% hint style="danger" %}
**Important**
Checking the **Enable PSADT Module** checkbox causes the following behaviors:
* When [creating a deployment](/patch-my-pc-cloud/deployments/deploy-app):
* If a PSADT script is included and you have not manually interacted with the checkbox, it will be **automatically enabled**.
* If you manually change the checkbox state, your selection will be preserved.
* When [editing a deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit):
* The checkbox is treated as **manually configured**, and its state will not be automatically changed.
* If a PSADT script is added during edit, the checkbox will **not be auto-enabled** and must be adjusted manually if needed.
{% endhint %}
## Deploying Scripted Custom Apps
As previously mentioned, if you deploy a Custom App where the **Installer Type** is set to **Installation Script**, the **Scripts** tool is automatically added to your deployment.
The **Scripts** tool will also show the **Install File** and **Uninstall Command** fields. Clicking **View** next to these fields opens the Script Editor, which displays the associated script (this is read-only, so you cannot make any changes).
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Using Pre-Install Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
A *Pre-Install Script* is a script that can be run before the installer runs.
To add a Pre-Install script:
1. Click **Add** beside the **Pre-Install** option.
The **Add Pre-Install Script** page is shown, highlighting that the default **Script Format** is **.ps1**, with built-in support for PSADT functions.
2. To import an existing script, click **Import,** then browse to the location containing the script and select it.
The **Script Name** field is populated with the filename of the script selected, and the **Add Pre-Install Script** page is populated with the imported script.
3. To manually add a script, enter a unique name for the script in the **Script Name** field.
4. Select the type of script from the **Script Format** dropdown.
5. In the script editor, type your script.
{% hint style="info" %}
**Note**
We currently have a limit of 50,000 characters per script. Use the **Number of characters used** counter to keep track of the number of characters you’ve entered in the script editor.
If PSADT commands are detected in the Script Editor, the **Script Format** field is updated to show **.ps1 +** the PSADT logo.
{% endhint %}
{% hint style="success" %}
**Tip**
Under the script editor, we include example syntax to help you understand the required syntax for referencing any additional files you've uploaded, which updates depending on the **Script Format** selected.
{% endhint %}
6. In the **Arguments** field, enter any arguments you want to provide to the script.
{% hint style="success" %}
**Tip**
You can use variable names as arguments, provided they are enclosed by percentage signs (`%`). We provide common variables under this field, which you can add by clicking the plus (+) symbol or relevant variable name.
{% endhint %}
{% hint style="danger" %}
**Important**
Using script Arguments is currently unsupported when deploying an app to macOS.
Also, if you add any PSADT scripts to your deployments, you need to ensure .NET version 4.7.2 is installed on any devices to which this app will be deployed.
{% endhint %}
7. Check the **Don’t attempt software update if the pre-script returns an exit code other than 0 or 3010** checkbox if you don’t want the app to be installed if the pre-script returns an exit code other than **0** or **3010**.
If you do not check this checkbox, we will attempt to install the app regardless of the exit code returned by the pre-install script.
8. Check the **Run the pre-update script before performing any auto-close or skip process checks** checkbox if you want to run the pre-install script before the conflicting process notification is displayed (if relevant).\
\
If you do not check this checkbox, we will run the pre-install script after the conflicting process notification.
9. Click **Save** to save your script.
The **Configurations** tab is re-displayed with the name of the configured script beside it.
{% hint style="success" %}
**Tip**
You can click **Edit** to edit a script or its settings. You can also click the red “`x`” beside a script to delete it.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Using Post-Install Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
A *Post-Install Script* is a script that can be run after the installer runs.
To add a **Post-Install** script:
1. Click **Add** beside the **Post-Install** option.
The **Add Pre-Install Script** page is shown, highlighting that the default **Script Format** is **.ps1**, with built-in support for PSADT functions.
2. To import an existing script, click **Import**, browse to the location containing the script, and select it.
The **Script Name** field is populated with the filename of the script selected, and the **Add Post-Install Script** page is populated with the imported script.
3. To manually add a script, enter a unique name for the script in the **Script Name** field.
4. Select the type of script from the **Script Format** dropdown.
5. In the script editor, type your script.
{% hint style="info" %}
**Note**
We currently have a limit of 50,000 characters per script. Use the **Number of characters used** counter to keep track of the number of characters you’ve entered in the script editor.
If PSADT commands are detected in the Script Editor, the **Script Format** field is updated to show **.ps1 +** the PSADT logo.
{% endhint %}
{% hint style="success" %}
**Tip**
Under the script editor, we include example syntax to help you understand the required syntax for referencing any additional files you've uploaded, which updates depending on the **Script Format** selected.
{% endhint %}
6. In the **Arguments** field, enter any arguments you want to provide to the script.
{% hint style="success" %}
**Tip**
You can use variable names as arguments, provided they are enclosed by percentage signs (`%`). We provide common variables under this field, which you can add by clicking the plus (`+`) symbol or relevant variable name.
`%ReturnCode%` is currently only supported on post-scripts.
{% endhint %}
{% hint style="danger" %}
**Important**
Using script Arguments is currently unsupported when deploying an app to macOS.
Also, if you add any PSADT scripts to your deployments, you need to ensure .NET version 4.7.2 is installed on any devices to which this app will be deployed.
{% endhint %}
7. Click **Save** to save your script.
The **Configurations** tab is re-displayed with the name of the configured script beside it.
{% hint style="success" %}
**Tip**
You can click **Edit** to edit a script or its settings. You can also click the red “`x`” beside a script to delete it.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Using Pre-Uninstall Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
A *Pre-Uninstall Script* is a script that can be run before the uninstaller runs.
To add a Pre-Uninstall script:
1. Click **Add** beside the **Pre-Uninstall** option.
The **Add Pre-Install Script** page is shown, highlighting that the default **Script Format** is **.ps1**, with built-in support for PSADT functions.
2. To import an existing script, click **Import** then browse to the location containing the script and select it.
The **Script Name** field is populated with the filename of the script selected, and the **Add Pre-Uninstall Script** page is populated with the imported script.
3. To manually add a script, enter a unique name for the script in the **Script Name** field.
4. Select the type of script from the **Script Format** dropdown.
5. In the script editor, type your script.
{% hint style="info" %}
**Note**
We currently have a limit of 50,000 characters per script. Use the **Number of characters used** counter to keep track of the number of characters you’ve entered in the script editor.
If PSADT commands are detected in the Script Editor, the **Script Format** field is updated to show **.ps1 +** the PSADT logo.
{% endhint %}
{% hint style="success" %}
**Tip**
Under the script editor, we include example syntax to help you understand the required syntax for referencing any additional files you've uploaded, which updates depending on the **Script Format** selected.
{% endhint %}
6. In the **Arguments** field, enter any arguments you want to provide to the script.
{% hint style="success" %}
**Tip**
You can use variable names as arguments, provided they are enclosed by percentage signs (`%`). We provide common variables under this field, which you can add by clicking the plus (`+`) symbol or relevant variable name.
{% endhint %}
{% hint style="danger" %}
**Important**
Using script Arguments is currently unsupported when deploying an app to macOS.
Also, if you add any PSADT scripts to your deployments, you need to ensure .NET version 4.7.2 is installed on any devices to which this app will be deployed.
{% endhint %}
7. Check the **Don’t attempt software uninstall if the pre script returns an exit code other than 0 or 3010** checkbox if you don’t want the app to be uninstalled if the pre-script returns an exit code other than **0** or **3010**.\
\
If you do not check this checkbox, we will attempt to uninstall the app regardless of the exit code returned by the pre-install script.
8. Check the **Run the pre-uninstall script before performing any auto-close or skip process checks** checkbox if you want to run the pre-uninstall script before the conflicting process notification is displayed (if relevant).\
\
If you do not check this checkbox, we will run the pre-uninstall script after the conflicting process notification.
9. Click **Save** to save your script.
The **Configurations** tab is re-displayed with the name of the configured script beside it.
{% hint style="success" %}
**Tip**
You can click **Edit** to edit a script or its settings. You can also click the red “`x`” beside a script to delete it.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Using Post-Uninstall Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
A *Post-Uninstall Script* is a script that can be run after the uninstaller runs.
To add a Post-Uninstall script:
1. Click **Add** beside the **Post-Uninstall** option.
The **Add Pre-Install Script** page is shown, highlighting that the default **Script Format** is **.ps1**, with built-in support for PSADT functions.
2. To import an existing script, click **Import,** then browse to the location containing the script and select it.
The **Script Name** field is populated with the filename of the script selected, and the **Add Post-Uninstall Scripts** page is populated with the imported script.
3. To manually add a script, enter a unique name for the script in the **Script Name** field.
4. Select the type of script from the **Script Format** dropdown.
5. In the script editor, type your script.
{% hint style="info" %}
**Note**
We currently have a limit of 50,000 characters per script. Use the **Number of characters used** counter to keep track of the number of characters you’ve entered in the script editor.
If PSADT commands are detected in the Script Editor, the **Script Format** field is updated to show **.ps1 +** the PSADT logo.
{% endhint %}
{% hint style="success" %}
**Tip**
Under the script editor, we include example syntax to help you understand the required syntax for referencing any additional files you've uploaded, which updates depending on the **Script Format** selected.
{% endhint %}
6. In the **Arguments** field, enter any arguments you want to provide to the script.
{% hint style="success" %}
**Tip**
You can use variable names as arguments, provided they are enclosed by percentage signs (`%`). We provide common variables under this field, which you can add by clicking the plus (`+`) symbol or relevant variable name.
`%ReturnCode%` is currently only supported on post-scripts.
{% endhint %}
{% hint style="danger" %}
**Important**
Using script Arguments is currently unsupported when deploying an app to macOS.
Also, if you add any PSADT scripts to your deployments, you need to ensure .NET version 4.7.2 is installed on any devices to which this app will be deployed.
{% endhint %}
7. Click **Save** to save your script.
The **Configurations** tab is re-displayed with the name of the configured script beside it.
{% hint style="success" %}
**Tip**
You can click **Edit** to edit a script or its settings. You can also click the red “`x`” beside a script to delete it.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Extra Files in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **Extra Files** tool is optional.
{% endhint %}
The **Extra Files** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to upload additional configuration files for a deployment.
To add extra folders and/or files:
1. Add the [**Extra Files** tool](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab#adding-additional-tools).
2. Click the **Extra Files** tool.
3. Either:
1. Drag and drop the relevant folders or files to the relevant area.
2. Click the relevant button to browse to and select the relevant folders or files.
{% hint style="info" %}
**Note**
See [Unsupported File Names and Extensions for Extra Files](/patch-my-pc-cloud/technical-references/unsupported-file-names-and-extensions-in-cloud) for a list of filenames and extensions we do not support for upload.
Also, adding a folder will add any files and folders (including their files) within the selected folder.
We support uploading files with the same name, provided they are in different folders. We also support uploading folders with the same name, provided the selected paths are unique.
{% endhint %}
4. Click **Upload** when your browser prompts you to upload the content.\
\
The hash will be calculated for any folders/files you upload, which will appear at the bottom of the **Extra Files** section.
{% hint style="info" %}
**Note**
The total number of extra folders/files is not limited, but their total size must not exceed the storage limits for your license type. See [Product Limitations](/patch-my-pc-cloud/product-limits) for more details.
Also, if the **Installer Type** on the **General Information** page is set to **`.msi`**, the **MST File** section will be shown, allowing you to upload a single MST file. This file must have the **`.mst`** extension.
\*\*
Uploading a **`.mst`** file automatically adds the following to the **Additional Argument** field of the **Install Parameters** section:
**`TRANSFORMS=[<`*****`mstfile>`*****`].mst`**
where **`<`*****`mstfile>`*** is the name of the uploaded MST file.
{% endhint %}
5. Repeat the above steps to add any additional folders/files as required.
{% hint style="info" %}
**Note**
Once a deployment has been successfully created, you can add or remove any additional folders or files as required.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
{% hint style="info" %}
**Note**
If you upload [Extra Files](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/extra-files) as part of your Patch My PC (PMPC) Cloud Deployment, you can reference those files in any of the [Scripts](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts) in the same deployment by building a path relative to the script's current location. See [Referencing Extra Files in Scripts](/patch-my-pc-cloud/deployments/technical-references/reference-external-scripts) for more information.
{% endhint %}
# Configure Dependencies in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **Dependencies** tool is optional.
{% endhint %}
The **Dependencies** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to create dependencies within a deployment, whereby the app being deployed requires one or more other apps to have already been installed on the targeted resource before it can be deployed.
If the required app(s) (known as the *parent*) have not already been installed on the device, they will automatically be installed before the app that is being deployed (known as the *child app*) is installed.
{% hint style="danger" %}
**Important**
Before you can create an App Dependency in a PMPC Cloud deployment, the deployment for the parent app(s) must:
* exist already
* have been deployed successfully
The parent app can be packaged without assignments and used in a Dependency chain rule, provided the parent app is deployed first.
Also, apps that have not been successfully deployed (such as those with a status of **Failed**, **Retrying**, **Processing**, etc.) cannot be used to create an app dependency, nor can apps with **Uninstall** or **Update Only** assignments.
{% endhint %}
{% hint style="info" %}
**Note**
Like Intune, we do not support circular dependencies (i.e. App A has a dependency on App B, and App B has a dependency on App A).
As per Intune, you can create a maximum of 100 dependencies, which includes the dependencies of any included dependencies, as well as the app itself. See [Step 5: Dependencies](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-5-dependencies) of [Add, assign, and monitor a Win32 app in Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add) for more information.
Also, the parent app must have been deployed successfully before you can create a dependency between apps.
{% endhint %}
To add a dependency:
1. Add the [**Dependencies** tool](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab#adding-additional-tools).
{% hint style="info" %}
**Note**
If we are aware that an app requires a dependency, we automatically add the **Dependencies** tool with a yellow dot after the tool name. If you click the **Dependencies** tool, we show you the name of the app we recommend you add as a dependency for this deployment.
{% endhint %}
2. Click the **Dependencies** tool.
3. From the **Add Dependencies** field, either:
1. Start typing the name of the relevant app that this app depends on already being successfully installed on the target device.
2. Click the dropdown and select the relevant app that this app depends on already being successfully installed on the target device.
The selected app appears under the **Parent Deployment** section.
{% hint style="info" %}
**Note**
Click the trashcan beside the relevant app under the **Parent Deployment** section to delete a dependency.
{% endhint %}
4. Repeat Step 3. to add any additional dependencies.
{% hint style="success" %}
**Tip**
Once a dependency has been configured, you can view it as part of the app’s properties in the Microsoft Intune admin center.
For more information, see [Step 5: Dependencies](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-5-dependencies) of [Add, assign, and monitor a Win32 app in Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/apps/apps-win32-add).
{% endhint %}
{% hint style="info" %}
**Note**
If a dependency is set up in the Intune admin center between an app managed by PMPC Cloud and an app managed directly in Intune, we will always copy-forward any dependencies from the PMPC Cloud app whenever we update the PMPC Cloud app.
{% endhint %}
{% hint style="danger" %}
**Warnings**
If we encounter any problems with app dependencies, we display a yellow exclamation mark (“**!**”) warning. Hovering over this will display more information.
We typically generate warnings in the following scenarios:
* If a dependency fails to be created. In this case, a warning is shown on the impacted child app(s) at the deployment level.
* If a dependency fails to be carried forward. In this case, a warning is shown on the impacted child app(s) at the deployment level.
* When multiple parent dependencies exist, any warnings will specify which particular dependency failed to be created to help you troubleshoot the issue.
If an entire deployment fails before the dependencies stage is reached, no warnings are shown, as we only show warnings for successful deployments.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Categories in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **Categories** tool is optional.
{% endhint %}
The **Categories** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to leverage Intune App Categories (Categories) in your deployments to help users find apps in the Company Portal.
{% hint style="info" %}
**Note**
See the [Create and edit categories for apps](https://learn.microsoft.com/en-us/mem/intune/apps/apps-add#create-and-edit-categories-for-apps) section of [Add apps to Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/apps/apps-add) for more information on App Categories.
{% endhint %}
To add a Category to a deployment:
1. Add the [**Categories** tool](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab#adding-additional-tools).
2. Click the **Categories** tool.
3. Go to Step 6. to add a new category or in the **Add Category** field, either:
1. Start typing the name of the relevant Category, then click the checkbox beside it to select it.
2. Click the dropdown to see a list of existing Categories and click the relevant checkbox(es) to select it.
{% hint style="success" %}
**Tip**
You can click the **X** beside a Category in the **Add Category** field to delete it from the list.
{% endhint %}
4. Repeat this process to add any additional categories.
5. Go to to step 8. if you do not want to add a new Category.
6. To add a new Category, type its name in the **Add Category** field.
{% hint style="info" %}
**Note**
You can create up to 200 categories per Intune tenant. Each category name must:
* Be unique
* Be less than 255 characters
* Not contain the backslash (**\\**) or quote (**"**) characters
* Not be the name of a script.
{% endhint %}
7. Press `ENTER` and the **Success – The category “<*****category\_name>*****” has been created** notification is shown, confirming the new category has been added to both Intune and this deployment.
The number of categories selected is shown beside the **Categories** tool.
{% hint style="info" %}
**Note**
See [Check App Categories](/patch-my-pc-cloud/technical-references/intune-reference/check-app-categories-in-intune) for details on how to check within Intune that the Categories defined in the deployment have been assigned correctly.
Also:
* If different Categories are configured in the portal and Intune admin center they are combined to be the same.
* If a Category is created in the portal and then removed from the Intune admin center, it will be re-added by the portal.
* Categories are also copied forward to a new version of an app.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure ESP Profiles in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **ESP Profiles** tool is optional.
{% endhint %}
The **ESP Profiles** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure your deployments created in our portal to be part of one or more profiles configured on the Enrollment Status Page (ESP) of the Microsoft Intune admin center.
{% hint style="info" %}
**Note**
See [Set up the Enrollment Status Page](https://learn.microsoft.com/en-us/mem/intune/enrollment/windows-enrollment-status) for more details about the ESP and working with ESP profiles.
{% endhint %}
To configure a PMPC Cloud deployment to use an ESP Profile:
1. Add the [**ESP Profiles** tool](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab#adding-additional-tools).
2. Ensure the ESP Profile(s) you want this deployment to belong to have already been created in Intune.
{% hint style="info" %}
**Note**
At the time of writing, Intune supports a maximum of 51 profiles plus the default profile (so 52 in total) per tenant.
{% endhint %}
3. Click the **ESP Profiles** tool.
4. In the **Add Profile** field, either:
1. Start typing the name of the relevant ESP Profile, then click the checkbox beside it to select it.
2. Click the dropdown to see a list of existing ESP Profiles and click the checkboxes beside the relevant profiles to select them.
{% hint style="info" %}
**Note**
If an ESP Profile already contains the maximum of 100 apps, you will be unable to select it from the dropdown. If you hover over it, you'll see the **Total limit reached** tooltip.
{% endhint %}
The selected ESP Profile(s) are added to the **Add Profile** field.
{% hint style="success" %}
**Tip**
You can click the **X** beside an ESP Profile in the **Add Profile** field to delete it from the list.
Also, the number in brackets shows the number of apps currently added to an ESP Profile, with 100 being the maximum.
{% endhint %}
{% hint style="info" %}
**Note**
See [Check ESP Profiles](/patch-my-pc-cloud/technical-references/intune-reference/check-esp-profiles-in-intune) for details on how to check within Intune that a PMPC Cloud deployment has been successfully added to an ESP Profile.
{% endhint %}
5. Repeat this process to add any additional ESP Profiles.
The number of ESP Profiles selected is shown beside the **ESP Profiles** tool.
{% hint style="info" %}
**Note**
To avoid potential conflicts, we highly recommend creating all deployments within the PMPC Cloud portal and using the ESP Profiles feature to control which apps belong to which ESP profiles. You should only use the **Enrollment Status Page** in the Intune admin center to create an ESP Profile.
Other important points about ESP Profiles:
* They are currently unavailable on macOS.
* Different ESP Profiles can be used in different Update Rings if required.
* If you edit an ESP Profile that is used in a deployment that uses Update Rings, the changes will only be applied to the version of the deployment that is applied to the ring with the lowest delay.
* If during a Sync Schedule the number of apps within an ESP Profile exceeds 100, we do not fail the deployment. The deployment will be completed with any new versions being assigned. However, we will display a warning indicator in the portal and the message\
\
“**Failed to add application with version “<*****version\_number*****>” to “<*****esp\_profile\_name*****>**”.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
# Configure Retention Policy in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Using the **Retention Policy** tool is optional and is not supported by the MSP App Sets feature.
{% endhint %}
The **Retention Policy** tool of the Patch My PC (PMPC) Cloud deployment wizard allows you to determine how many versions of an app (both Windows and macOS) you want to keep. If deploying a later version of an app causes issues, you can redeploy an older version.
By default, PMPC only retains the latest version of an app in your environment. Configuring a Retention Policy allows you to keep the current version, plus the number of configured versions as set by the Retention Policy.
For example, setting a Retention Policy of 1 for Google Chrome would mean you always have *n-1* versions of Chrome, the latest and the previous version, until a newer version is deployed.
{% hint style="danger" %}
**Important**
The previous version (n-1) of an app may temporarily remain visible in Intune even when a Retention Policy is **not** configured.
The portal only deletes the previous version during the **next** [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule), not in the same sync that creates the new version.
This behavior is intentional as it prevents situations where if the new version (n) fails to package, no version of the app remains available.
If Update Rings are configured, the previous version may remain for more than one sync, and will only be deleted after the next [Sync Schedule and all Update Rings ](/patch-my-pc-cloud/deployments/update-rings/sync-schedule)steps are completed.
{% endhint %}
To configure a PMPC Cloud deployment to use a Retention Policy:
1. Add the [**Retention Policy** tool](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab#adding-additional-tools).
2. Click the **Retention Policy** tool.
3. In the **Versions to Retain** box, either type the required number or use the controls to configure the number of versions of this app you wish to retain in your environment.
{% hint style="info" %}
**Note**
The default value of **0** means only the most recent version of the app is retained. You can retain up to ten versions of an app.
{% endhint %}
{% hint style="success" %}
**Tip**
See [Check App Version Retention](/patch-my-pc-cloud/technical-references/intune-reference/check-app-version-retention-in-intune) for details on how to check within Intune that the correct number of versions of an app are being retained as defined in your Retention Policy.
{% endhint %}
## Next Steps
If you do not want to configure any additional settings, click **Next** to move to the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab.
Otherwise, navigate to the relevant tool to configure the required settings, which are explained in the relevant section.
{% hint style="info" %}
**Note**
Other important points about App Version Retention:
* Modifying the **Versions to Retain** setting is supported. The next time the [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) runs (or you manually [update an app](/patch-my-pc-cloud/deployments/manage-deployments/updates)), the changes will be applied to the deployment.
* Deleting a deployment or disconnecting [Intune ](broken://pages/RoXhXa1jcXhIcPcKJk05#deleting-an-intune-tenant-connection)will delete the latest and all old unassigned versions of all of your deployments.
* Modifying an existing deployment with a Retention Policy configured will only affect the current version, not all previous versions. For example, if you edit a deployment and add an extra file, the file is only added to the latest version, not all previous versions.
* You should avoid deleting versions of apps manually using the Intune admin center. Inadvertently deleting a previous version from Intune will not break the Retention Policy for the deployment. When a newer version is deployed, we will delete the relevant previous version(s) accordingly to keep everything in sync.
{% endhint %}
# About the "Assignments" tab of a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The **Assignments** tab of the Patch My PC (PMPC) Cloud deployment wizard allows you to configure various assignments (explained below) for how you want the app to be deployed.
{% hint style="info" %}
**Note**
See [Understand Patch My PC Cloud Assignments](/patch-my-pc-cloud/deployments/technical-references/understand-assignments) for more details about assignments and how they work in PMPC Cloud.
You can deploy an app without assignments as detailed in [Create a Deployment Without Assignments](/patch-my-pc-cloud/deployments/technical-references/deployment-without-assignments).
{% endhint %}
From the **Assignments** page you can also:
* Apply a [Template](/patch-my-pc-cloud/deployments/use-template) of pre-configured settings to this deployment.
* [Enable Update Rings](/patch-my-pc-cloud/deployments/update-rings/create) for this deployment.
To add an Assignment to a deployment:
1. Click **Add Assignment** and then choose the assignment type you want to add for this deployment:
1. **Add Required –** A mandatory application that will be installed automatically for all users or devices it is assigned to.
2. **Add Available –** An optional application that will be available to install via the Company Portal for the primary user of the device.
3. **Add Update Only –** Creates a separate Win32 package in Intune that exclusively updates existing installations. It will not install the software on devices where it isn't already present, and only applies if the installed variant matches the one configured in the deployment.
{% hint style="info" %}
**Note**
Assignments configured in the portal are the *source of truth* for deployments with assignments. If you manually add any assignments outside the portal, these will not be retained when a new version is created. To ensure your assignments persist, configure them directly in the portal.
Also:
* If your deployment uses a [Retention Policy](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/retention-policy), using the **Update Only** assignment type will also retain the relevant number of versions of the app in addition to the regular deployment types in Intune.
* Intune does not support using the **Update Only** assignment type with a deployment that is also configured to use [ESP Profiles](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/esp-profiles). If you try to use this configuration, the **Deploy** button will be greyed out and the **Configurations** tab will show a red "**X**".\
\
In this scenario, you either need to:
* Remove the **Update Only** assignment type
* Or remove all ESP Profiles.
{% endhint %}
d. **Add Uninstall –** A mandatory uninstall that will remove the application from any users or devices it is assigned to, using the apps uninstaller.
{% hint style="info" %}
**Note**
We do not support the **Uninstall** assignment type for pkg installers.
See [Uninstall a Custom App](/patch-my-pc-cloud/custom-apps/uninstall-a-custom-app) for more details on how the Custom Apps uninstall feature works and its limitations.
{% endhint %}
e. **Install App -** Allows the Intune admin to add **Required**, **Available**, or **Uninstall** assignments from within the Intune admin center.
f. **Update Only App -** Allows the Intune admin to add an **Update Only** assignment from within the Intune admin center.
{% hint style="info" %}
**Note**
See [Create a Deployment Without Assignments](/patch-my-pc-cloud/deployments/technical-references/deployment-without-assignments) for more details on deploying apps without assignments.
Also, if the **Installed Apps Name** field on the **Configuration** tab of a Custom App is not completed, then the **Add Update Only** and **Update Only App** assignment types are unavailable, as per the tooltip you will see if you hover your mouse over either of these assignment types.
{% endhint %}
{% hint style="info" %}
**Note**
Adding an **Available** assignment allows you to add an **Update Only** application. This ensures that any applications assigned as **Available** are updated automatically when installed via Microsoft’s Company Portal.
{% endhint %}
2. On the **Add <*****assignment\_type*****> Assignment** screen, choose the relevant Entra ID security groups to target for this assignment, then click **Save**.
| Option | Description |
| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Include | If checked, all of the items in this group will receive the assigned app. |
| Exclude |
If checked, all of the items in this group will not receive the assigned app.
Can be used in conjunction with Include to exclude a subset of devices when you have an Include of a superset of devices.
For example, you want to target all of your computers except for your test devices. To achieve this, you'd configure your Entra ID groups as follows:
o Check Include for your All Company Devices Entra ID group. o Check Exclude for your Test Devices Entra ID group.
|
{% hint style="info" %}
**Note**
You will be unable to select any options under the **Add update only app for** section for an Available Assignment until you select at least option.
Also, as our portal uses application permissions to read Entra ID groups, all groups will be visible whenever you manage assignments.
{% endhint %}
The **Assignments** page updates to show the newly added assignments, including their configuration.
3. Make any of the following optional modifications to the assignment(s).
| Option | Description |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Add Filter |
The ability to add Assignment Filters you have already created in Intune to target specific managed devices for the deployment.
TIP: You can click the red X beside a filter to remove it.
|
| Notifications | When to display notifications related to this deployment. |
| Content Download |
How to download the content for the deployment:
o Foreground - The default for initial installs. o Background - The default for updates.
|
{% hint style="info" %}
**Note**
We automatically configure these settings based on our experience and best practices, but you can modify certain settings if necessary.
{% endhint %}
{% hint style="success" %}
**Tip**
You can click **Deploy** on this page if you don’t want to add additional assignments or see the **Summary** page, which allows you to double-check the settings you’ve configured for this deployment.
{% endhint %}
4. Add any additional assignments for this deployment by clicking **Add Assignment** and repeating the steps in this section.
5. If you are happy you have entered all of the details for the deployment correctly, click **Deploy** to deploy the app. However, we recommend you click **Next** to move to the [**Summary** ](/patch-my-pc-cloud/deployments/deploy-app/summary-tab)tab, where you can verify the settings for this deployment before you deploy this app.
# About the "Summary" tab of a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Reviewing the **Summary** tab is optional, but recommended.
{% endhint %}
The **Summary** tab of the Patch My PC (PMPC) Cloud deployment wizard provides a summary of the deployment so you can confirm that it is configured correctly before you create it.
Review the summary of the deployment shown on the **Summary** page.\
\
If you are happy click **Deploy**.\
\
If you need to change something, click **< Prev** to backtrack through the Deployment Wizard to the relevant setting. Make the change, then step back through the wizard to this page. If everything is now correct, click **Deploy**.
{% hint style="info" %}
Note
If you have configured this deployment to use [Update Rings](/patch-my-pc-cloud/deployments/update-rings), you will see the **Deployment Summary** screen, containing details on how you have configured the rings.
See [Update Rings](/patch-my-pc-cloud/deployments/update-rings) for more information.
{% endhint %}
The App Catalog is redisplayed along with the **Success - Created *****\*** notification.
{% hint style="warning" %}
**Important**
When a new version of software is released, it is automatically deployed using the settings of the existing deployment. The old version will be removed from the target user/device and replaced with the newer version.
{% endhint %}
{% hint style="info" %}
**Note**
By default, the installation logs for an app will be created in the following folder regardless of the installer file type:
`%ProgramData%\PatchMyPCInstallLogs`
The only exception is for EXE files, where the specified value for the **loggingSwitch** variable will be used if it is not null or empty.
{% endhint %}
# Use a Template in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
Once the *Deployment Templates* ([Templates](/patch-my-pc-cloud/manage/settings/deployment-templates)) feature of Patch My PC (PMPC) Cloud has been enabled for your PMPC Cloud company and you have created at least one template, you can start using templates for your new deployments.
{% hint style="info" %}
**Note**
Templates are currently unsupported for use in existing deployments. To configure an existing deployment to use a template, you need to delete it and recreate a new one. When creating the new deployment, you can choose which template to use.
Also, if a template contains an option that is not supported by a deployment, that option will not be shown in the portal.
If a template contains an option that is supported by a deployment, that option will be shown in the portal with its configuration set as per the template. However, you can modify the configuration of that option if required.
{% endhint %}
To configure a new deployment to use a template:
1. Follow the relevant deployment scenario.
2. Once the Deployment Wizard has started, click **Apply Template**
{% hint style="info" %}
**Note**
You can click **Apply Template** at any time, regardless of the tab you are working on.
{% endhint %}
3. On the **Apply Template** screen, select the radio button beside the template you want to apply, then click **Apply**.
{% hint style="info" %}
**Note**
Only the templates created for the Operating System (OS) platform you are deploying to are shown.
{% endhint %}
The Deployment Wizard is redisplayed along with the **Success - Template ‘<*****template\_name*****>’ applied** notification.
{% hint style="info" %}
**Note**
You can click **Apply Template** again to select and re-apply a template (which overwrites any existing settings) at any time before you click **Deploy** to ensure the template settings are applied to this deployment.
{% endhint %}
# Update Rings in Patch My PC Cloud
Applies to *: Patch My PC Cloud*
Welcome to the Update Rings section for Patch My PC (PMPC) Cloud.
This section contains articles covering the various Update Ring-related tasks for PMPC Cloud.
# Overview of Update Rings in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
The *Update Rings* feature of Patch My PC (PMPC) Cloud allows you to deploy apps and updates in a phased manner across your Intune estate.
For example, you may want to deploy software to a pilot group of users/devices to ensure it functions as expected. Then, after a set period of time, you want to deploy the update to a wider group of users/devices and pause a set amount of time to check for issues. Then finally, if there are no issues, deploy the update to the remaining users/devices in scope for the deployment.
Although this approach increases the amount of time it takes to deploy software, it can reduce the impact of deploying software with unforeseen issues that impacts your business in undesirable ways.
{% hint style="info" %}
**Notes**
* Update Rings do not use Intune's built-in capability to create delayed assignments using Availability and Deadlines.
* The use of Update Rings is optional and is controlled at the individual deployment level.
* See our [Update Ring Forecaster](https://www.youtube.com/watch?v=RelJPqWIGno) YouTube video for an explanation of Update Rings, plus how to use our free [Get-UpdateRingForecast](https://github.com/PatchMyPCTeam/Community-Scripts/blob/main/Other/Reports/Get-UpdateRingForecast.ps1) script on GitHub which creates an interactive HTML visualization of app update deployment rings for staged rollouts. It calculates and displays a schedule based on specified parameters and helps you understand your version rollout cadence across different environments.
{% endhint %}
{% hint style="success" icon="user-check" %}
**Learning Hub**
See the [How Update Rings Work in Patch My PC Cloud](https://patchmypc.com/learning-hub/how-update-rings-work-in-patch-my-pc-cloud/) video on our Learning Hub for a practical walkthrough of how Update Rings work, including how to enable them and how overlapping updates are handled.
{% endhint %}
# Update Ring Types in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
In Patch My PC (PMPC) Cloud, there are two different types of *Update Rings,* both of which depend on the start time of the relevant deployment and how you have your Sync Schedule configured:
* [Delayed Update Rings](#delayed-update-rings)
* [Immediate Update Rings](#immediate-update-rings)
{% hint style="info" %}
**Note**
Only once the configured start time has passed will the assignments under an Update Ring be created in Intune for the corresponding Win32 app.
{% endhint %}
## Delayed Update Rings
The *Delayed* option works as follows:
1. The first Update Ring is created immediately, and the software is deployed to the assigned test users/devices (usually known as a *pilot group).*
2. After waiting the configured number of days from when the deployment was created (to allow testing to be performed), the next Update Ring is created, and the software is deployed to the assigned users/devices (usually a bigger group/all assigned users/devices).
3. Step 2 is repeated until all Update Rings have been created and the software has been deployed to all users/devices requiring it.
### Advantages
The advantage of the delayed option is:
* As the next ring (and therefore the next set of assignments) has not been created, if the software causes an issue that is detected in the first ring, the issue cannot propagate to other rings as they haven’t been created.
* Your full Update Ring workflow is followed, starting with the current version.
* Useful when you want every version to follow the same controlled rollout.
### Disadvantages
The disadvantages of the delayed option are:
* The deployment will be in a scheduled state until at least one version has passed through all rings.
* Your Sync Schedule configuration can impact both when the initial rings are created and when the Sync Schedule runs, which will update your rings and their assignments, including promoting a new version to your relevant rings.
* You cannot edit a deployment that uses delayed Update Rings until all of the rings have been created. If you try, you will see the [Error - Editing is not allowed until all rings are created after the configured delay.](/patch-my-pc-cloud/troubleshoot/update-rings/error-editing-is-not-allowed-until-all-rings-are-created-after-the-configured-delay-cloud-error)
* If you need to change anything, you must delete and recreate the deployment.
## Immediate Update Rings
The *Immediate* options works as follows:
1. All Update Rings are created immediately with their relevant delays and assignments.
2. Assignments from all of the Update Rings will be applied to the version of the app you created the deployment with.
3. Update Rings will not begin to work until the next version (current plus one or n+1) of the software is released. At this point, the assignments from the previous version are moved to the latest version and Update Rings start to function as configured.
### Advantages
The advantages of the immediate option are:
* All rings are created and configured once.
* The deployment can be edited and adjusted as required.
* You can make configuration changes at any time.
* Helpful for first-time deployments where version *n* needs to reach all devices right away, while future updates follow the phased rollout.
### Disadvantages
The disadvantages of the immediate option are:
* If the software in one ring causes an issue, if the admin forgets to pause the deployment or remove any additional rings, the issue could be spread to the next ring, even if a delay between rings is configured.
* All assignments from all Update Rings are applied to the same version of the application that the deployment was created with. However, this is only true for the initial creation of the Update Rings. All other functionality of Update Rings will continue to work as normal in any new app versions.
{% hint style="danger" %}
**Important**
You need to consider the following when working with Update Rings:
* You cannot mix standard deployments (that don’t use Update Rings) and Update Rings in a single deployment.
* [How the Sync Schedule Affects Update Rings](/patch-my-pc-cloud/deployments/update-rings/sync-schedule) for more information on how your configuration of the Sync Schedule will affect how Update Rings behave.
* [How Update Rings Handle New Versions](/patch-my-pc-cloud/deployments/update-rings/new-versions) for more information about how update rings handle new versions, including worked examples.
{% endhint %}
# Update Ring Progression in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
If your Patch My PC (PMPC) Update Rings are configured with longer delays, a new version of a product may be released while an older version is still moving through the rings.
This is not a problem, as when a newer version becomes available, PMPC Cloud does not restart or override the Update Ring process already in progress.
Each version of the software must complete the full Update Ring lifecycle independently. In other words, version *n* will finish all rings exactly as configured, and version *n+1* will follow the same path when its turn begins.
The diagram below illustrates how each version progresses through the rings independently.
{% hint style="info" %}
**Note**
See the [Patch My PC Update Rings: Mastering Phased Rollouts in Intune | Tips for a Better User Experience](https://www.youtube.com/watch?v=jgfErZIzNhQ) on our YouTube channel for more details.
{% endhint %}
## Update Rings forecast
To help you predict how your Update Rings will progress, we provide a [PowerShell script](https://github.com/PatchMyPCTeam/Community-Scripts/blob/main/Other/Reports/Get-UpdateRingForecast.ps1) that generates an HTML report. This report gives you a clear visual overview of your current Update Rings configuration and how each ring is expected to advance.
{% hint style="info" %}
**Note**
See the [Update Ring Forecaster](https://www.youtube.com/watch?v=RelJPqWIGno) on our YouTube channel for a detailed walkthrough of the script and the report.
{% endhint %}
# How the Sync Schedule in Patch My PC Cloud affects Update Rings
*Applies to: Patch My PC Cloud*
As the [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) affects when your Portal checks for updates to your Patch My PC (PMPC) Cloud deployments, how often it runs can also affect how your Update Rings behave.
For example, if you have deployed an app that updates more frequently than your configured Sync Schedule, the ring with the lowest delay (for example, Ring 1) will have the latest suitable version applied.
Depending on how often you run your Sync Schedule and the delay between your rings, the scenario could arise where we have to skip versions to keep everything configured as per your ring strategy.
If this arises, we will not deploy a version of an app to any rings that has not been deployed to at least Ring 1. This ensures we only deploy apps to later rings that have been tested on at least one ring.
## Other Factors
Also:
* The Sync Schedule evaluates your Update Rings. When a ring’s configured Days Delay has been reached, the assignments for that ring are created.
* As Update Rings are evaluated only during the Sync Schedule, the frequency of your sync sets the minimum pace at which the rings can progress. For example, if your Sync Schedule runs weekly, the Update Rings cannot move faster than a weekly cadence.
{% hint style="info" %}
**Note**
If you want Update Rings to be evaluated more frequently, but prefer a slower schedule for packaging new versions, you can support this request by upvoting [Update rings independent of sync schedule](https://ideas.patchmypc.com/ideas/PATCHMYPC-I-5986) on our UserVoice page.
{% endhint %}
* If you create your Update Rings with an **Immediate** start time, the Sync Schedule configuration only impacts the daily update of the rings and their assignments (promotion to the new version).
* If you create your Update Rings with the **Delayed** start time, the Sync Schedule configuration impacts both the initial creation of the rings and the daily update of their assignments (promotion to the new version). For example, you create a deployment with two Update Rings with the default two-day delay between them. The first ring will be created when you deploy the software. The second ring won’t be created until two days have passed since the time the deployment was created and the next Sync Schedule run.
The following table summarizes how your [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) configuration determines how you can configure the delay between Update Rings.
Sync Schedule Configured For
Delay between Rings
Daily
Delays between rings can be configured as required.
Weekly
Ring 2 has to have a minimum delay of 7 days
Ring x has to be configured with a delay of at least 7 days apart from any other ring.
Monthly
Ring 2 cannot have a delay of less than 31 days
Ring x has to be configured with a delay of at least 31 days apart from any other ring.
These limitations ensure that the update delays align with your chosen sync frequency and is why we advise configuring your [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) to run on a daily basis when using Update Rings.
# How Patch My PC Cloud Update Rings Handle New Versions
*Applies to: Patch My PC Cloud*
Let’s assume you want to deploy an app in a controlled manner using Patch My PC (PMPC) Cloud.
First, you want to deploy the software to a pilot group containing a few users who want to test the software.
Then, a couple of days later, once you are happy the app functions correctly, you want to deploy it to a different group containing more users.
You could:
1. Create a single deployment targeted to the pilot users group.
2. Two days later, either:
1. Modify the deployment targeted to the pilot users group to add the other group containing more users.
2. Create a new deployment targeted to the other group containing more users.
This approach is admin intensive and relies on the admin remembering to create the deployment two days later to ensure the other group containing more users gets the app.
Alternatively, you can create a single deployment and enable Update Rings with:
* One ring assigned to the pilot users group.
* A separate ring assigned to the other group containing more users, but with a two-day delay to allow the pilot users to perform testing.
How Update Rings behave depends on which Update ring Start Time you chose at the time of creating the rings:
* [Delayed](#how-delayed-update-rings-handle-new-versions)
* [Immediate](#how-immediate-update-rings-handle-new-versions)
## How Delayed Update Rings Handle New Versions
For this example, we will assume you want to deploy version 2019.1 of dBase:
* Initially to the **dBase Pilot Users** group.
* Two days later, you want to deploy the software to the **dBase All Users** group.
This is how you would configure this deployment in the PMPC Cloud portal to use **Delayed** update Rings.
In this scenario, when you deploy the app the **Deployments** node is displayed along with the **Success – Created <*****app\_name*****>** notification.
Once the deployment has been completed successfully, if you look in the Microsoft Intune admin center under **All apps** and search for the app, you will see that version **2019.1** has been successfully deployed.
If you click the app and navigate to **Manage | Properties**, then scroll down to the **Assignments** section, as you are using delayed update rings you will only see the assignments for the first Update Ring has been created and applied to this version.
If you click on the deployment in the portal, then click **More Info**, then click **Ring 2**, you will see that this ring is scheduled to be created two days after the deployment was created.
Two days after the deployment was created and after the next Sync Schedule runs, the second update ring will be created and the assignment added for the **dBase All Users** group to install the software to all of the members of this group.
You can now edit the deployment if required, as all of the rings have been created.
If you also look at the deployment's properties, you will see that the second ring has been created successfully and assigned to the **dBase All Users** group.
As the following table shows, the software is installed immediately for any users in the **dBase Pilot Users** group.
Any users in the **dBase All Users** group will not have the software installed until two days later.
Day
Group
Software installed?
0
dBase Pilot Users dBase All Users
Yes No
1
dBase Pilot Users dBase All Users
Yes No
2
dBase Pilot Users dBase All Users
Yes Yes
### New Version Released
Now, let’s assume a new version (2019.2) gets released.
In this scenario, you can:
* Wait until the overnight sync runs to pick up the new version.
* Run the [Sync Now](/patch-my-pc-cloud/deployments/manage-deployments/updates/sync-now) process to update just this deployment immediately.
{% hint style="info" %}
**Note**
This is one of the many reasons why we recommend configuring your [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) to **Daily** if you are using Update Rings.
We also use the release date of the new version to validate if it is the right time to update the assignments to upgrade rings to later versions.
{% endhint %}
Once the deployment has been updated, you can now edit it as all of the rings have now been created. If you look at the deployment’s properties, you will see that for the **Ring 1**, version **2019.2** has now been assigned to the **dBase Pilot Users** group.
But if you click on **Ring 2**, you will see that version **2019.1** is still assigned to the **dBase All Users** group.
If you check in the Intune admin center, you will now see both the existing app (version 2019.1) and the new version we have just deployed (version 2019.2).
If you check the assignments for the original deployment (version 2019.1), you will see it is now only assigned to the **dBase All Users** group.
Whereas, if you check the assignments for the new deployment (version 2019.2), you will see it is only assigned for now to the **dBase Pilot Users** group.
Two days after the new version of the app is released and after the next Sync Schedule runs, the assignment for the **dBase All Users** group will be automatically moved from the version 2019.1 deployment to the 2019.2 deployment, automatically upgrading the members of the **dBase All Users** group to version 2019.2.
The old version of the app (2019.1), will remain, but will no longer show as **Yes** under the **Assigned** column in the Intune admin center. At the next sync, the old version of the app will be deleted.
This update process is summarized in the following table:
Day*
Group
Current version
Upgraded?
Installed version
0
dBase Pilot Users dBase All Users
2019.1 2019.1
Yes No
2019.2 2019.1
1
dBase Pilot Users dBase All Users
2019.2 2019.1
No** No
2019.2 2019.1
2
dBase Pilot Users dBase All Users
2019.2 2019.1
No** Yes
2019.2 2019.1
\* Number of days after the new version of the app is released
\*\* Any new users/devices added to the group will receive the version applicable to the group.
## How Immediate Update Rings Handle New Versions
For this example, we will assume you want to deploy version 2024.1 of PaintShop Pro:
* Initially to the **Corel Pilot Users** group.
* Two days later, you want to deploy the software to the **Corel All Users** group.
This is how you would configure this deployment in the PMPC Cloud portal to use **Immediate** Update Rings.
When you deploy the software, you see the **Deployment Summary** of how the deployment will be handled.
Once the deployment has completed successfully, if you look in the Microsoft Intune admin center under **All apps** and search for the app, you will see that version **2024.1** has been successfully deployed.
If you then click the app and navigate to **Manage | Properties**, then scroll down to the **Assignments** section, you will see all of the assignments for each of the Update Rings have been created and applied to this version.
As the following table shows, when using Immediate Rings, the software is installed immediately for any users in any of the groups assigned to any of the update rings.
| Day | Group | Software installed? |
| --- | ------------------------------------------- | ------------------- |
| 0 |
Corel Pilot Users Corel All Users
|
Yes Yes
|
| 1 |
Corel Pilot Users Corel All Users
|
Yes Yes
|
| 2 |
Corel Pilot Users Corel All Users
|
Yes Yes
|
It is only when a [new version](#new-version-released-1) of the targeted software gets released (current plus one or n+1), do the assignments from the previous version get moved to the latest version and Update Rings start to function as configured.
### New Version Released
Now, let’s assume a new version (2024.2) gets released.
In this scenario, you can:
* Wait until the overnight sync runs to pick up the new version.
* Run the [Sync Now](/patch-my-pc-cloud/deployments/manage-deployments/updates/sync-now) process to update just this deployment immediately.
{% hint style="info" %}
**Note**
This is one of the many reasons why we recommend configuring your [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) to **Daily** if you are using Update Rings.
We also use the release date of the new version to validate if it is the right time to update the assignments to upgrade rings to later versions.
{% endhint %}
Once the deployment has been updated, if you look at its properties, you will see that for the **Ring 1**, version **2024.2** has now been assigned to the **Corel Pilot Users** group.
But if you click on **Ring 2**, you will see that version **2024.1** is still assigned to the **Corel All Users** group.
If you check in the Intune admin center, you will now see both the existing app (version 2024.1) and the new version we have just deployed (version 2024.2).
If you check the assignments for the original deployment (version 2024.1), you will see it is now only assigned to the **Corel All Users** group.
Whereas, if you check the assignments for the new deployment (version 2024.2), you will see it is only assigned for now to the **Corel Pilot Users** group.
Two days after the new version of the app is released, the assignment for the **Corel All Users** group will be automatically moved from the version 2024.1 deployment to the 2024.2 deployment, automatically upgrading the members of the **Corel All Users** group to version 2024.2.
The old version of the app (2024.1), will remain, but will no longer show as **Yes** under the **Assigned** column in the Intune admin center. At the next sync, the old version of the app will be deleted.
This update process is summarized in the following table:
Day*
Group
Current version
Upgraded?
Installed version
0
Corel Pilot Users Corel All Users
2024.1 2024.1
Yes No
2024.2 2024.1
1
Corel Pilot Users Corel All Users
2024.2 2024.1
No** No
2024.2 2024.1
2
Corel Pilot Users Corel All Users
2024.2 2024.1
No** Yes
2024.2 2024.2
\* Number of days after the new version of the app is released
\*\* Any new users/devices added to the group will receive the version applicable to the group.
# How Patch My PC Cloud Update Rings Affect Dependencies
*Applies to: Patch My PC Cloud*
If your deployments are using [App Dependencies](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/dependencies) and both the deployments for the child and parent apps have Update Rings enabled, the following behavior occurs:
* Each version of an app for the child deployment with update rings enabled must depend on the parent app with the version related to the last ring of the parent deployment.
* When the last ring of the parent app is updated to a new version, we also move over the dependencies associated with the last ring.
* If Update Rings are disabled for the parent app, we rebuild the dependency with the app that used to be Ring 1, with the lowest delay/the latest version.
* If the delay for the ring with the oldest version is decreased and this ring becomes the ring with the newest version, we will delete the previous dependency and build the dependency with the app that, after editing, has the oldest version.
# Create Update Rings in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To create Update Rings for a new Deployment in Patch My PC (PMPC) Cloud:
1. If you are unfamiliar with creating a deployment, follow the [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app) process until Step 7.
2. On the **Assignments** page, click **Enable Update Rings**.
3. From the **Update ring start time** dropdown, choose how you want your Update Rings to handle the start times for their assignments:\
• [Delayed](/patch-my-pc-cloud/deployments/update-rings/update-ring-types#delayed)\
• [Immediate](/patch-my-pc-cloud/deployments/update-rings/update-ring-types#immediate)
By default, two Update Rings are created with a two-day delay between them.
4. If you do not want to add additional Update Rings, go to step 7.\
\
To add an additional Update Ring, click **Add Update Ring**.
5. On the **Add Update Ring** dialog box, enter the name for the new ring in the **Name** field and click **Save**.
A new ring is added.
{% hint style="danger" %}
**Important**
Whenever you add a new Update Ring, it is created with a default delay of **0** days, i.e. the deployment will be installed immediately on any targeted users/devices.
If you already have another ring with a default delay of 0 days, you will see the **Two rings cannot have the same delay value** message besides the second ring with the duplicate delay.
You should adjust the delays on your Update Rings to avoid duplicates.
Also, if your [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) is configured for anything other than **Daily**, this will affect the delay you can configure between rings. For example, assuming you have your Sync Schedule configured for **Monthly**, when you add a new ring you will not be able to configure a delay between rings of less than 30 days as shown below.
{% endhint %}
6. Repeat step 4 to add any additional Update Rings.
{% hint style="info" %}
**Note**
You can add up to a maximum of 10 Update Rings per deployment.
{% endhint %}
7. If you do not want to change the names of any of the rings, go to Step 10.\
\
If you want to change the name of any of the rings, click the pencil icon () beside the relevant ring.
8. Enter the ring's name in the **Name** field of the **Edit Update Ring** dialog box, then click **Save**.
The updated name appears.
9. Change the name of any other rings.
10. If you do not want to change the delay for any of the rings, go to Step 11.\
\
If you want to change the delay for a ring, click the plus (**+**) or minus (**-**) sign beside the relevant rings.
11. Click **Add Assignment** and add the relevant assignments for each ring, configuring the settings for each assignment as required.
{% hint style="info" %}
**Note**
See the [Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) section of the [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app) process for more information.
{% endhint %}
{% hint style="success" %}
**Tip**
You can drag assignments between Update Rings by clicking the double ellipsis () beside the relevant assignment and dragging and dropping it to the relevant Update Ring.
{% endhint %}
12. Click **Deploy**.
The **“<*****deployment\_name*****>” Deployment Summary** dialog box appears, summarizing what you are deploying, to which groups, and when.
{% hint style="info" %}
**Note**
If your [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) is set to anything other than **Daily**, the UI will warn you that some rings may not be evaluated as expected.
This is why we recommend you set your [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) to **Daily** if you plan to use Update Rings.
{% endhint %}
13. Either click :\
\
a. **Cancel** to return to the **Assignments** tab to make any changes (after which you need to click **Deploy**).\
\
b. Click **Confirm** to continue.
When you click **Confirm**, the **Deployments** node appears showing the deployment as **In Progress** and the **Success – Created <*****deployment\_name*****>** notification.
# Edit Update Rings in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
If a Patch My PC (PMPC) Cloud deployment is created with [Delayed Update Rings](/patch-my-pc-cloud/deployments/update-rings/update-ring-types#delayed-update-rings), you cannot edit it until all of the rings have been created. If you attempt to edit a deployment with incomplete Update Rings you will see the [Error - Editing is not allowed until all rings are created after the configured delay](/patch-my-pc-cloud/troubleshoot/update-rings/error-editing-is-not-allowed-until-all-rings-are-created-after-the-configured-delay-cloud-error) message.
Also, if you make any changes to Return Codes for a deployment where Update Rings are enabled, these changes are only applied to the latest ring (newest version).
{% endhint %}
To edit the Update Rings configuration for a deployment:
1. Navigate to the **Deployments** node.
2. Click the relevant deployment whose Update Ring configuration you want to edit.
{% hint style="success" %}
**Tip**
Click the filter button () and select the **Enabled** option under the **Update Rings** section, followed by **Apply Filters** to see just those deployments that have update Rings configured.
{% endhint %}
3. Click **Edit**.
4. Click the **Assignments** tab.
5. Make any required changes, for example:
1. Move Assignments between rings using drag and drop
2. Rename rings by clicking the pencil icon beside the relevant ring
3. Modify the delay for a ring by clicking the minus (**-**) or plus (**+**)
4. Add a ring by clicking **Add Update Rings**
5. Delete a ring by clicking the red x after the delay.
6. Click **Save** to save your changes.
\
If you make any changes that affect how the Update Rings will work, you will see the **“<*****app\_name*****>” Deployment Summary** asking you to either confirm or cancel your changes.\
\
For example, reducing the delay for **Corel All Users** ring from **3** days to **2** results in the following.
7. Either click **Cancel** to return to the **Assignments** tab and make any required changes or click **Confirm** to save your changes.\
\
The **Deployments** node is redisplayed along with the **Success – Edited <*****deployment\_name*****>** notification.
# View Update Rings in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To view the Update Rings configured for a Patch My PC (PMPC) Cloud deployment:
1. Follow the [Edit a Deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit) process to open the properties of the relevant deployment whose Update Rings you want to view.
2. Click **More Info**.
\
Any configured Update Rings are shown as tabs, which you can switch between to review your settings.
{% hint style="info" %}
**Note**
If any rings have a status of **Scheduled**, it means that specific ring has yet to be created. See [Check if an Update Ring has been created](/patch-my-pc-cloud/deployments/update-rings/check) for more information.
{% endhint %}
3. Click the red **X** in the top right-hand corner to close the **More Info** page and return to the **Deployments** node.
# Check an Update Rings has been created in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
In Patch My PC (PMPC) Cloud, the [Delayed](/patch-my-pc-cloud/deployments/update-rings/update-ring-types#delayed-update-rings) option for Update Rings doesn’t create an Update Ring until any configured delay has passed.
As a result, you cannot edit a deployment that uses Delayed Update Rings until all rings have been created.
{% hint style="info" %}
**Note**
If you try editing a deployment that uses Delayed Update Rings and not all of the rings have been completed, you will see the following error:
[Error - Editing is not allowed until all rings are created after the configured delay.](/patch-my-pc-cloud/troubleshoot/update-rings/error-editing-is-not-allowed-until-all-rings-are-created-after-the-configured-delay-cloud-error)
{% endhint %}
To determine if a specific Update Ring has been created:
1. Use the [Edit a deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit) process to navigate to the properties page of the deployment.
2. Each Update Ring is represented by a separate tab and the status of the ring shows you whether it has been created or not:\
\
• **Success –** The ring has been created.\
• **Scheduled –** The ring has not been created.\
\
In the following example, **Ring 1** has been created as it has a status of **Success**.
\
However, as **Ring 2** has a status of **Scheduled**, it has yet to be created as the configured delay has not passed.
{% hint style="success" %}
**Tip**
If you look in the top right-hand corner of the deployment, the timestamp shows when the deployment was created. From this and looking at the number of days delay configured for a ring, you can work out when a specific ring will be created.
{% endhint %}
# Update a Patch My PC Cloud Update Ring
*Applies to: Patch My PC Cloud*
If you are using the Update Rings feature of Patch My PC (PMPC) Cloud, you may find that a version of an app deployed to a ring works fine and you now want to deploy this version to the next update ring without waiting for either the configured delay to be reached for that ring or the [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) to be run.
To update an individual Update Ring to a later version:
1. Navigate to the **Deployments** node.
2. Click the relevant deployment to open its properties then click **More Info**.
3. If you can update a ring to a newer version the **Update Now** button is available.
{% hint style="danger" %}
**Important**
Some important points to note:
* The **Update Now** option is only available if the deployment has been deployed successfully. It will not be shown if the deployment is in any other state or if **Pause Updates** has been enabled for this deployment.
* An individual update ring can only be updated to a later version than the one it is currently running.
* An individual update ring can only be updated to a later version that has already been applied to the ring with the lowest delay.
* You are only updating a specific ring to a later version, not the whole deployment or any other rings.
{% endhint %}
4. Click **Update Now** and select the relevant version you want to upgrade this ring to.
5. On the **Update “<*****deployment\_name*****>” ring to version <*****version\_number*****>** dialog box, click **Confirm**.
\
The portal refreshes showing that the deployment is **In Progress** and the **Success – Ring <*****ring\_name*****>** updated notification is shown.
\
Once the deployment has completed successfully, if you navigate back to the ring, you will see the version number has changed and the **Update Now** button is unavailable.
# Convert an existing Patch My PC Cloud Deployment to use Update Rings
*Applies to: Patch My PC Cloud*
If you have already successfully deployed an app using Patch My PC (PMPC) Cloud, you can convert that deployment to use Update Rings.
To convert an existing deployment to use Update Rings:
1. [Edit the deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit) and navigate to the **Assignments** tab.
Any existing assignments for the deployment are shown.
2. Click **Enable Update Rings**.
3. On the **Move Assignments or Delete** dialog box, click **Move** to create the Update Rings and move any existing assignments to the first Update Ring.
{% hint style="info" %}
**Note**
Clicking **Delete** will delete any existing assignments, not the deployment itself. It will also create the default two Update Rings with default settings.
{% endhint %}
Any existing assignments are moved into the first Update Ring.
4. Continue from Step 3 of the [Create Update Rings](/patch-my-pc-cloud/deployments/update-rings/create) process to configure your Update Rings. For example, adding additional assignments, moving assignments between rings, etc.
5. Once you have completed reconfiguring the deployment, click **Save**.
{% hint style="danger" %}
**Warning**
When you convert an existing deployment to use Update Rings, the rings will be created with the **Immediate** option, i.e. immediately. As this is the expected behavior, it cannot be changed.
{% endhint %}
# Delete an Update Ring in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
For a Patch My PC (PMPC) Cloud deployment with Update Rings enabled, you can either:
* [Delete all Update Rings](#delete-all-update-rings)
* [Delete a Single Update Ring](#delete-a-single-update-ring)
{% hint style="info" %}
**Note**
All deletion tasks for Update Rings are performed from the **Assignments** tab of the respective deployment.
{% endhint %}
## Delete all Update Rings
To delete all Update Rings for a deployment:
1. [Edit](/patch-my-pc-cloud/deployments/manage-deployments/edit) the relevant deployment and navigate to the **Assignments** tab.
2. If you want to delete a single Update Ring, use the [Delete a Single Update Ring](#delete-a-single-update-ring) process.\
\
To delete all Update Rings for this deployment, click **Remove all Rings**.
3. On the **Move Assignments or Delete** dialog box, click **Move** to remove the Update Rings but keep all the existing assignments.\
{% hint style="info" %}
**Note**
Clicking **Delete** will delete any existing assignments but not the deployment itself.
{% endhint %}
The Update Rings are removed and any existing assignments are kept.
4. Click **Save** to save your changes.\
{% hint style="danger" %}
**Important**
As removing all Update Rings disables Update Ring functionality for this deployment (which could result in unintended results), the **"*****\*****" Deployment Summary** is shown detailing the impact of your proposed change.\
\
For example, this version of the app will be deployed immediately to all of the following assignments without any of the delays enforced by using Update Rings.
{% endhint %}
{% hint style="info" %}
**Note**
If the existing deployment had different versions applied to different assignments, we use the version that was applied to the lowest delay ring before the deployment was edited.
{% endhint %}
5. Click **Cancel** to return to the **Assignments** tab to make any required changes, or click **Confirm** to save your changes.\
\
The **Deployments** node is displayed along with the **Success – Edited <*****deployment\_name*****>** notification.
{% hint style="success" %}
**Tip**
If you edit the deployment and click **More Info**, you will see the tabs representing the Update Rings are no longer present.
{% endhint %}
## Delete a Single Update Ring
To delete a Single Update Ring:
1. Navigate to the **Assignments** page of the deployment.
2. Click the red **X** beside the Update Ring you want to delete.
{% hint style="info" %}
**Note**
Deleting an Update Ring also deletes any assignments controlled by that ring. If you want to keep the assignment, drag and drop it to another ring before you delete the ring.
{% endhint %}
The ring and any assignments it contains are deleted.
3. Click **Save** to save your changes.\
\
As you’ve removed an Update Ring and it’s assignments, the **"<*****deployment\_name*****>" Deployment Summary** is shown detailing the impact of your proposed change.\
\
For example, by deleting the **7-Zip Pilot +7 Days** ring, this app will not be deployed to the **03 - Patching - Production - All - 7 Days** Entra ID group.\
4. Click **Cancel** to return to the **Assignments** tab to make any required changes, or click **Confirm** to save your changes.\
\
The **Deployments** node is displayed along with the **Success – Edited <*****deployment\_name*****>** notification.
{% hint style="success" %}
**Tip**
If you edit the deployment and click **More Info**, you will see the tab representing the deleted Update Ring is no longer present.
{% endhint %}
# Monitor a Deployment in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
All Patch My PC (PMPC) Cloud deployments include a status.
{% hint style="danger" %}
**Important**
Because PMPC Cloud performs the deployment, not Microsoft Intune, you can only view the status of these deployments in the PMPC Cloud Portal. The status of PMPC Cloud deployments is not visible from within the Intune admin center.
{% endhint %}
To see the status of a deployment:
1. Sign in to the portal at .
2. Navigate to the **Deployments** node.
\
The **Deployments** page loads, showing all current deployments.\
\
The **Status** column shows the current status of each deployment, which will be one of those shown in the table below.
Status
Means the application…
Success
The application was successfully created in Intune.
In Progress
The application is currently being created in Intune. During periods of high activity, processing may take longer than usual. If an issue occurs, the Portal will automatically retry the creation process for up to 24 hours.
During this time, the status will change to Retrying. If the application still cannot be created after 24 hours, the status will change to Failed.
Whilst a deployment is In Progress, no other actions can be performed on it, including editing or deleting the deployment.
Retrying
The application is still being processed. The initial creation attempt was unsuccessful and may have failed due to a Microsoft Graph issue or a temporary issue within Patch My PC services.
No action is required from you as PMPC. Patch My PC will continue retrying the operation for up to 24 hours.
If the deployment remains in a Retrying state for longer than 24 hours, the status will change to Failed.
Failed
The deployment could not be successfully processed and created in Intune.
In some cases, the application may already exist in Intune even though the deployment is marked as Failed.
This can happen when the app is successfully created, but PMPC is unable to complete all required processing steps or confirm the final status.
If a deployment remains unsuccessful after all retry attempts, its status will be changed to Failed.
# Manage Deployments in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
All deployment-related tasks for Patch My PC (PMPC) Cloud are performed from the **Deployments** node of the portal.
To manage deployments:
1. Sign in to the Portal at .
2. Navigate to the **Deployments** node.
\
The **Deployments** page is displayed.
Clicking the ellipsis (**⋮**) beside a deployment opens the management menu, allowing you to:
* [Edit a deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit)
* [Recreate a deployment](/patch-my-pc-cloud/deployments/manage-deployments/recreate)
* [Sort deployments](/patch-my-pc-cloud/deployments/manage-deployments/sort)
* [Delete a deployment](/patch-my-pc-cloud/deployments/manage-deployments/delete)
{% hint style="info" %}
**Note**
See [View a Deployment’s Properties](/patch-my-pc-cloud/deployments/manage-deployments/view-properties) for more details on how to view the properties of a deployment.
{% endhint %}
# View the Properties of Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
To view the properties of a Patch My PC (PMPC) Cloud deployment:
1. On the **Deployments** page, click the relevant deployment to open its properties screen.
2. To find out more details, click **More Info** to open the more info page.
More information about the deployment is shown.
{% hint style="info" %}
**Note**
If [PSADT scripts](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts) have been used in a deployment, the script's name will be shown in the **Configurations** section of the deployment's properties.
Also, if the deployment has any [App Dependencies](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/dependencies), the **Dependencies** section allows you to view them.
{% endhint %}
3. Click **X** in the top-right corner to return to the **Deployments** page, or click **Less Info** to return to the deployment’s property page.
# Edit a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
In Patch My PC (PMPC) Cloud, a successful deployment can be edited (changed) should you wish to change any of its settings (e.g., assignments, command line parameters, etc.).
{% hint style="info" %}
**Note**
Some notes about Deployments:
* Only successful deployments can be edited.
* If you edit a deployment with [App Dependencies](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/dependencies) configured and edit just the dependency, the app won’t be republished in Intune from scratch. However, making any other changes could result in the app being republished.
* If the **Apply Template** option is unavailable when editing a deployment, as templates are currently unsupported for use in existing deployments. See [Use a Template in Deployment](/patch-my-pc-cloud/deployments/use-template) for more information.
* When you edit an existing deployment, if a default template has been configured for the OS platform that this deployment uses, the default template is not applied when you save the deployment.
* If when you edit an existing deployment several variants of the app are available, we prevent you from changing any settings that could lead to issues such as different installer variants of the same app being installed on devices with the currently deployed one already installed.
* Editing a Return Code in an existing deployment does not trigger the recreation of app.
{% endhint %}
There are two ways to edit a deployment:
* [Editing a deployment from the Deployments node](#editing-a-deployment-from-the-deployments-node)
* [Editing a deployment from the App Catalog](#editing-a-deployment-from-the-app-catalog)
## Editing a deployment from the Deployments node
To edit an existing deployment from the **Deployments** node:
1. Navigate to the **Deployments** node.
2. Click the relevant deployment you want to edit.
3. On the deployment's property page click **Edit**.
The Deployment Wizard starts.
4. Follow the [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app) process.
{% hint style="info" %}
**Note**
Be mindful of any changes you make, as you are editing the existing deployment, not creating a new one.
{% endhint %}
{% hint style="success" %}
**Tip**
You can also edit a deployment from the **Deployments** node by clicking the ellipsis (**⋮**) beside the relevant deployment you want to edit, then click **Edit**.
{% endhint %}
## Editing a deployment from the App Catalog
To edit a deployment from the App Catalog:
1. Navigate to the **App Catalog** and click on the app whose deployment you wish to edit.
{% hint style="success" %}
**Tip**
Any apps already deployed by Intune Apps have the green cloud icon with a tick () next to the version number.
{% endhint %}
2. Click **Edit Deployment** on the deployment's property page.
The behavior of the **Edit Deployment** button depends on whether there is at least one existing, successful deployment:
* If there is only deployment for an app, clicking the **Edit Deployment** button starts the Deployment Wizard.
* If there is more than one deployment for the same app, clicking the **Edit Deployment** button provides a dropdown list of all deployments for this app, from which you can select the relevant deployment to edit. Clicking a deployment starts the Deployment Wizard.
{% hint style="info" %}
**Note**
If there is more than one deployment for the same app but any of them are in **Processing**, **Retrying** or **Failed** state, the **Edit Deployment** button still provides a dropdown list of all deployments for this app, but you can only select those that have successfully completed to edit.
{% endhint %}
The Deployment Wizard starts.
3. Follow the [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app) process.
{% hint style="info" %}
**Note**
Be mindful of any changes you make, as you are editing the existing deployment, not creating a new one.
{% endhint %}
# Recreate a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
Using Patch My PC (PMPC) Cloud, you can delete software from Intune and recreate it to retrigger the deployment on the targeted resources.
To recreate a deployment:
1. From the **Deployments** page, click the ellipsis (**⋮**) beside the relevant deployment you want to recreate and click **Recreate**.
2. On the **Are you sure you want to recreate <*****deployment\_name*****>** dialog box, click **Yes**.
\
The **Status** of the deployment changes to **In Progress** and the **Recreating the deployment *****\***** has started** message is displayed.
\
Once the deployment has been recreated, the portal auto-refreshes and the **Status** changes to **Success**.
{% hint style="success" %}
**Tip**
You can also click **Recreate** on the property page of a deployment to recreate it.
{% endhint %}
{% hint style="info" %}
**Note**
If the deployment you are recreating has [Update Rings](/patch-my-pc-cloud/deployments/update-rings) enabled, clicking **Recreate** will result in duplicate versions of the apps being created in Intune. Any existing assignments will be automatically moved from the old version to the new, recreated version.
Also, if the deployment you are recreating has [App Dependencies](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/dependencies), clicking **Recreate** creates a new app, creates any dependencies, deletes the dependencies for the old app, and finally deletes the old app from Intune.
{% endhint %}
# Sort Patch My PC Cloud Deployments
*Applies to: Patch My PC Cloud*
To sort Deployments in Patch My PC (PMPC) Cloud:
On the **Deployments** page, click the relevant column heading to sort the entries by this column.
The column heading will be highlighted and a small arrow will show you whether the results are displayed in ascending or descending order.
To sort by a different column, just click the column name.
{% hint style="info" %}
**Note**
In the current release, you can only sort by certain columns.
{% endhint %}
# Manage Updates to a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
Once Patch My PC (PMPC) Cloud has successfully deployed an app, you need to decide how to manage any updates to that app.
{% hint style="info" %}
**Note**
By default, every morning at 02:00 AM in the country you selected during onboarding, our [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) runs to check for any updates to apps you have successfully deployed. If a newer version is found, we:
* Create a new version of the app in your Intune tenant.
* Move the assignments for the current version over to the new version.
* Install the new version on the relevant devices.
Also, if a deployment has [App Dependencies](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/dependencies) (either this deployment has dependencies on another deployment or another deployment has dependencies on this deployment), at the time the [Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) runs, if a newer version is found, we:
* Create a new version of the app in your Intune tenant.
* Move all the dependencies for the current version over to the new version.
* Install the new version on the relevant devices.
The next time the Sync Schedule runs, that is when we delete the old version of the Intune app, which includes removing it from any Enrollment Status Page (ESP) profiles.
{% endhint %}
All update-related tasks for an app are performed at the deployment level from the **Deployments** node of the PMPC portal by:
Navigating to the **Deployments** node.
The **Deployments** page is then displayed, showing any existing deployments and allowing you to:
* [Pause Updates](/patch-my-pc-cloud/deployments/manage-deployments/updates/pause)
* [Resume Updates](/patch-my-pc-cloud/deployments/manage-deployments/updates/resume-updates)
* [Sync Now](/patch-my-pc-cloud/deployments/manage-deployments/updates/sync-now)
# Pause Updates to a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
The *Pause Updates* feature (which is disabled by default) of Patch My PC (PMPC) Cloud allows you to prevent an app that’s previously been successfully deployed from being updated whenever a new version is released.
{% hint style="danger" %}
**Important**
Pausing updates for an app only affects our portal. If a new version of an app becomes available and updates are paused, the portal won’t create a new version of that app while updates are paused.
However, any existing versions of apps already in Intune that are assigned will still be evaluated and, if applicable, installed by your devices.
{% endhint %}
To Pause Updates for an app:
1. Click on the relevant successful deployment you want to pause for updates.
{% hint style="success" %}
**Tip**
Click the filter button () and select the **Disabled** option under the **Updates** section, followed by **Apply Filters** to see just those deployments that do not have updates paused.
{% endhint %}
2. Click the **Pause Updates** slider to enable it.
3. Click the **X** to close the deployment properties page.
\
The list of deployments is displayed and **UPDATES PAUSED** shows under the deployment name so you updates are paused for this specific deployment.
{% hint style="info" %}
**Note**
If **Pause Updates** is enabled for a Deployment, you can still manually sync it at any time to check for and publish a newer version, if one is available. See the [Sync Now](/patch-my-pc-cloud/deployments/manage-deployments/updates/sync-now) process for more details.
Also, if your deployment has [Update Rings](/patch-my-pc-cloud/deployments/update-rings) enabled and you experience a problem with any of the rings, **Pause Updates** prevents both an existing ring from being upgraded to a new version and any additional Update Rings from being created provided the **Immediate** option was set for the rings.
The **Pause Updates** option will be unavailable if your deployment uses **Delayed** rings and some of these rings have yet to update. As a workaround, you can delete the deployment to stop any outstanding updates.
{% endhint %}
# Resume Updates to a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
If the *Pause Updates* feature of Patch My PC (PMPC) Cloud has been configured for an app that has since been updated, and you want to bring the app up-to-date to the latest version, you need to disable pause updates.
{% hint style="info" %}
**Note**
If an app has more than one version of an update available, resuming updates will ensure it is updated to the latest version.
Also, if you paused a deployment with [Update Rings](/patch-my-pc-cloud/deployments/update-rings) enabled, when you resume updates for that deployment, the Update Rings are re-enabled and function normally.
{% endhint %}
To resume updates for an app:
1. Click on the relevant deployment that has been paused.
{% hint style="success" %}
**Tip**
Click the filter button () and select the **Enabled** option under the **Updates** section, followed by **Apply Filters** to see just those deployments that have updates paused.
{% endhint %}
2. Click the **Pause Updates** slider to disable it.
{% hint style="info" %}
**Note**
Notice on the above screenshot that the **Sync Now** button is available, meaning one or more updates are available for this app.
{% endhint %}
3. Click the **X** to close the deployment properties page.
\
The list of deployments is displayed without **UPDATES PAUSED** under the deployment you just unpaused.
Updates for this app are now resumed.
You now need to decide how you want to install any updates for this app:
* **Install the updates now –** If you want to install the updates as soon as possible, follow the [Sync Now](/patch-my-pc-cloud/deployments/manage-deployments/updates/sync-now) process.
* **Wait for the nightly sync to run –** If you are happy to wait for the updates to be installed the next time the daily sync runs (at 2 am by default), you do not need to do anything.
{% hint style="info" %}
**Note**
You can change the Sync Schedule to a different time, as detailed in the [Managing the Sync Schedule](/patch-my-pc-cloud/manage/settings/sync-schedule) process.
{% endhint %}
# Use the "Sync Now" feature in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
If an app has more than one version of an update available, using **Sync Now** ensures it is updated to the latest version as soon as possible, which could impact your users. So, think carefully before using this.
{% endhint %}
If you have [resumed updates](/patch-my-pc-cloud/deployments/manage-deployments/updates/resume-updates) for an app in Patch My PC (PMPC) Cloud and want to update it as soon as possible rather than waiting for the nightly sync job to run:
1. Click on the relevant deployment which has been resumed.
2. Click **Sync Now** to install any updates for the app immediately.
{% hint style="info" %}
**Note**
If the **Sync Now** button is greyed out, no updates are available for this app.
{% endhint %}
3. On the **Are you sure you want to update <*****app\_name*****> to the latest version** popup, click **OK**.
\
The **Deployment <*****app\_name*****> updated** notification is displayed and the deployment **Status** changes to **In Progress**.
\
Once the deployment has been completed successfully, the **Status** changes to **Success**.
{% hint style="success" %}
**Tip**
If you look in the **Events node**, you will see the following event:
**Deployment <*****app\_name*****> Updated.**
{% endhint %}
# Delete a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
To delete a deployment in Patch My PC (PMPC) Cloud:
1. From the **Deployments** page, click the ellipsis (**⋮**) beside the relevant deployment you want to delete and click **Delete**.
2. On the **Are you sure you want to delete <*****deployment\_name*****>** dialog box, click **Yes**.
{% hint style="info" %}
**Note**
If the deployment you are deleting is for an app that another app is dependent on, the **Are you sure** dialog box will state which app has a dependency on this deployment and warn you that proceeding will delete this dependency, which could break the app dependent on this one.
{% endhint %}
The deployment is deleted and the **Success - Deployment *****\***** deleted** notification is displayed.
{% hint style="danger" %}
**Warning**
Deleting a deployment will also delete the:
* latest and all old unassigned versions of this deployment if a [Retention Policy](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/retention-policy) has been configured.
* packaged win32 app from Intune.
{% endhint %}
{% hint style="success" %}
**Tip**
You can also click **Delete** on the property page of a deployment to delete it.
{% endhint %}
# Technical references for Patch My PC Cloud Deployments
*Applies to: Patch My PC Cloud*
This section contains various deployment-related articles for Patch My PC (PMPC) Cloud.
# Deploy the same App with multiple configurations using Patch My PC Cloud
*Applies to: Patch My PC Cloud*
You can deploy the same app with different configurations using Patch My PC (PMPC) Cloud.
{% hint style="danger" %}
**Important**
For this to work, you must use a different **Display Name** for the deployment. If you don't, you will receive the [deployment with the same name already exists](/patch-my-pc-cloud/troubleshoot/deployments/a-deployment-with-the-same-name-less-than-deployment_name-greater-than-already-exists-error-when-dep) error.
{% endhint %}
To deploy the same app with a different configuration:
1. Sign in to the portal at .
2. Locate the required app on the **App Catalog** page.
{% hint style="success" %}
**Tip**
Use the **Search** field to help you locate the app.
{% endhint %}
{% hint style="info" %}
**Note**
The green cloud icon beside the version number tells you this software has already been deployed using PMPC Cloud.
{% endhint %}
3. Click the app to open its properties, then click **Deploy** to start the Deployment Wizard.
{% hint style="info" %}
**Note**
See the [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app) for more details. You can also apply a deployment template to this deployment by clicking **Apply Template** and following the [Use a Template in Deployments](/patch-my-pc-cloud/deployments/use-template) process.
{% endhint %}
4. On the G**eneral Information** tab, in the **Display Name** field, enter a unique name for this deployment, then click **Next**.
5. On the **Configurations** tab, configure the settings to add any required scripts or additional installation parameters, then click **Next**.
6. On the **Assignments** tab, click **Add Assignment**, then select the assignment type you want to add for this deployment.
7. On the **Add <*****assignment\_type*****> Assignment** page, select the relevant options, then click **Save**.
{% hint style="info" %}
**Note**
If you add an available assignment, as shown below, we recommend selecting the same options in the **Add update only app for** section. Doing this will automatically make the current version of the app and any updates (current or future) available.
{% endhint %}
The **Assignments** page updates to show the newly created deployment.
8. Configure the settings for deployment, if required.
{% hint style="info" %}
**Note**
We automatically configure these settings based on our experience and best practices, but you can modify certain settings if necessary.
{% endhint %}
{% hint style="success" %}
**Tip**
You can click **Deploy** on this page if you don’t want to add additional assignments or see the **Overview** page, which allows you to double-check the settings you’ve configured for this deployment.
{% endhint %}
9. Add any additional assignments for this deployment by clicking **Add Assignment** and repeating Steps 6 to 8, then click **Next**.
10. Review the deployment summary shown on the **Summary** page.\
\
If you are happy, click **Deploy**.
If you need to change something, click **< Prev** to backtrack through the Deployment Wizard to the relevant setting. Make the change, then step back through the wizard to this page. If everything is now correct, click **Deploy**.
The **Deployments** page is displayed along with the **Success - Created *****\*** notification.
{% hint style="info" %}
**Note**
By default, the installation logs for an app will be created in the following folder regardless of the installer file type:
`%ProgramData%\PatchMyPCInstallLogs`
The only exception is for EXE files, where the specified value for the **loggingSwitch** variable will be used if it is not null or empty.
{% endhint %}
# Create a Deployment without Assignments in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Some large organizations want to be able to create deployments in Intune Apps for Patch My PC (PMPC) Cloud without any assignments.
{% hint style="info" %}
**Note**
See [Understand Patch My PC Cloud Assignments](/patch-my-pc-cloud/deployments/technical-references/understand-assignments) for more details about assignments and how they work in PMPC Cloud.
{% endhint %}
Then, their local IT organization adds and manages the assignments to the relevant deployments to meet their needs by using Intune admin center.
To create a deployment with no assignments:
1. Follow the [Deploy an App](/patch-my-pc-cloud/deployments/deploy-app) process until you reach the[ Assignments](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) tab where you can add an assignment.\
\
When you click **Add Assignment**, you will see the **App Without Assignment** sub-menu containing the following two items:
* **Install App -** Allows the Intune admin to add **Required**, **Available**, or **Uninstall** assignments from within the Intune admin center.
* **Update Only App -** Allows the Intune admin to add only an **Update Only** assignment from within the Intune admin center if the **Installer Type** is **.msp**.
{% hint style="info" %}
**Note**
If you are deploying a Microsoft patch file (**.msp**), only the **Update Only App** option is shown under the **App Without Assignment** section as **.msp** files cannot be used to install an app, only update it.
{% endhint %}
{% hint style="success" %}
**Tip**
You can also [Add a Template](/patch-my-pc-cloud/manage/settings/deployment-templates/add-template) with the **App Without Assignments** options configured. Then when you create the deployment, simply click **Apply Template** and select the relevant template to have its settings applied to this deployment.
{% endhint %}
2. Select the relevant option.
3. Uncheck the **Copy-Forward** checkbox if required.\
\
This checkbox is checked by default, which means that whenever we update the app, we remove all assignments from the previous version and add them to the new version.\
\
If the **Copy-Forward** checkbox is unchecked, we keep all assignments from the previous version.
{% hint style="info" %}
**Note**
The **Copy-Forward** checkbox also affects the behavior of assignments when you [recreate a deployment](/patch-my-pc-cloud/deployments/manage-deployments/recreate):
* If the **Copy-Forward** checkbox is checked, any existing assignments will be copied.
* If the **Copy-Forward** checkbox is unchecked, any existing assignments will be deleted.
{% endhint %}
4. Click **Deploy** and wait for the deployment to complete successfully.
Once the deployment has successfully completed, if you look in the Intune admin center you will see that the app has been created without any assignments.
Your local IT teams can now follow the [Assign apps to groups with Microsoft Intune](https://learn.microsoft.com/en-us/mem/intune/apps/apps-deploy) process to add the relevant assignments for this app.
{% hint style="info" %}
**Note**
If you checked the **Copy-Forward** checkbox, the next time the Sync Schedule detects a new version, the assignments are copied forward to the new version. The old version of the app will be removed immediately once the new version has been created and the assignments moved over to it.
Also, a deployment without assignments can be edited and managed in the same way as a regular deployment. See the [Manage Updates](/patch-my-pc-cloud/deployments/manage-deployments/updates) and [Manage Deployments](/patch-my-pc-cloud/deployments/manage-deployments) sections for more details.
{% endhint %}
{% hint style="danger" %}
**Important**
The current release of this feature has the following restrictions:
* A deployment cannot contain both regular assignment types and no assignment types.
* If you edit a deployment with no assignments, you cannot add a regular assignment type.
* If you have a regular deployment with update rings enabled, you cannot edit that deployment, disable update rings, remove all the assignments and then add a new no assignment type.
{% endhint %}
# Reference External Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
If you upload [Extra Files](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/extra-files) as part of your Patch My PC (PMPC) Cloud Deployment, you can reference those files in any of the [Scripts](/patch-my-pc-cloud/deployments/deploy-app/configurations-tab/additional-tools/scripts) in the same deployment by building a path relative to the script's current location.
This ensures your script can reliably locate the files you uploaded, whether they are in the root or a subfolder.
Below are examples for referencing a file named `file_to_be_copied.txt`, either from the script root or a subfolder called `MyFolder`.
## PowerShell (.ps1)
To reference additional files you’ve uploaded, use `$PSScriptRoot\file_to_be_copied.txt` or `$PSScriptRoot\MyFolder\file_to_be_copied.txt` if the file is in a subfolder.
For example:
```
# File in script root
Copy-Item -Path "$PSScriptRoot\file_to_be_copied.txt" -Destination "C:\TargetFolder"
# File in subfolder
Copy-Item -Path "$PSScriptRoot\MyFolder\file_to_be_copied.txt" -Destination "C:\TargetFolder"
```
## Batch / CMD (.bat / .cmd)
To reference additional files you’ve uploaded, use `%~dp0file_to_be_copied.txt` or `%~dp0MyFolder\file_to_be_copied.txt` if the file is in a subfolder.
For example:
```
:: File in script root
copy "%~dp0file_to_be_copied.txt" "C:\TargetFolder"
:: File in subfolder
copy "%~dp0MyFolder\file_to_be_copied.txt" "C:\TargetFolder"
```
## VBScript (.vbs)
To reference additional files you’ve uploaded, use `scriptDir & "\file_to_be_copied.txt"` or `scriptDir & "\MyFolder\file_to_be_copied.txt"` if the file is in a subfolder.
For example:
```
Set fso = CreateObject("Scripting.FileSystemObject")
scriptDir = fso.GetParentFolderName(WScript.ScriptFullName)
' File in script root
fso.CopyFile scriptDir & "\file_to_be_copied.txt", "C:\TargetFolder\"
' File in subfolder
fso.CopyFile scriptDir & "\MyFolder\file_to_be_copied.txt", "C:\TargetFolder\"
```
# Understand Patch My PC Cloud Assignments
*Applies to: Patch My PC Cloud*
As detailed in ["Assignments" tab of a Patch My PC Cloud Deployment](/patch-my-pc-cloud/deployments/deploy-app/assignments-tab) and [Create a Deployment without Assignments in Patch My PC Cloud](/patch-my-pc-cloud/deployments/technical-references/deployment-without-assignments), there are several different types of assignments you can configure for a Patch My PC (PMPC) Cloud deployment.
This article focuses on some caveats and considerations specific to configuring assignments, which, if overlooked, can sometimes lead to errors.
## Assignments types
To quickly recap from the public documentation, there are two ways to deploy applications:
* [Apps with Assignments Configured in the Cloud Portal](#apps-with-assignments-configured-in-the-cloud-portal)
* [Apps without assignments](#apps-without-assignments)
### Apps with Assignments Configured in the Cloud Portal
These deployments can use four assignment types:
* **Required -** The software installation is enforced on targeted devices.
* **Available -** The software appears in the Company Portal for users to install.
* **Uninstall -** The software is removed from targeted devices.
* **UpdateOnly -** Installs a new version only if an older version is already present. Selecting this creates a new Win32 app for the update.
#### Key Point
The Cloud Portal is the source of truth for these deployments. All edits should be made in the Portal, not manually in Intune.
* By default, the Cloud Portal checks daily for new software versions.
* If you make manual changes in Intune, packaging a new version from the Portal can fail.
* Following the Portal as the source of truth ensures your assignments are applied correctly and avoids deployment errors.
### Apps without Assignments
These apps allow manual control in Intune and come in two types:
* **Install App –** A base installation. You can assign it in Intune as **Required**, **Available**, or **Uninstall**.
* **UpdateOnly App –** A conditional Win32 update. Intune evaluates whether a device has an older version installed before applying the update.
#### Key Point
For these apps, Intune is the source of truth. You manage assignments manually in Intune, and the Portal does not enforce them.
* If the **Copy-Forward** option is enabled, the Portal will copy these manual assignments to new versions automatically.
* If **Copy-Forward** is not enabled, assignments are not carried over, and you must manage them manually for each new version.
* Once a deployment is created without assignments in the Portal, you cannot switch it later to a deployment with pre-configured Cloud Portal assignments. You must create a new deployment if you want that functionality.
# Use Patch My PC Scripts in a Patch My PC Cloud Deployment
*Applies to: Patch My PC Cloud*
For certain applications in the Patch My PC (PMPC) App Catalog, we include scripts to enhance the installation and configuration of the app, based on our experience. By default, if an app includes one of our recommended scripts, these are automatically executed at the time the app is installed.
However, this default behavior can cause issues for some customers who are not aware of the scripts and their contents.
To give you better visibility and to allow you to customize the deployment process, for those apps that include our recommended scripts, you will now see the **Customer Scripts | PMPC Scripts** toggle on the **Scripts** tool page of the **Configurations** tab of the PMPC Cloud Deployment Wizard.
Contrast this to an app that does not include any recommended scripts.
Using this feature allows you to:
* [View PMPC Scripts](#viewing-pmpc-scripts)
* [Disable a PMPC Script](#disable-a-pmpc-script)
* [Enable a PMPC Script](#enable-a-pmpc-script)
## View PMPC Scripts
To view the PMPC scripts, click the PMPC Scripts toggle.
Any recommended scripts included with the app are shown.
Once you have clicked PMPC Scripts, you can:
* Hover over the script’s name to see its location.
* Click the script, which will open it in a new browser tab so you can see its contents.
* Click **Edit** to open the script in the relevant script editor window.
{% hint style="info" %}
**Note**
In the current release, you cannot modify the script’s name, format, contents, or arguments. You can disable the script as detailed in [Disable a PMPC Script](#disable-a-pmpc-script).
{% endhint %}
## Disable a PMPC Script
If you do not want to use our recommended scripts in your deployments, you can disable them (although we’d recommend you do not do this unless you have a genuine reason for doing so).
To disable a PMPC script:
1. Either [deploy ](/patch-my-pc-cloud/deployments/deploy-app)or [edit an existing deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit) for the relevant app.
2. Navigate to the **Configurations** tab.
3. Click the **Scripts** tool if it is not already selected.
4. Click **PMPC Scripts**
5. Click **Edit** beside the relevant script.
6. If the app includes a recommended Post-Install script, go to Step 9.
7. If the app includes a recommended Pre-Install script, you have the option of checking either or both of the following checkboxes:
1. **Don’t attempt software update if the pre script returns an exit code other than 0 or 3010**
2. **Disable the Patch My PC Recommended Pre-Install scripts for this product**
8. Go to Step 10.
9. If the app includes a recommended Post-Install script, check the **Disable the Patch My PC Recommended Post-Install scripts for this product** checkbox.
10. Click **Save**
The **Configurations** tab is displayed.
If either a Pre or Post-Install script has been disabled, a red circle is shown beside the script to indicate this and that it will not be included as part of the deployment.
{% hint style="info" %}
**Note**
Checking the **Don’t attempt software update if the pre script returns an exit code other than 0 or 3010** checkbox for a Pre-Install script does not cause the red circle to be displayed.
{% endhint %}
## Enable a PMPC Script
If you have previously [disabled a PMPC Script](#disable-a-pmpc-script), you can re-enable it by [editing the deployment](/patch-my-pc-cloud/deployments/manage-deployments/edit) and following the [Disable a PMPC Script](#disable-a-pmpc-script) section, but uncheck the **Disable the Patch My PC Recommended <*****script\_type*****> for this product** checkbox.
When you click **Save** to save the deployment, a new deployment will be created that includes the script.
## How new versions are handled
If you create a deployment for an app and disable the PMPC Scripts, when your Sync Schedule runs and creates a new deployment for the new version, we check the existing deployment. If you have disabled any scripts, we will also disable them for the new deployment of the new version.
# Events in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Welcome to the Events section for Patch My PC (PMPC) Cloud.
# Overview of Patch My PC Cloud Events
*Applies to: Patch My PC Cloud*
An event is written to the **Events** node whenever a user performs a task in the Patch My PC (PMPC) Cloud portal. Events are also created if the action a user performs triggers a component to perform an activity.
To access the Events node:
1. Using your portal account, sign in at .
2. Navigate to **Events**.
{% hint style="danger" %}
**Important**
Only users assigned the **Full Admin** role will be able to see the **Events** node.
See [User Roles](/patch-my-pc-cloud/manage/settings/users/user-roles-reference) for more information.
{% endhint %}
The **Events** page is then displayed, allowing you to:
* [Search for an Event](/patch-my-pc-cloud/events/search)
* [Export Events](/patch-my-pc-cloud/events/export)
* [Filter Events](/patch-my-pc-cloud/events/filter)
* [Sort Events](/patch-my-pc-cloud/events/sort)
* [Find out more information about an Event](/patch-my-pc-cloud/events/find-more)
* [Change the number of Events per page](/patch-my-pc-cloud/events/configure)
* [Navigate between pages of Events](/patch-my-pc-cloud/events/navigate)
{% hint style="danger" %}
**Important**
Events are only held in the portal for 30 days, after which they are automatically groomed from the database. If you wish to keep events longer than 30 days, follow the [Export Events](/patch-my-pc-cloud/events/export) process.
{% endhint %}
# Search for an Event in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To search for an Event in Patch My PC (PMPC) Cloud, type what you are looking for in the **Search** box on the **Events** page.
{% hint style="info" %}
**Note**
If the portal finds any matching entries as you type, they are displayed. However, if no results are shown when you’ve finished typing your search phrase, either press Enter or click the magnifying glass.
{% endhint %}
The search results of the matching entries is displayed.
To clear the search, either click the red **X** or manually clear the **Search** box.
# Filter Events in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
You can use a *Filter* in Patch My PC (PMPC) Cloud to help you find only the relevant Events you require.
To filter Events:
1. Click the funnel button in the header of the **Events** page.
\
The filter sidebar opens.
2. Configure your required filters, then click **Apply All Filters**.
\
Only the Events matching the filter criteria are displayed.
{% hint style="info" %}
**Note**
You can click the filter button to close the filter sidebar to see more details about the results without affecting the filter.\
\
{% endhint %}
{% hint style="success" %}
**Tip**
When a filter is applied, a green dot appears beside the **Filter** button.
{% endhint %}
To clear a Filter:
1. Click **Clear All** at the bottom of the filter box or navigate to a different page of the portal.
2. Verify the green dot beside the **Filter** button has gone.
# Export Events from Patch My PC Cloud
*Applies to: Patch My PC Cloud*
{% hint style="danger" %}
**Important**
Events are only held in the portal for 30 days, after which they are automatically groomed from the database. If you wish to keep events longer than 30 days, you need to export them.
{% endhint %}
To export today's events from Patch My PC (PMPC) Cloud, plus the past 29 days of events, click **Export** in the header of the **Events** page.
{% hint style="info" %}
**Note**
The number in parentheses beside the **Export** button shows how many events will be exported.
{% endhint %}
A CSV file called **events\_log\_entries.csv** is downloaded to your computer. This contains the number of entries shown in parentheses and can then serve as an archive or be imported to another application for onward manipulation.
We export the following:
* Date
* Title
* Architecture
* Installer Type
* User
* Category
* Operation
* Type
* Version
* Description
Here is an example:
{% hint style="success" %}
**Tip**
You can use Filters to control which events you export, rather than exporting all events. See [Filter Events](/patch-my-pc-cloud/events/filter) for more information.
{% endhint %}
# Sort Events in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To sort Events in Patch My PC (PMPC) Cloud:
On the **Events** page, click the relevant column heading to sort the entries by this column.
The column heading will be highlighted and an arrow will show you whether the results are displayed in ascending or descending order.
To sort by a different column, just click the column name.
{% hint style="info" %}
**Note**
In the current release, you can only sort by certain columns.
{% endhint %}
# Find Out More About an Event in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
You can display more information about a Patch My PC (PMPC) Cloud Event by clicking it.
The details page is displayed for the Event.
Either click the **X** or click outside of the details page to close it.
# Configure the number of Events per page in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To configure the number of events shown per page in Patch My PC (PMPC) Cloud:
Click the down arrow next to **Items per page** in the **Events** page footer and choose the required number.
# Navigate between pages of Events in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
To navigate between pages of Events in Patch My PC (PMPC) Cloud, in the **Events** page footer, click the relevant control to go to the first page, previous page, next page, or last page.
# Technical references for Patch My PC Cloud Events
*Applies to: Patch My PC Cloud*
An event is written to the **Events** node whenever a user performs a task in the Patch My PC (PMPC) Cloud portal. Events are also created if the user's action triggers a component that performs an activity.
Events are created with one of the following severity levels:
* [General Events](/patch-my-pc-cloud/events/technical-references/general)
* [Security Events](/patch-my-pc-cloud/events/technical-references/security)
# Events reference for General Events in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
This article lists the various that are generated with the **General** severity by Patch My PC (PMPC) Cloud for the following categories:
| | | |
| --------------------------- | ----------------------------------- | --------------------------------------- |
| [Application](#application) | [Client](#client) | [Company](#company) |
| [Environment](#environment) | [Intune Branding](#intune-branding) | [Intune Deployment](#intune-deployment) |
| [License](#license) | [MSP Invite](#msp-invite) | [Publisher](#publisher) |
## Application
| Title | Operation Type | Generated when... |
| ----------------------------------------------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Application <*app\_name*> Created | Created | An app is created |
| Application <*app\_name*> Changed by <*user\_name*> | Updated | An app is updated |
| Application <*app\_name*> Removed by <*user\_name*> | Removed | An app is removed |
| Intune Application Discovered | Created | Created the first time Discovery is run in your PMPC Company |
| Intune Discovered Applications Refreshed | Updated | Created whenever someone clicks Refresh Data to refresh your discovery data. |
| Managed Company Relationship for <*child\_company\_name*> Removed by <*user\_name*> | Removed |
A child company is unlinked from a parent MSP company
NOTE This event is shown on both the parent and child companies
|
## Client
| Title | Operation Type | Generated when... |
| ---------------------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------- |
| Client Deployment Created for *\* | Created | PMPC Client has been deployed |
| Client Deployment Updated for *\* | Updated | List of Entra ID Groups PMPC Client deployed to has been updated or the **Uninstall Client** feature is used. |
| Client Deployment Deleted for *\* | Removed | PMPC Client deployment is deleted |
## Company
| Title | Operation Type | Generated when... |
| ------------------------------------------------------------------ | -------------- | ------------------------------------ |
| Company <*company\_name>* Created by <*user\_name>* | Created | A company is created |
| Company <*company\_name>* Updated by <*user\_name>* | Updated | A company is updated |
| Managed Company <*child\_company\_name*> Created by <*user\_name*> | Created | A child company of an MSP is created |
## Environment
| Title | Operation Type | Generated when... |
| ----------------------------------------- | -------------- | ------------------------- |
| Environment <*environment\_name*> Updated | Updated | An environment is updated |
## Intune Branding
| Title | Operation Type | Generated when... |
| -------------------------------------------------- | -------------- | ------------------------------------ |
| Custom Branding <*branding\_app\_name*> Created | Created | A Branding App is created. |
| Custom Branding <*branding\_app\_name*> Recreated | Recreated | A Branding App is recreated. |
| Custom Branding <*branding\_app\_name*> Deleted | Removed | A Branding App is deleted. |
| Custom Branding <*branding\_app\_name*> Updated | Updated | A Branding App is updated. |
| Default Branding - <*branding\_app\_name*> Created | Created | The default Branding App is created. |
| Default Branding - <*branding\_app\_name*> Deleted | Removed | The default Branding App is deleted. |
## Intune Deployment
| Title | Operation Type | Generated when... |
| ------------------------------------------------------------------------ | -------------- | --------------------------------------------- |
| Deployment <*deployment\_name*> Created | Created | An Intune deployment is created. |
| Deployment <*deployment\_name*> Deleted | Removed | An Intune deployment is removed. |
| Deployment <*deployment\_name*> Recreated | Recreated | An Intune deployment is recreated. |
| Deployment <*deployment\_name*> was updated by scheduled synchronization | Synchornized | A deployment is updated by the Sync Schedule. |
## License
| Title | Operation Type | Generated when... |
| --------------------- | -------------- | ------------------------------------------- |
| macOS (Trial) Applied | Applied | A macOS trial begins |
| macOS (Full) Applied | Applied | A full (not trial) macOS license is applied |
## MSP Invite
| Title | Operation Type | Generated when... |
| ------------------------------------------------- | -------------- | ------------------------------------------------- |
| Invitation Accepted by *\* | Approved | A user accepts an invitation to an MSP company |
| Invitation Sent to *\* | Created | An invitation to an MSP company is sent to a user |
| Invitation Deleted by *\* | Removed | A user deletes an invitation to an MSP company |
| Invitation Declined by *\* | Rejected | A user declines an invitation to an MSP company |
## Publisher
| Title | Operation Type | Generated when... |
| ---------------------------- | -------------- | ----------------------------------------------------- |
| Publisher Connection Added | Connected | Publisher is connected to the PMPC Cloud portal. |
| Publisher Connection Removed | Disconnected | Publisher is disconnected from the PMPC Cloud portal. |
# Events reference for Security Events in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
This article lists the various that are generated with the **Security** severity by Patch My PC (PMPC) Cloud.
| Title | Category | Operation Type | Generated when |
| ---------------------------------------------------------------------------------------------------------------------- | ---------- | -------------- | ------------------------------------------------------------------------ |
| Company Ownership Approved for <*user\_name*> | Access | Approved | A user successfully completed the "Recover Your Company" process. |
| Company Ownership Rejected for <*user\_name*> | Access | Rejected | A user failed to complete the "Recover Your Company" process. |
| Customer Support Settings Updated for Company <*company\_name*> | Company | Updated | The settings for a company are updated. |
| Group role with id <*entra\_id\_security\_group\_id*> was created with role <*user\_role\_assigned*> | Group Role | Created | When an Entra ID Security Group is added to the portal |
| Group Role Removed | Group Role | Removed | When an Entra ID Security Group is removed from the portal |
| Group role with name <*group\_name*> and id <*entra\_id\_security\_group\_id*> was changed to role <*new\_user\_role*> | Group Role | Updated | When the role of an Entra ID Security Group is changed within the portal |
| Intune Connection Added | Intune | Connected | An Intune tenant is connected to the portal. |
| Intune Connection Removed | Intune | Disconnected | An Intune tenant is disconnected from the portal. |
| Invitation Sent to <*user\_name*> | Invitation | Created | A user invitation is sent. |
| Preview Features Setting Updated by \ | Company | Updated | A user changes the **Preview Features** setting for a company |
| User Account Created for <*user\_name*> | User | Created | A user is created. |
| <*user\_name*> Removed by <*admin\_name*> | User | Removed | A user is deleted. |
| <*user\_name*> Role Changed by <*admin\_name*>\` | User | Role changed | A user's role is changed. |
# ConfigMgr to Intune App Migration using Patch My PC Cloud
*Applies to: Patch My PC Cloud*
# Overview of ConfigMgr to Intune App Migration using Patch My PC Cloud
*Applies to: Patch My PC Cloud*
The *Migration* feature of Patch My PC (PMPC) Cloud allows you to migrate applications from a Microsoft Configuration Manager (ConfigMgr) hierarchy to a PMPC Cloud company.
Rather than simply copying existing applications *as-is*, our migration experience is designed to support modernization by allowing you to move away from outdated, unsupported, or vulnerable applications and toward applications that are easier to manage and keep secure in a modern Microsoft Intune environment.
As part of the migration process, PMPC Cloud analyzes your existing ConfigMgr applications to help identify:
* Applications that are outdated or no longer supported
* Applications exposed to known Common Vulnerabilities and Exposures (CVEs)
* Opportunities to upgrade to newer, supported versions that are available in the PMPC catalog.
{% hint style="info" %}
**Note**
Migrating ConfigMgr Packages to Intune is unsupported.
{% endhint %}
All migrated applications benefit from additional customization and management capabilities to ensure they remain secure, maintainable, and aligned with modern desktop management practices.
## Application Migration Options
PMPC Cloud supports two methods for migrating applications from ConfigMgr to Intune.
* [PMPC Catalog App](#pmpc-catalog-app)
* [PMPC Custom App](#pmpc-custom-app)
The migration path is determined through ongoing application evaluation, not when the migration is initiated.
{% hint style="info" %}
**Note**
See [How Migration Type Is Determined](/patch-my-pc-cloud/migration/how-migration-type-determined) for more information on how PMPC Cloud determines the appropriate migration path.
{% endhint %}
### PMPC Catalog App
Where possible, PMPC Cloud attempts to match a ConfigMgr application to an existing app in the PMPC catalog. A confident match is typically made using the hash of the main installer binary.
When the hash isn't recognized, PMPC Cloud evaluates application metadata, such as the application title and publisher, to suggest a potential catalog match.
When an application is migrated as a catalog app, it is automatically updated and maintained over time.
### PMPC Custom App
If PMPC Cloud cannot confidently match the application to an app in the PMPC catalog, the application is migrated as a PMPC Custom App.
Custom Apps migrate the exact version, including all installation arguments and customizations, allowing the app to be managed and modified in Intune through the PMPC Cloud Portal.
Unlike applications migrated as catalog apps, PMPC Custom Apps are not automatically kept up to date and require manual updates when new versions are needed.
# ConfigMgr to Intune App Migration using Patch My PC Cloud Requirements
*Applies to: Patch My PC Cloud*
To use the Patch My PC (PMPC) Cloud Migration tool, you need to have a:
* A supported version of Microsoft Configuration Manager (ConfigMgr).
* Patch My PC Publisher, version 2.1.99.0 or later.
* PMPC Cloud Company:
* To which you have an account that has been granted the **Full Admin** user role (either by having this account created directly in the Cloud Company or by being a member of an Entra ID Group that has been granted this role).
* A valid Enterprise Premium or Enterprise Plus license:
* **Enterprise Premium** allows you to:
* Use Publisher to retrieve a list of applications from your ConfigMgr site and send it to your PMPC Cloud Company.
* Use PMPC Cloud to review and evaluate if an application can be migrated to Intune.
* Click **Migrate** (when supported) to migrate the application to Intune, which creates either a:
* Deployment for a PMPC catalog app (if we match to a catalog app).
* Custom App and a Deployment (if we match to a Custom App).
In both cases, you can specify the configuration and assignments in the same way as a regular Cloud deployment.
* **Enterprise Plus** only allows you to:
* Use Publisher to retrieve a list of applications from your ConfigMgr site and send it to your PMPC Cloud Company.
* Use PMPC Cloud to review and evaluate if an application can be migrated to Intune.
{% hint style="danger" %}
**Important**
Because the Migration feature is part of our Enterprise Premium license SKU, if your PMPC Cloud company is using an Enterprise Plus license, the **Migrate** button will be locked, preventing you from migrating the app to PMPC Cloud.
However, the [Migration Dashboard](/patch-my-pc-cloud/migration/about-migration-dashboard) is available and can be used to give you an overview of the detected ConfigMgr applications and to see a list of the ConfigMgr applications detected, along with their associated information.
To unlock the **Migrate** button so you can perform the migration, you either need to:
* [Request a quote for upgrading to Enterprise Premium](/patch-my-pc-cloud/manage/settings/subscription/license/request-quote).
* [Sign up for an Enterprise Premium Trial from Enterprise Plus](/patch-my-pc-cloud/manage/settings/company-settings/sign-up-enterprise-premium-trial), which allows you to migrate up to five applications.
{% endhint %}
{% hint style="info" %}
**Note**
The Migration feature is unsupported if your PMPC Cloud company is running an MSP license.
{% endhint %}
# Setting Up ConfigMgr to Intune App Migration for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
Before you can perform a migration using the Patch My PC (PMPC) Cloud *Migration* feature, you need to ensure that Publisher is connected to the same PMPC Cloud Company that you plan to migrate the objects to.
{% hint style="info" %}
**Note**
See [Add a Connection](/patch-my-pc-cloud/manage/settings/connections/add-connection) for further details.
{% endhint %}
You also need to ensure that the **Enable application migration** checkbox on the **Cloud** tab is checked.
{% hint style="info" %}
**Note**
If you do not see the **Enable Application Migration** checkbox on the **Cloud** tab, ensure you are running the required version of Publisher as detailed in [Migration Requirements](/patch-my-pc-cloud/migration/requirements).
Also, if the [Publisher was connected to the Cloud](https://docs.patchmypc.com/patch-my-pc-publisher/administration/cloud) more than 90 days ago, you may be prompted to sign in again using an account that has access to the Cloud Portal.
This is expected behavior as we do not control the authentication token, and once it expires, it must be renewed by re-authenticating.
{% endhint %}
By default, Publisher polls the ConfigMgr Site Database every 60 minutes for application changes.
{% hint style="danger" %}
**Important**
If you click **Disconnect** on the Publisher's **Cloud** tab, all of the Migration features data will be deleted from your PMPC Cloud company. You should therefore avoid doing this until you have completed the migration of all required items from ConfigMgr to PMPC Cloud.
{% endhint %}
Next, sign in to your PMPC Cloud company and verify that the **Migration** node is visible in the Cloud Portal.
{% hint style="success" %}
**Tip**
The following log files can be used for more information and for troubleshooting the migration feature:
`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs\PatchMyPC-AppMigrationService.log”`
`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs\PatchMyPC-CloudFileUploadBackgroundService.log”`
`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\PatchMyPC.log”`
{% endhint %}
{% hint style="info" %}
**Note:**
For new installations of Patch My PC Publisher, the **PatchMyPC.log** file will exist in the following folder:
`"%ProgramFiles%\Patch My PC\Patch My PC Publishing Service\Logs"`
{% endhint %}
# About the ConfigMgr to Intune App Migration for Patch My PC Cloud Migration Dashboard
*Applies to: Patch My PC Cloud*
When you click the **Migration** node in the Patch My PC (PMPC) Cloud Portal, the **Migration** page opens with the **Dashboard** tab selected by default, which provides an overview of the detected ConfigMgr applications.
## Dashboard tab
The dashboards are:
### ConfigMgr Apps
Provides a breakdown of detected ConfigMgr applications by match type.
{% hint style="info" %}
**Note**
See the **Match Type** field in the [Apps tab](#apps-tab) section below for more information on how apps are matched.
{% endhint %}
### CVEs Detected
This chart shows the number of known vulnerabilities (CVEs) associated with applications discovered in your ConfigMgr environment.
If we recognize the hash of a ConfigMgr app, we check whether that hash is associated with any published CVEs. If matches are found, the CVEs are grouped by severity (Critical, High, Medium, Low).
In the screenshot example, we found:
* 1 x Critical CVE
* 12 x High-severity CVEs
* 6 x Medium severity CVEs
* 2 x Low severity CVEs
Giving us a total of 21 CVEs across all ConfigMgr applications, where we recognized the hash of the installer.
### Migration Status
Shows the total number of ConfigMgr applications discovered and their current migration progress.
### Unsupported Apps
Displays the number of ConfigMgr applications that cannot be migrated, with reasons based on validation errors.
### App Update Status
Displays ConfigMgr applications in your environment that are out of date.
## 'Apps' tab
From the **Migration Dashboard**, you can click the **Apps** tab to see a list of the ConfigMgr applications that have been detected with their associated information.
Field
Description
Match Type
The result of our attempt to match the ConfigMgr application to an app in our App Catalog, which will be one of the following:
Catalog App – We have successfully matched the ConfigMgr application to a version in our catalog. These apps can be deployed into Intune as a PMPC App and kept up to date by us for you.
Custom App – We have been unable to successfully match the ConfigMgr application to a version in our catalog, but we can still help you migrate it to Intune.
Publisher App – We have identified that the application was created by Patch My PC Publisher. These apps are not supported for migration.
Multiple Matches - We have found multiple matches in our catalog to the app that is to be migrated.
TIP: You can hover over the “(i)” for an unsupported match type to see why it is unsupported for migration.
Matched App
The name of the app we have matched the ConfigMgr application to in our catalog.
Status
The migration status of the ConfigMgr application, which will be one of the following:
Not Started – The migration process has not been started.
Pending – The migration process has been initiated.
Importing - The app is currently being processed by the Publisher and is being imported to the PMPC Cloud Portal.
In Progress – The migration is in progress.
Migrated – The application has been successfully migrated to PMPC Cloud.
Failed - The migration encountered an error.
Info
If there are further information/warnings about this application that we want you to review (e.g. we’ve detected a setting in the ConfigMgr application we cannot migrate), a warning triangle is displayed in the Info column.
The triangle includes a number indicating the number of warnings. If you hover your mouse over the triangle, you will see a summary. If you click the triangle, it opens the properties of the application and displays the triangle beside the items we are warning you about.
Clicking the triangle shows more details you should review before continuing the application migration.
{% hint style="info" %}
**Note**
The last column displays the **Migrate** button, which you click to migrate the application.
If there are multiple matches for the application, the **Migrate** button will show as either of the following:
* Without a down arrow if we’ve matched the app to at least one Public app, but not a Custom App. When you click **Migrate**, the Migration Wizard starts, allowing you to choose the relevant app to migrate this application to.
* With a down arrow, which, when clicked, shows a dropdown with two options:
* **Migrate as Catalog**, which either shows the single matching app or the available multiple matches to the Catalog apps from which you can select the one you want to migrate this app to.
* **Migrate as Custom**, will start the migration of the app as a Custom App without the option to select any other app.
Also note that the **Migrate** button will be unavailable if:
* The application cannot be migrated or has already been migrated to PMPC Cloud.
* You do not have the correct license for your PMPC Cloud Company.
{% endhint %}
# How Migration Type is Determined in ConfigMgr to Intune App Migration for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
The *Migration* feature of Patch My PC (PMPC) Cloud evaluates Microsoft Configuration Manager (ConfigMgr) applications using an initial full scan when the environment is first connected, followed by delta scans that run every 60 minutes by default, but can also be triggered manually.
These scans detect changes to application metadata and determine whether an application can be reliably migrated as a PMPC Catalog App, a PMPC Custom App, or is unsupported for migration.
Where possible, PMPC Cloud prefers migrating applications as catalog apps, as this ensures they can be automatically kept up to date. PMPC Cloud cannot automatically update PMPC Custom Apps when a vendor releases a new version, as Custom Apps are not tracked in the catalog.
### Option 1: Publish the App in Intune as a PMPC Catalog App
Wherever possible, we attempt to match ConfigMgr applications to an existing app in our catalog using the installer hash. When a match is found, you can deploy the catalog app to Intune instead of the version in ConfigMgr, which may be out of support or exposed to known vulnerabilities.
When we migrate ConfigMgr applications using this method, we also migrate any installation arguments, customizations, and command lines you have defined for the ConfigMgr application.
The end result is that you now have a version of the app deployed that can be managed and kept up to date for the app's lifetime.
{% hint style="info" %}
**Note**
See [Publish the App in Intune as a PMPC Catalog App](/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app) for more information.
{% endhint %}
### Option 2: Publish the App in Intune as a **Suggested** PMPC Catalog App
In some cases, we cannot confidently match a ConfigMgr application to a catalog app using the installer hash alone. When this happens, we evaluate additional application metadata to determine whether a reliable catalog match can still be suggested.
This evaluation may include:
* Application display name
* Application vendor
* Installer type (for example MSI or EXE)
* Installer context (system or user).
If these indicators collectively align with a known catalog app, we may suggest migrating the application as a PMPC Catalog App even when a direct installer hash match isn’t available. This allows you to leverage our catalog-based updates while making it clear that the match is based on metadata rather than binary identification.
{% hint style="info" %}
**Note**
See [Publish the App in Intune as a Suggested PMPC Catalog App](/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-suggested-app) for more information.
{% endhint %}
### Option 3: Publish the App in Intune as a PMPC Custom App
For those ConfigMgr applications that we cannot find a direct match to an app in our catalog, we can still migrate them, but as a [PMPC Custom App](/patch-my-pc-cloud/custom-apps/custom-apps-overview).
When we migrate ConfigMgr applications using this method, we migrate the exact version and include the migration of all installation arguments, customizations, and command lines you have defined for the ConfigMgr application.
You will be able to modify and manage the app from within the PMPC Cloud Portal and take advantage of the various customizations and features of PMPC Cloud Custom Apps.
{% hint style="info" %}
**Note**
See [Publish the App in Intune as a PMPC Custom App](/patch-my-pc-cloud/migration/migrate-application/publish-migrated-app-catalog-app-1) for more information.
{% endhint %}
# How Different Applications are Migrated in ConfigMgr to Intune App Migration for Patch My PC Cloud
*Applies to: Patch My PC Cloud*
# Migrate EXE-based Applications from ConfigMgr to Intune using Patch My PC Cloud App Migration
*Applies to: Patch My PC Cloud*
When applications are inventoried from Microsoft Configuration Manager (ConfigMgr), Patch My PC (PMPC) Cloud analyzes the application metadata to determine how the application is installed and how it should be migrated. As part of this process, the installation command line is evaluated, and the primary installer file is identified from the application’s content source folder.
## Identifying an EXE-based App
ConfigMgr does not explicitly label an application as EXE-based. In most cases, the easiest way to confirm an application is EXE-based is to select the application from the Migration dashboard and review the **Installation Program** field.
If the **Installation Program** references an **.exe** file, the application can be considered EXE-based.
{% hint style="info" %}
**Note**
When evaluating EXE-based applications, references to helper executables such as **msiexec.exe**, **powershell.exe**, and the PowerShell App Deployment Toolkit (PSADT) are not classified as EXE-based installers; instead, they are treated as [MSI-based](/patch-my-pc-cloud/migration/how-different-apps-migrated/migrate-msi-apps), [Script-based](/patch-my-pc-cloud/migration/how-different-apps-migrated/migrate-script-apps), or [PSADT-based](/patch-my-pc-cloud/migration/how-different-apps-migrated/migrate-psadt-based-apps).
{% endhint %}
During the migration deployment flow, the **Installer Type** field also indicates when an application is being treated as EXE-based.
If the application is identified as EXE-based, as much of the existing metadata as possible is captured to support migration. This includes analyzing the install command line, the main installer file, and any supporting content to ensure the application behaves the same way after migration to Intune.
## Migration Behavior of EXE-based Apps
The information analyzed is used to determine how the application is migrated and how the installation is executed. Any custom command-line arguments defined in ConfigMgr are preserved, and all supporting files in the original content source folder are included in the migration.
{% hint style="info" %}
**Note**
The only exception is the primary installer itself. When an application is migrated as a PMPC Catalog App, the original installer and version are replaced with the latest version available in the PMPC catalog. When migrating as a PMPC Custom App, the original installer and version are retained and used.
{% endhint %}
When the application is migrated, **PatchMyPC-ScriptRunner.exe** becomes the new primary installer and invokes the original EXE with the existing command-line arguments. This approach preserves the original installation behavior whilst allowing the deployment to leverage additional PMPC customizations that would not be available with a "lift and shift" migration.
In the following, an older version of Notepad++ has been matched to a PMPC Catalog App. The original ConfigMgr application included an additional command-line argument, **/noupdater**, which has been preserved and carried through into the migration flow to ensure the application is deployed with the same installation behavior.
## Preserved Properties of EXE-based Apps
This section details the properties that are carried forward from the ConfigMgr application to the migration deployment flow when the application is either matched to:
* [PMPC Catalog App](#pmpc-catalog-app-properties-preserved)
* [PMPC Custom App](#pmpc-custom-app-properties-preserved)
{% hint style="info" %}
**Note**
See [How Migration Type is Determined](/patch-my-pc-cloud/migration/how-migration-type-determined) to understand how ConfigMgr applications are matched during migration.
{% endhint %}
### PMPC Catalog App Properties Preserved
* Source Files (the main EXE-based installer will be replaced with the current version of the matched application in the Patch My PC catalog)
* DisplayName
* Additional Arguments
* Return Codes
* Vendor
* Description
* Information URL
* Privacy URL
### PMPC Custom App Properties Preserved
* Source Files
* DisplayName
* Vendor
* Description
* Version
* Silent Install Parameters
* Installer Type
* Additional Arguments
* Return Codes
* Information URL
* Privacy URL
* Detection Rules
# Migrate MSI-based Applications from ConfigMgr to Intune using Patch My PC Cloud App Migration
*Applies to: Patch My PC Cloud*
When applications are inventoried from Microsoft Configuration Manager (ConfigMgr), Patch My PC (PMPC) Cloud analyzes each application's metadata to determine how it is installed and should be migrated. As part of this process, the installation command line is evaluated, and the primary installer file is identified from the application’s content source folder.
## Identifying an MSI-based App
ConfigMgr does not explicitly label an application as MSI-based. In most cases, the easiest way to confirm an application is MSI-based is to select the application from the Migration dashboard and review the Installation Program field.
If the **Installation Program** contains both **msiexec** and a reference to a **.msi** file, the application can be considered MSI-based.
During the migration deployment flow, the **Installer Type** field also indicates when an application is being treated as MSI-based.
If an application is identified as MSI-based, as much existing metadata as possible is captured to support migration, drawing from both the ConfigMgr application and the MSI properties table.
This includes analyzing the following to help ensure the application behaves the same way after it is migrated to Intune:
* installation command line
* primary installer file
* conflicting processes
* any supporting content.
## Migration Behavior of MSI-based Apps
The information analyzed is used to determine how the application is migrated and how the installation is executed. All supporting files in the original content source folder are included in the migration.
{% hint style="info" %}
**Note**
The only exception is the primary installer itself. When an application is migrated as a PMPC Catalog App, the original installer and version are replaced with the latest version available in the PMPC catalog. When migrating as a PMPC Custom App, the original installer and version are retained and used.
{% endhint %}
MSI properties (**PROPERTY=value**) are preserved and applied to the created deployment.
Detection rules are carried across during migration; however, the default PMPC detection rule (which detects applications based on the MSI product code) is enabled by default in the migration flow. If required, this can be changed to **Use Custom** on the **Detection Rules** tab to use the detection rules defined in ConfigMgr instead.
When the application is migrated, **PatchMyPC-ScriptRunner.exe** becomes the new primary installer and invokes the original MSI. This approach preserves the original installation behavior whilst enabling the deployment to leverage additional Patch My PC customizations that would be unavailable with a "lift and shift" migration.
## Preserved Properties of MSI-based Apps
The following information indicates the properties that are carried forward from the ConfigMgr application to the migration deployment flow when the application is either matched to a PMPC Catalog App or a PMPC Custom App.
{% hint style="info" %}
**Note**
See [How Migration Type is Determined](/patch-my-pc-cloud/migration/how-migration-type-determined) to understand how ConfigMgr applications are matched during migration.
{% endhint %}
### PMPC Catalog App Properties Preserved
* Source Files (the main MSI-based installer will be replaced with the current version of the matched application in the Patch My PC catalog)
* DisplayName
* MSI Properties (not visible in the Deployment created, but are present in the app metadata)
* Return Codes
* Vendor
* Description
* Information URL
* Privacy URL.
### PMPC Custom App Properties Preserved
* Source Files
* DisplayName
* Vendor
* Description
* Version
* MSI Properties
* Installer Type
* Return Codes
* Information URL
* Privacy URL.
# Migrate Script-based Applications from ConfigMgr to Intune using Patch My PC Cloud App Migration
*Applies to: Patch My PC Cloud*
{% hint style="info" %}
**Note**
Support for Script-based apps is still in development and is expected to be available soon.
{% endhint %}
When applications are inventoried from Microsoft Configuration Manager (ConfigMgr), Patch My PC (PMPC) Cloud analyzes the application metadata to determine how the application is installed and should be migrated. As part of this process, the installation command line is evaluated, and the primary installer file is identified from the application’s content source folder.
## Identifying a Script-based App
ConfigMgr does not explicitly label an application as Script-based. In most cases, the easiest way to confirm that an application is Script-based is to select the application from the Migration dashboard and review the **Installation Program** field.
If the **Installation Program** contains a **.ps1, .cmd, .bat** or **.vbs** file reference, the application can be considered Script-based.
During the migration deployment flow, the **File** tab also indicates when an application is being treated as Script-based, and the script content is displayed.
If the application is identified as Script-based, as much of the existing metadata as possible is captured to support migration. This includes any supporting content to ensure the application behaves the same way after migration to Intune.
## Migration Behavior of Script-based Apps
Script-based apps can only be migrated as PMPC Custom Apps.
When the application is migrated, **PatchMyPC-ScriptRunner.exe** becomes the new primary installer and invokes the original script defined in the installation command line. This approach preserves the original installation behavior whilst allowing the deployment to leverage additional PMPC customizations that would be unavailable with a "lift and shift" migration.
In the example below, a PowerShell-based Windows Update script is being migrated. The installation script content is displayed inline within the migration flow, allowing it to be reviewed or edited before proceeding. The script is currently not code-signed, as indicated by the warning below the editor. The script can be exported for signing and then re-imported, or migrated "as-is," depending on your organization’s script-signing requirements.
{% hint style="danger" %}
**Important**
If the script is code-signed, any modification on the **File** tab will invalidate the existing signature. For this reason, editing should only be performed on unsigned scripts. Signed scripts should be exported, re-signed after any changes, and then re-imported before completing the migration.
{% endhint %}
## Preserved Properties of Script-based Apps
The following information indicates the properties that are carried forward from the ConfigMgr application to the migration deployment flow when the application is migrated as a PMPC Custom App:
* Source Files
* DisplayName
* Vendor
* Description
* Version
* Return Codes
* Information URL
* Privacy URL
* Detection Rules.
---
[Next Page](/llms-full.txt/1)