Patch My PC Publisher

Instead of sending 1 email for all customers from Publisher to MSPs, allow the sending of 1 email per customer so that they can be shared with customers easier.

Ideas: 1) Set assignments to XYZ groups until specified date then delete that rule 2) Delay Intune assignment for X period (e.g. year end accounts) for specific group or filter 3) Auto exclusions

Add support for user-based apps that store data in HKLM ARP instead of HKCU. Some user-based apps do this and today our detection for user-based apps only looks in HKCU.

It would be nice to have a way to set gradual enforcement of installation conflicting process behavior. Example would be first 10 days to deploy required immediately and defer on conflicting process. Days 10-20 prompt the users of conflicting proc...

Similar to the CVE Import Wizard for CM applications / updates (https://patchmypc.com/how-the-cve-import-wizard-works-for-matching-cve-ids) It'd be a great idea to allow the same functionality for Intune applications / updates.

Our standard is to hide / not populate these URLs because we do not want to have our users clicking out directly to third party websites. Instead we would prefer they call our helpdesk with any issues they have.

I would like to be able to change the process conflict defer options for CVE or Critical Severity updates. Normally I don't mind users taking upto 5 days or 5 defer attempts (as an example) for a normal software update. However if that software up...

When auto-publishing rules for updates/apps are created, Patch My PC will create the Win32 application in Intune, however it will not automatically assign the application. This means that it's difficult for MSPs to manage for a large number of cli...

Almost all our apps deploy ASAP to a subset of Test Users, and then they vary for +5 / +10 / +15 days for general population. I'd love to see some sort of Visual for a how many days or on what specific days the apps will publish to the general pop...

Had a few occasions lately where the Cached package was missing or corrupt. This caused the built in Repair option to fail. Changing the repair option to the following corrected the issue. Using the v option to re-cache the local file. msiexec.exe...