Patch My PC Publisher

Currently setting Manage Conflicting Processes at the top level automatically applies to all products in the catalogue and you can opt products out of that option. Alternatively if you only want Manage Conflicting Processes for a handful of produc...

As per Idea PATCHMYPC-I-317 could we enhance the registry key value to also use this path to store the scripts for Intune and Intune Updates. Could this also be enhanced to create the folders if its missing. Currently if you do not have the folder...

I'm fairly certain this is already a feature for configman applications and updates. It would be nice for that to be an option for intune applications as well.

this would allow us to set apps that can only or could never install during autopilot. The requirement would be for a registry value hklm\software\microsoft\windows nt\currentversion\winlogon defaultuser equals or doesnotequal defaultuser0

A module in the publisher that would connect to a git repository and use that database to manage proactive remediation and /or powershell scripts. To go a little deeper you could make each PR a single git repo with an PAT or ssh Key. The publisher...

It would be great to have the option to hide the Intune Apps and Intune Updates tab similar to how we hide the Config Mgr apps and updates tabs for Intune standalone mode.

Intune will only attempt to install an application 3 times, before it gives up entirely. The manage conflicting Processes feature currently allows the user to defer installation for more than 3 attempts. This may cause users to never receive an up...

For Intune Apps and Updates, it would be nice to take action on notifications generated by the Publisher, a button to take you to the newly generated Intune App/Update is the first thing that comes to mind.

a template with the patchmypc publisher already installed would be great for automation. Especially if you could export all of your configurations and have it build on a schedule.

It would be nice if we could right click for updates/applications and force a validation to see if the publisher can find the file stored in the local content share.