• 06 May 2024
  • 11 Minutes to read
  • Dark
  • PDF


  • Dark
  • PDF

Article summary



  • PowerShell cmdlet "New-LiquitZone" fails with error: "Property named 'primary' cannot be set on creation".
  • Production package action sets can be dragged.
  • Registry filters value types of binary and multi sz are handled incorrectly.
  • Filter icon on action is reset after copy.
  • Splunk client certificate is not always used.
  • Broken link for documentation on the Event Collectors.
  • Unable to see error details on the System Update task.
  • Microsoft System Center Configuration Manager connector produces error message: "The call is ambiguous between the following methods or properties".
  • Universal Agent content is cleaned up too aggressively.



  • Universal Agent (Windows) fails to install if started with non-administrator privileges.



  • Webserver doesn't recognize TLS offloading.



  • Webserver doesn’t correctly redirect requests in all cases.
  • Update SixLabors.ImageSharp library within the Liquit UserHost to resolve CVE-2024-27929.
  • Action "Stop-Process" doesn't work when device context is used.
  • Issues while switching between online and offline mode in the Universal Agent.
  • "UserHost not found" message while using a portal or browser without a logged in UserHost.
  • Universal Agent doesn’t function on some languages (Thai).
  • "_" and "~" characters produce incorrect search results within the workspace.
  • Invalid option to redirect output on script and process actions when display is set to normal.
  • Synchronization connector can create packages with missing or dummy values when synchronization profile settings are set to "Set from connector during creation".



  • Small server performance improvements.


  • When an Event Collector (Splunk and Sentinel) fails, it doesn't retry to send the failed events.
  • Previously configured certificate in a Splunk Event Collector cannot be viewed or removed.
  • Package filter “Mac App installed version” fails if the app is not installed.



  • Added support for Windows 11 23H2.


  • Options of the tray icon are missing after Agent switches to the offline mode.
  • Possible to have both the launcher and login window active when a relog is triggered.
  • Member list for contexts, dynamic user and device collections does not include collections.
  • Additional networks do not include non-routable addresses used by some VPN products.
  • An error occurs when importing a registry file that contains delete actions for non-existent registry values.



  • Websockets are disabled on the server side.
  • Improved handling of ACME busy errors.
  • Allow for a small clock skew for certificate-based registration.
  • Small server performance improvements.


  • Changes to a filter on a deployment action aren't directly available for Agents.
  • Deployments ending with filtered actions after the last reboot action aren't creating server events.
  • The satellite server shows content unavailable in the content overview.
  • The result of the "User Prompt" action can't be saved to a variable.
  • Variable names are not validated in the output option on multiple actions.
  • The "Install server update" scheduled task always sends a notification.
  • Missing primary property on the zone in PowerShell zone cmdlet.



  • The generated zip file with the "Install uploaded directory" action will be based on the directory name.


  • Unable to upload content with the Universal Agent when the location is on a user network share.
  • macOS applications with symbolic links can break code signature with the "Install Mac App" and "Install uploaded Mac App" actions.
  • ShellAPI cannot launch workspace item with only package ID when the primary shortcut is disabled.
  • User collections are not usable for the user membership filter on contexts.
  • Microsoft Store connector does not detect updates on synchronized packages.



  • AVD connector incorrectly detects RDPW certificate changes.



  • Improved performance when large numbers of user and or device collections are used.


  • Uploaded RDP file and Remote RDP actions can generate "Invalid connection file" message.
  • Permalink for the credential store pages can direct to the user credentials.
  • Deployments that end with a reboot action do not generate a successful event.



  • The progress bar of a Liquit Task in PowerShell is not disposed of after the task finishes.
  • AVD connector requires credentials while not needed with SSO.
  • Agent refresh could result in “Value cannot be null. Parameter name: ipString” message on the server.
  • Updating an existing IPP printer on Windows can cause a UserHost crash.
  • VMware connector stops synchronizing when an application has no icon.
  • The filter defined in the User Portal is incorrectly used in Offline mode.
  • Unable to modify a custom URL for the SIEM Azure Sentinel connector after creation.
  • Universal Agent can take a long time to display the workspace icons.
  • The server can have degraded performance and logs “There were not enough free threads in the ThreadPool to complete the operation.”.



  • Replaced the icon that indicates an inactive filter on an action/action set.


  • Uploaded icons with the Universal Agent can become corrupted.
  • HSTS headers are only sent for REST requests.
  • Icons in the previously specified start menu folder are not removed.
  • Universal Agent can be missing the username of stored credentials.
  • Connection between the UserHost and the Universal Agent is not always recovered.
  • Possible high CPU usage on the server since 4.1.
  • Static device collections not visible on devices.
  • Universal Agent doesn't wait for first refresh for non-primary workspaces and may generate error: “No workspace item found”.



  • An application shortcut generated by the ShellAPI, when it is pinned to the icon, it can be that of another application.
  • A package with a refresh workspace action can trigger a loop if it is also entitled to a refresh trigger event.
  • Entitlement synchronization options are available for some connectors which do not support synchronization.
  • IPv6 filter can generate errors.
  • Userhost can be closed even when the close option is set to false.
  • Event Collectors stop working when an identity can’t be resolved.
  • The userhost can generate the error: 'No package item found with workspace Id {workspaceID} or name {PackageName}'.
  • Rename 'Azure Active Directory' to 'Microsoft Entra ID' in the server installer.
  • The install package action can generate a critical error when using non-Latin characters.
  • Nullreferenceexception can occur when the agent is refreshed.



  • Old system updates are not cleaned up.
  • No additional networks are shown for devices.
  • Setup Store packages can trigger “Trying to modify Entity object which is in read-only state” error.
  • An incorrect error message can be shown during a “process start” action.
  • Set-LiquitIdentitySource PowerShell cmdlet can trigger a “Object reference not set to an instance of an object” error.
  • LiquitIdentitySource cmdlets are case sensitive for type.
  • IPv6 subnet masks are incorrectly displayed.
  • Agent actions can fail for some non-Latin languages.


Universal Agent enhancements

Automatically clean stale cached content

The stale content from the local cache of devices is automatically deleted:

  • all content superseded by a new version is deleted immediately.
  • all content that is inactive for a certain period is automatically deleted at the end of the period (expireContent) configured in the .JSON file. By default, this value is set to 90 days.

For more information, see Agent Configuration.

Performance improvements

  • In case of offline Agent UI updates, the content is retrieved from the Content Store of CDN or Liquit Workspace Satellite Server, instead of the Liquit Workspace Server. It reduces the number of HTTP requests to the Liquit Workspace Server. Note that CDN / satellite servers are not configured by default.
  • In case of packages marked offline, only the active snapshots of all stages will be cached, instead of all snapshots. The reason behind it is to offload content downloads from the Liquit Workspace Server.

Events data upload to server

In the Portal > Agent settings a new section was added to control if the data generated after the agent triggers an event is stored to server and at what time interval. For more information, see Agent configuration and Agent settings.

Certificate enrollment method for device registration

A new method for registering devices to a Liquit zone was added: certificate enrollment. This method employs the PKI system and is helpful for large enterprises since it is more secure than the certificate method and allows you to issue individual certificates for each device, for example.
For more information, see Device Registration.

Liquit Workspace

Event collection (SIEM)

You can now send out events information to Splunk and Microsoft Sentinel external SIEM systems.
For more information about how to configure this integration, see Event Collectors.

Scheduled tasks

A new type of scheduled task called Install server update was introduced in Managed > Automation > Scheduled tasks. You can use it to automatically update all satellite servers within your zone.


Uninstall MSI action via Product code

A new option to uninstall an MSI file was added, namely via its unique product code.
There is no need to upload the file to the client computers, you can fill in the product code manually or extract it from MSI file present on your local device. Directly extracting the product code from an MSI is available only for Windows OS. For more information, see Uninstall MSI.
Support was also added for the MSI summary data in UserHost GetMetadata.


  • Now it is easy to spot if an action or action set inside a package has filters set. For an action the pictogram is placed at the beginning of the row, for a set of actions the pictogram is at the top right corner of the table. If it is greyed that means filters are not set.
  • In the packages list grid two new columns were added, Tag and Category which are displayed by default.
  • A new package filter was added, Browser Exists. It checks if a certain web browser is installed on devices.
  • Disabled shortcuts are now indicated as such in the action dialog, making it easier to identify the correct shortcut.

Other filters enhancements

Subnet filter supports IPv6
Besides IPv4, the Subnet filter now supports also IPv6. We introduced the concept of additional networks because currently there is only one network Liquit can detect. For example, if a VPN was needed in an environment, Liquit would not detect it.
The additional networks are displayed under User Portal > Diagnostics > Device > Network. You can use these additional addresses in the Subnet filter.
For more information, see Subnet.

Platform version filter by editions
More granular filtering options are now available for the Platform version filter.
In case of a Windows type platform you can now filter by edition: Home, Pro, Enterprise, Windows Multi-version, Windows for IoT.
As for Windows Server you can now filter by the version of the server, Server Core or Full Server.
For more information, see Platform version.

Support for PowerShell 7 and later
Run script and Run uploaded script type of actions now support two types of PowerShell engines:

  • Windows Powershell - it is the old option, renamed and it is for Windows only
  • PowerShell (Core) - for the new edition of PowerShell that is cross-platform (Windows, macOS)

For more information, see Run script and Run uploaded script.

Mac App installed version filter by short version
A new checkbox called Use short version was added to the Mac App installed version filter. If this checkbox is selected, the filter will check the short version string rather than the long version string in the .plist file. This option is useful when the file contains errors like missing long version or the short version is different than the long one.

Events displayed for deployments

A new screen named Events was added to deployments, which displays all events that are associated with the respective deployment.

Microsoft Entra ID (Azure AD) identity source

  • The name of Azure Active Directory (Azure AD) identity source was changed to Microsoft Entra ID. For more information see Microsoft documentation.
  • The Microsoft Entra ID (Azure AD) identity source now requires the Application ID URI from your Azure Portal for the Token Exchange authentication method.

User Collections

The User Collection functionality was added, to assist you in organizing users within a network based on your own criteria and to configure and deliver packages simultaneously for multiple users at once.

Portal Settings

The Download Agent for Windows > Windows Agent (Obsolete) option will be unavailable for selection starting this release and will be removed in a future release.


This configuration utility which is shipped with the Liquit Workspace Server product, can be used to register the local device as a new server within an existing Liquit Workspace database and to change the Server.json file. For more information about every action, see Serverutil.

Liquit Workspace PowerShell Module

  • The Get-LiquitDevice cmdlet also displays the last logged in user.
  • Multiple new cmdlets were added for creating, removing, configuring identity sources. For more information, see Identity Sources.


Drag and drop files in Workspace

Automatically create links to a local file, folder or application by dragging and dropping them in Liquit Workspace. No matter where you drop them, the links are created in the Workspace tab.

Support for screen readers in compliance with WCAG 2.1 AA

Users can now use screen readers to convert webpage text to audio (navigation elements, application names, menu items etc.).

Workspace UI consistency improvement

For consistency purpose, the Platform field in User Portal > Diagnostics > Device displays the OS and its version.

Longer license keys

The License key field in Manage > Workspace > Licenses now allows longer strings.

Entity IDs displayed in entities lists

A new column called ID has been added to all the entities lists across Liquit Workspace, for a better traceability of entities.

Was this article helpful?

What's Next