Ideas

Endpoint Insights creates an application object of the matching recast agent version when it installs/updates. Now that the Recast Agent can be updated by Application Manager, it would be nice to have this behavior configurable, so you don't end u...

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

I would like to request an enhancement in Application Workspace to support all properties listed under User Information as variables, such as ${identity.company} and ${identity.jobtitle}. Currently, these properties are not available as variables,...

A report that could specifically query either the C:\windows\font directory for the files present or query the registry to capture all the values in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\ A report of this type would benefit anyon...

A report, dashboard or Power BI showing the Windows Update for Business (WUfB) Feature and Quality update deferrals policies set on workstations. Will be useful to ensure existing GPO or SCCM WUfB policies are being applied correctly and that Depl...

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...

Now when new applications are published to RAM supported application list, there is no information/impulse easily available for customers/technicians. Could there be action to notice customers when new applicatons are published? Automatic email de...

This is interesting for customers without Microsoft Endpoint Manager. So we can manage all things in liquit without domain gpo policies

Hello, We would like to submit a feature request regarding the Powershell module. At the moment it isn't possible to copy an actionset from one package to another. It is possible to copy a complete package with the "copy-liquitpackage" command but...

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.