A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
This issue happens upon the creation of manual supersedence rules on some of the apps that we publish within ConfigMgr, but when we do the update in place on each new release, it sets their supersedence rule to inactive.
Actually, PmPC always deploys the latest version, and we don’t have the option to stay on an older version or to, for example, always deploy the N-2 version to avoid compatibility issues. This is especially important for engineering or development...
Add Version of an app but have option to keep old version deployed
When using the cloud custom app and we want to add a new version, we would like to be able to keep the previous version until the new version has been tested. As of now we have to create a new app and deployment and it is a pain to change the name...
rigth now pmpc has : requires 32bit os requirement, only install on server, only install on worksations.would be awesome to see more like: only install on "dell" workstations, only install on "laptops", only install if device has wifi, only instal...
Have an option in Settings - Notifications to centrally manage the new app notifications to ensure it's consistent and if you need to make changes to all the apps at once
Allow configuration of "Device restart behavior" in the App deployment Wizard
Currently, reboot behavior follows the application’s exit codes after installation. If you need to enforce a mandatory reboot, Intune provides an option called 'Intune will force a mandatory device restart', which is not currently available in the...
sometime there a specific settings configured on a app for different reasons and shouldn't be changed without further discussions... sometimes it just to pause a update for x days... or disable update completely from being published... with a righ...