Patch My PC Publisher

Setting the option to Prune old log files to 0 in the Advanced tab should disable log pruning on the endpoints completely.

We don't like users to have uninstall/repair options on applications. We'd like to be able to switch this off by default for all applications.

Currently, if and when an administrator unticks an application from the 'ConfigMgr Apps' tab in the Publishing console to cease creating/updating an application object, previously built applications are not deleted from SCCM and the sources are le...

Some apps install fine even if an older version is running, but fail to uninstall if the app is running.Would be nice to allow configuring the Manage Conflicting Processes notification individually, per install or uninstall purpose. Or configure i...

Currently, under "Manage installation logging", it is possible to select the folder where logs will be generated when the installation/update of a software occurs. The logname is based on the installer's filename (i.e. for Github CLI 2.32.0 -->...

Currently, under "Manage installation logging", it is possible to select the folder where logs will be generated when the installation/update of a software occurs. The logname is based on the installer's filename (i.e. for Github CLI 2.32.0 -->...

It would be helpful especially for Local Content to see the SHA256 (or SHA1) hash of the software from the catalog so that this can be compared against local content.

Would be nice to have the ability to easily compare a customer's list of apps against the list of PMPC supported products, to show which apps the customer can patch using the Publisher.At the moment, a lot of manual work needs to be done in Excel,...

Show update classification and severity in Show package info

At this time, notifications are sent out when a new Publisher version is installed, however, there are no notifications when a new publisher version is available. A notification when a new version of the Publisher was made available would be helpf...