Patch My PC Publisher

When testing application publishing and modifying application settings, the publishing tool should update the Intune or SCCM application if there was a change to any of the options that are available via right click. Currently, the tool will only ...

We are using ADR to automate a flow from test to production. Patches/applications have to be approved before we are pushing them into production because of our complex infrastructure and a desire not to interfere with patches every day. But someti...

As it's not always needed to see all applications/updates available to be published, a filter to show only applications/packages that have been enabled or disabled might make the environment less cluttered and easier to skip to the "meat".

Hello, Some of our users have vision problems and are not able to read the toast notification when a software has to be closed with a screen reader like Jaws or NVDA. We have tested the notification behavior with Jaws and NVDA and only the title o...

For End of Life products without anymore updates available… there could be a final update in the catalog that has the same applicability rule(s) detecting the EOL product being present on a system but instead of installing an update actually remov...

This relates to the recently shipped idea, PATCHMYPC-I-1862. Currently the list of delayed ConfigMgr applications in email notifications are sorted in reverse alphabetical order by application name. Requesting to have the default sort order change...

It's maybe not always obvious to someone new to it that clicking "apply" doesn't sync your changes immediately. Thoughts on something like the above that says "you've made changes, do you want to sync now or wait to the next sync?"

It isn't necessarily obvious that clicking "OK" will apply the settings/changes that have been made within the Publisher or that it will close the Publisher. Changing "OK" to be something like "Apply and Close" would potentially make it more user ...

With the PMPC option to update apps in place, custom requirements are kept when the app is updated to a new revision for a newer version.However, OS requirements are not retained, they are reverted to the default OS requirement PMPC configures.

We already have the "Do not include the version in the application name, so the application name doesn't change after updates" option but it would be nice if we could also exclude the version information from the Deployment Type name. We have "Jab...