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:
Allow process conflict defer options to be set differently for Dynamic Assignments
I would like to be able to change the process conflict defer options for CVE or Critical Severity updates. Normally I don't mind users taking upto 5 days or 5 defer attempts (as an example) for a normal software update. However if that software up...
Intune-Option to use code signing cert to sign unsigned installers
In some cases, enterprises might use Airlock or similar solutions to block unsigned installers from running.In those cases, the hash of the installer will always have to be whitelisted manually each time there is a new update for that software. wi...
Similar to how variable support was added for post\pre-(un)install Please add these variables to custom command line as well For example, we have several apps and would like more control over the install location. Especially for supporting multipl...
Export / import function to "copy" update settings to another PMP site
Working with several PMP sites, it would be nice with a function to export / import an update configuration from one site to another. The function must include all settings incl. custom settings / files / etc.... It could be an API The goal is to ...
Remove prompt for UAC when opening Patch My PC Publisher
The Publisher's UI prompts for UAC because Settings.xml is needed for read/write in Program Files. Moving this to another location eg ProgramData would enable teams without local administrator rights on servers to manage our software.
Add visibility of which Pre/Post Scripts have been set in InTune Apps and InTune Updates
Currently the only way of knowing which scripts are being used in the pre and post installation steps is to view the client-side logs. It would be useful to include an indication of the script name and location that has been set.
Acrobat Reader detection should check both x86 and x64
Adobe is switching Reader to 64-bit. Reader 32-bit should consider itself installed if 64-bit is already installed. We shouldn't need to rely on CM collection queries.