I’d like to suggest adding a bulk re-import capability to Recast Patching. Our use case involves common files that are referenced by the pre-install actions of multiple applications. Occasionally, we need to update these files. Currently, updating...

As an admin of Recast, I would like the ability to control who can see the Patching module within the Recast Management Server. There currently is no way to prevent those who have access to RMS to not see Patching. Also more granular control aroun...

We deploy applications to user collections. However, since users can log in to both fat clients and terminal systems, the applications should only be installed on fat clients. Until now, we have manually added a custom requirement rule after creat...

Vaison Printer Installer Client software cannot do an in-place upgrade. To install the new version you have to first uninstall the existing version then install the new version. This means the AW managed package "Printer Installer Client" cannot b...

As a customer, I want to compare my application inventory against the Recast Application Catalog so that I can immediately understand which applications are recognized, which are unsupported, and where catalog coverage gaps exist. This visibility ...

Assigning permissions in the console is a complete mess, we need to be able to assign permissions just based on the right click context menu, so we only enable and disable the needed permissions without just guessing what we need.

Having the ability to run actions via LAPS vs the logged in user of the console would be a huge win for orgs that split admin privs on accounts and/or restrict admin rights on workstations.

Allow users to override the ability to use the user account of the user logged into the SCCM console when retrieving LAPS passwords instead of the proxy user account when the proxy is set to a higher priority in the routes. I like the fact that I ...

When setting up custom roles in Recast Management Server, it would be helpful to be able to have a button to clone/copy to create clones of existing roles. This would save time on not having to manually check all the specific boxes of permissions ...

Remove the version number from the name of applications. Applications like the Omnissa Horizon Client include the version number. Meaning that because the title is unique to a specific version of the application, the deployment of that application...