Automation

I would to suggest to add a 'Product Code' text field between 'File' and 'Arguments'. This gives the option to bypass selecting an MSI, when the Product Code is already known. And also clarifies that using the 'File' select option (...) is just an...

Currently Liquit PowerShell .NET library is based on .NET Framework but doesn't support .NET CORE environments. This limits the ability for customers to manage Liquit in cloud environments that support .NET CORE only.

For every deployment I prefer to save logging in the C:\Windows\Temp directory. We should be able to call variables so that the log file naming is dynamic such as adding the install string /l*v C:\Windows\Temp\%APPNAME%-%VERSION%.log and having th...

As a system administrator, I want to be able to limit the systems on which to deploy applications, such as 32-bit or 64-bit systems, or different operating systems, such as Windows 10, 11, servers, or workstations. Also ability to require older ve...

Would it be possible when running a "Add Computers to Collection" function to add the ability to schedule the time when devices are added, and once added run a Machine Policy Retrieval and Evaluation Cycle. This would allow for techs to have a set...

Dynamic Groups in EntraID (AzureAD) are severely limited in what can be targeted. ConfigMgr has a great feature that can create "dynamic" EntraID groups based off of ConfigMgr data. For customers who are Intune only, it would be great if there was...

Reports get us to the data we need, would be great to build collection off that query automatically to take action. For example i filtered down to Adobe version 9.0 and want to upgrade these systems to 11. Collection with members from report auto ...

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

Allow customers to configure dependency chain in custom applications, and add other customs apps as dependencies