Patch My PC Publisher

We would like to be notified when PMPC adds or modifies a product in any section on the Known Issues and Considerations page after it is deployed. There have been instances where an update is deployed and later shows up on the section for conflict...

it would be helpful if you don't have to manually assign every single application or update to a group in Intune, but could do this with a mulitselect for multiple applications or updates at once.

On the Publisher.. you could configure a "+" button to the right of every Product. clicking on this lets you add a SCOPE to the product/category.. or select a scope that was already added. You would also be able to remove a SCOPE from the list.. d...

Postponed applications in ConfigMgr should be able to be postponed at least as long as the maximum number of days between patch Tuesdays.

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...

Currently Publisher supports sending the Publisher Report via SMTP or Webhook on the Alerts configuration tab. It's fairly typical in products that send reports via email that there are also options to have reports saved to a folder but this is mi...

Different companies do source folders differently it would be nice to change/affect the structure that is created. For example creating an app that has the same name as the source folder would make it easy to track the what source folder is attach...

When customizing an update, it is possible to enable the "Manage conflicting processes..." option and configure a desktop notification to require the user to close running apps. That notification is custom-made and does not intergrate seamlessly w...

When republishing an existing app after making changes to the included files and scripts, the Publishing Service leaves the old files in place and doesn't overwrite updated files causing unintended and inconsistent behavior. Please purge the sourc...

Adobe is switching Reader to 64-bit. Reader 32-bit should consider itself installed if 64-bit is already installed. We shouldn't need to rely on CM collection queries.