All ideas

Allow output from a PowerShell step to be used as input in future steps. This could just be a single variable, or customizable list (similar to input param for script blocks). This would allow for a lot more customization in builder actions.

Allow to configure implicit uninstallation settings (MS docs) for any deployment targeting to MECM collection

A great feature would be to add in Event Viewer to the Console tools to view the remote computers event logs.

To RCT teams reading this forum, I would like to request following enhancement : as done for managing client(s) or collection(s) actions, a nice idea would be to add or enhance your software, from any deployement's contextual menus, with a shortcu...

We have actions for repair and uninstall client, install client would be useful to have as well. Even though ConfigMgr has a built in client install right click action, it uses the client push account which has inherent insecurities. A right click...

Imagine this: Software has been manually installed or deployed to multiple machines, but you may not know how many machines have application x installed. You now need to uninstall this title, but you don't want to connect to each Remote Software C...

As more people are using passwordless and/or long passwords, when using the run as domain users, writing the password is a bit legacy. Could we use Windows Hello for Business credentials to confirm the elevation without using a password?

Add search feature to Agents TAB on the mgmt server to be able to go directly to an agent/device. Also, add the ability to check box more than one agent at a time. This will be handy when cleaning up retired devices that will no longer report in. ...

Patching for third party apps would be a nice to have. It would elminate the need for patch my pc or manage engine.

Stay connected with first responders and neighboring jurisdictions with one integrated dispatch and mapping system.