Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? Don't worry, no email address or name fields are shared on the public portal. You can create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.

13 Vote

Missing Requires UAC in PowerShell Scripts

When selecting to allow powershell scripts to run from a specific location for SCCM, there is no option to check Requires UAC like in EVERY OTHER piece of software. All scripts from SCCM run from the same location and some need to be run under the user context, but Privilege Management is elevating those scripts. Please add this ASAP

  • Guest
  • Mar 13 2020
  • Future consideration
  • Attach files
  • Guest commented
    29 Mar 10:03am

    Many Windows application types support embedding UAC elevation data into a manifest file, which is interpreted by the operating system.

    Whilst the PowerShell process itself can be supported, unfortunately PowerShell scripts do not support UAC natively, nor can they be targeted to 'Run as Administrator' via a shortcut's advanced properties. As such there is not a scenario where this criteria is relevant to PowerShell scripts themselves.

    Currently the templated support for SCCM automatically targets PowerShell scripts for elevation, but customers are free to amend this behavior for all PowerShell scripts or to exclude certain scripts such that they do not run elevated.