Patch My PC Publisher

If content is being distributed to only a specific DP group, and new DPs are added, the content is not distributed to those DPs for the already created applications.Would be good to have such an option.

In some cases, IT Admins might want to override the general settings specified in the Publisher, it would be good to easily recognize which ones they are.

When setting assignments for Intune, one can create deployment rings and set it to install after a certain number of days.Can the same be done similar to Autopatch, to only move on if the previous assignment had a certain percentage success rate?

Please allow the option to have a list of previously created apps which were deleted because a newer version was created in a dedicated channel.

If the option to "Update Existing application in place" is set, and the "delay" option is used, if the switch is made to the "Create a new application" option, create the postponed apps at the next sync run, instead of waiting until the delay peri...

When updating existing SCCM apps in place, and when a new version is released, the update in SCCM is delayed by an X number of days, reference in the log file for how many days the publish is still delayed.

If we know that Package.xml should look like package.xml_1 but it actually looks like package.xml_2 then update/rectify that package.xml file

When snoozing an update, if a user updated the installation in the meantime via company portal or by itself. it will still prompt the installation again, afterwards.

After an jre update, it's always listed in the "recent added" list under windows. It's very annoying. Would be great if there's an option to disable this

Give each catalogue release a version number and when the Publisher pulls down the catalogue each sync, Write that catalogue version number out to PatchMyPC.log