A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
The Publisher currently only attempts downloads for packages a single time before failing. It would be beneficial for the Publisher to retry downloads a configurable number of times before failing a download. This would be especially helpful for d...
Detection methods supported in the generic detection script (PowerShell) - only work for MSI or Registry. One application, Adobe Digital Editions, currently can only be properly detected by looking at an info attribute of the installed exe file, s...
Today we can't support products which are either originally sourced or downloaded as .zip or .exe with an extractable parameter. This request is to support products which are supplied by vendors in this format. Example products: Autodesk Desktop C...
Support Remotely Changing the Publishing Service Settings from Another Device
I'm not sure if this is too much of a stretch, would over-complicate things or even possible but figured I'd put it out there.
It'd be nice to have a single pane of glass to work from, even if it was only the commonly used features eg Update Rule...
Add a Right-Click option similar to the "Add 32bit OS requirement" for ARM64 Requirements. This will allow 32 and 64-bit applications that can be emulated on ARM64 to be installed on those endpoints.
Alerts - webhooks configurable based on update severity
It would be useful to be able to create alerts (webhooks) based on the severity of updates, to get the "Critical" or "Important" updates to a different channel
We would like to have an option to create a custom detection rule for some applications. E.g. Adobe Acrobat Reader gets updated automatically but I don't want to offer this application as "new" to our users, since everything will get updated event...
It would be beneficial for MSP's to be able to track who enabled or disabled apps in patch my pc. A log to track changes made with the user against that action would help to discover when and who selected the installation from pmpc
Hi, It would be great if it was possible to decide where the PMP define scripts logs are saved on the client's computer. Currently, the following is hardcoded under the PatchMyPC-Remove-Application-X.ps1 script : "C:\Windows\Temp\PatchMyPC-' + $($...