Ideas

Sometimes I want to scan the DB for products we have enabled, but no longer need to deploy. However, I can't sort the list by what is enabled (like I can with vendor/product/count). I have to export the list and sort the CSV, then go back to the G...

It could be helpful to be able to pass the results of the pre-script to the command line of an application. Specifically, the Tenable Nessus Agent can have groups assigned at install time, it would be nice to read that info from ConfigMgr. We have...

For MSP customers who are using one standard PMPC configuration for all tenants, it would be nice to have a per tenant copy button in the Publisher. Similar to the copy function across tabs, but for multiple connect intune tenants. For example, I ...

Today the intune apps created get in the notes a GUID for the specific update of an app This means if you have 3 updates of Google Chrome they each get a different ID Could another GUID be added which identifies the Application, which remains the ...

Staging Explorer enables you to rapidly transfer large amounts of data to and from RelativityOne to jump-start and sustain the data pipeline for critical projects. Use it to upload files to a staging area for RelativityOne or to download files fro...

The ability to customize the download URL would alleviate the problem of chasing mirrors/CDN redirects not listed in the PMPC firewall documentation. GIMP, with 14 US mirrors, is a perfect example and one that our Security team did not approve, re...

It would be nice if, when setting up an application with a custom command line or pre/post install scripts, we had an option to carry those settings over to the update packages as well. We have instances where we deployed an application with a ...

It would be useful to have an option for a progress bar that could be enabled (Cloud and or Publisher) for app installs/updates during the install. This would be something like a notification or progress bar to detail the status of the installation.

During the initial setup, a vendor name was added incorrectly. We need a way to remove any legacy entries in that field.

Instead of sending 1 email for all customers from Publisher to MSPs, allow the sending of 1 email per customer so that they can be shared with customers easier.