Patch My PC Ideas & Feedback
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Allow the deployment name to be separate from the displayName, so we can keep displayNames clean and consistent while still assigning unique deployment names behind the scenes.
Today, Patch My PC pulls the deployment name to match the app displayName, which makes it difficult to maintain clean and consistent naming when creating multiple deployments of the same app.
7‑Zip:
We currently hard‑code values like installer type and architecture directly into the displayName (e.g., 7‑Zip (MSI‑64‑bit)) just to keep deployments unique.
If we instead rely on %InstallType% in the naming convention, Patch My PC produces:7‑Zip (MSI‑64‑bit) 25.01 (MSI) – PMPC
This results in duplicate “MSI” entries and inconsistent naming.
Grammarly:
We maintain separate deployments for Install & Update and Update‑Only, and both should share the same displayName.
However, since deployment names must be unique and tied to the displayName, we’re forced to change one of the displayNames unnecessarily.
We would like to have different settings set when conflicting processes found. For Install only deployment, prompt the user to close the apps and for update only deployments, skip the installation. We create 2 separate deployments in PMPC to achieve this and have prefix "Update for" set for update only deployment. However, when PMPC creates app in Intune, it uses Prefix and Display name of the deployment. Which has to be different from "Install" only deployment. As a result, there is no consistency in Appname. Allowing to use App name instead of display name would achieve this. I submitted case # 00034586.