jobTitle | mail | mobile | postalCode | street | telephone}] [-LiquitContext ] [-WhatIf] [-Confirm] [ ] Parameters Name Value Description Required Default value DisableFields {city | company | country | department | description | fax | jobTitle | mail | mobile | postalCode | street | telephone} Choose which attributes to be synchronized to Application Workspace . LiquitContext Determines the selected zone. No Default Set-LiquitIdentitySourceAccountLockoutPolicy Synopsis This cmdlet is applicable only for the Local identity source. Syntax Set-LiquitIdentitySourceAccountLockoutPolicy [-IdentitySource] [-Enabled ] [-ResetInterval ] [-Threshold ] [-Duration ] [-LiquitContext ] [-WhatIf] [-Confirm] [ ] Parameters Name Value Description Required Default value ResetInterval The period of time during which the [-Threshold ] must be reached before the lockout will be applied. Threshold How many invalid login attempts are allowed before the lockout will be applied. Duration The amount of time that an account is locked for. LiquitContext Determines the selected zone. No Default Set-LiquitIdentitySourcePasswordPolicy Synopsis This cmdlet is applicable only for the Local identity source. Syntax Set-LiquitIdentitySourcePasswordPolicy [-IdentitySource] [-Enabled ] [-MinimalLength ] [-MinimalLetters ] [-MinimalNumbers ] [-MinimalSpecialChars ] [-ValidationRegex ] [-LiquitContext

Creating a dynamic variable for a license key can help you save time instead of wasting it searching for a key each time you install an application. Then you use that variable inside an Install action as a placeholder for a dynamically value obtained by Application Workspace . In the example below we will create a dynamic variable for the license key of FolderSizes, a disk space analysis software. Go to Manage > Workspace > Licenses . Create a new license with the following parameters: Name FolderSizes License License count 2 License cost 20 License key 123-123-123-123 Go to Manage > Workspace > Variables . Create a new variable with the following parameters: Type Dynamic Name FolderSizes_License Entity type License Entity select the FolderSizes License created at step 2 Property License key Go to Manage > Workspace > Packages . Create a new package with the following parameters: Type Custom package Name File Size Reporting Leave

when requested. Mobile field not being included with an Azure AD identity source. When switching sessions within the Remote Control dialog causes JavaScript error. 3.4.1936 Changes Added SameSite attribute to session cookie(s). Added support for ADFS on a Azure AD identity source. Bugfixes Missing 'Create Server' permissions in default Administrator policy. Liquit Workspace Connector synchronized entitlements with Refresh event is created as Device Startup event. Agent reports user cancel event as 'Uninstall' when user cancels an installation action set. UI is not properly updated with the zone managed option in the Satellite Server. A warning is displayed in the server logs about failed to delete content file(s) in the SQL database. 3.4.1929 Bugfixes IP address field allows spaces in subnet filter, which causes filter to fail. Missing auto complete feature in add package wizard. Missing stage option in connector entitlement transformation/static rules. When

pre-Windows 10 devices. It displays a message about missing GetDpiForWindow. Slow authentication through an LDAP Identity Source within large environments. Action 'Delete Printer' does not work. Workspace Agent keeps user auto launch enabled after disabling. Incorrect size of multiple prompts when using different DPI settings in the Universal Agent. SetupStore connect doesn't show correct error message if there are connectivity issues. Citrix integration doesn't close the Liquit Browser popup after completion (Also it requires the latest version of the Citrix StoreFront integration script). 4.0.3175 Bugfixes Double clicking on a resource in the connector resource overview does not show the creation wizard. Condition set stage is wrongly translated in the Workspace connector. 4.0.3174 Bugfixes Some documentation links are blocked by the Content Security Policy. Configured connector publishing stage is not used when creating a new resource. Unable to select Install dependency in the Microsoft

As the name suggests, User mail does not filter devices, but rather users based on their e-mail address. General Type ​​ User mail Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with Value The value matched against Agent It is available on devices with or without an Agent running. You can view the e-mail address of a user: on the local device in User Menu > User Portal > Diagnostics > User Supported platforms Platform Supported Web Yes Windows Yes macOS Yes

The Open URL action allows you to open an URL (optionally in a specific browser). General Type Open URL Name Actions are easier to comprehend and manage over time when they have a suitable name that accurately expresses what they do. URL www.example.com Advanced Browser Specify which browser should open the web page. The following options are available: Default - the URL will be opened by the browser configured as default on devices. Internet Explorer Firefox Chrome Opera Microsoft Edge Safari Recast Software - the URL will be opened using the Recast Software browser. When you select a specific browser to open the URL with and that browser is not available on the device, the URL will be opened in the default browser. Hidden If this option is selected, then a background web request is made and no browser will be opened. This option is available only for Recast Software

This task wakes all devices that are members of a specific device collection. For more information about the Overview , Notifications , Schedule and History screens, see Scheduled Tasks .

The detection methods enable the administrator to verify if an application is already installed. Additionally, it can prevent an application installation if it overlaps with another application that is already installed. During the Application Deployment Evaluation , the System Center Configuration Manager client can detect the installation of an application using these methods even if they did not use the Software Center or the Application Catalog to install it. In case of applications using a ‘Windows Installer (Native) – ‘MSI’ Deployment type, the MSI Product Code GUID is used for the detection method to detect whether an application has been installed. This GUID is added automatically as a detection rule when you use an MSI to create an app, both in Setup Commander as well as in the System Center Configuration Manager. In case of applications using a ‘Script Installer (Native)’ – Script Deployment type, non-MSI setups also called legacy setups, there

Manage the content in the Content Store , that can be used as icons or as uploaded content associated with actions. Get-LiquitContent Synopsis This command downloads a file or folder from the Content Store . Syntax Get-LiquitContent [-ID] [-LiquitContext ] [ ] Get-LiquitContent [-EntityRef] [-LiquitContext ] [ ] Example Get-LiquitContent -id 00000000-0000-0000-0000-000000000000 Parameters Name Value Description Required Default value ID The ID of the content that needs to be downloaded. Yes EntityRef Represents the item it is assigned to. e.g. if the content is for a package, then this is the reference of the package. No LiquitContext Determines the selected zone. No Default New-LiquitContent Synopsis This command uploads a file or folder to the Content Store . Syntax New-LiquitContent [-Path] [-FileName ] [-Resize] [-LiquitContext ] [-WhatIf] [-Confirm] [ ] Examples Example 1: Upload folder New-LiquitContent -Path "C:\test\" This command uploads all files and folders located in C:\test\ to the

Use the Agent available filter to check whether or not an Agent is available on devices. This can be useful in a situation where a web action only needs to be executed when an Agent is running. General Type Agent available Enabled Yes the Agent is available. No the Agent is not available. Agent It is available on devices with or without an Agent running. Supported platforms Platform Supported Web Yes Windows Yes macOS Yes

4.3.XXXX Change The /legacyDownload option is no longer present in the bootstrapper. Thus, Liquit Workspace Agent will no longer be downloaded. 4.2.3547 Change Liquit Workspace Agent 3.x moves to extended support​ This is the latest version where the Liquit Workspace Agent (XML-based) is supported.​ The bootstrapper is still able to download the (XML-based) Liquit Workspace Agent but this is the last version. 3.9.2684 Change Liquit Agent Bootstrapper is out of preview. 2.1.0.2 Bugfix Bootstrapper doesn't parse arguments correctly. 2.1.0.1 (Preview, Windows only) Bugfix Bootstrapper doesn't require the C++ Runtime libraries anymore on Windows. 2.1.0.0 (Preview) Changes Added bootstrapper support for macOS. Added support for '--' instead of '/' for specifying commands on macOS. Added support for an external argument file named 'arguments.txt' on macOS. Added '/certificateIssuer=' command to support the new

It is currently not possible to install Bartender under device context. If you install it under device context, because some files are missing, the application will not start. This is due to the way Application Workspace installs Bartender. Currently, the only way is to install it is under user context. The only downside is that the user gets a UAC prompt.

If you want to create an application for Cisco Jabber there are some extra steps you have to take. Prerequisites To download the MSI installer, you must Log In to your Cisco account and have a valid service contract associated with your Cisco.com profile. Download the MSI installer from the Cisco Sofware Download webpage . Application Workspace Setup Store Configuration Wizard We’ve included a configuration wizard which prompts you for several additional options: Further reading Cisco Jabber Unified Communications webpage

Tags allow you to organise a set of packages or certificates. In order for a tag to be displayed on the user's device, you must first assign to that user the packages assigned to the tag. Moreover, based on the way you set up a package, the tag is displayed in Workspace tab, Catalog tab or both. To view which tags does an app belong to, go to Manage > Workspace > Packages > open the app you need and go to Catalog > Tags . Tags table There are two types of tags: Workspace : This tag is visible within the users Workspace . Management : This tag is only visible within the management interface for administrators. The Built-in column denotes that the tag comes from self-signed, server, client or chain type certificates. It cannot be modified. The Managed column denotes that the tag comes from a connector, configured as a synchronized connector that

In case you encounter any errors while creating a Windows package, check File System permissions for the selected share and then choose one of the suggestions below, and try again. add ‘LOCAL’ to the ACL of the share you’ve selected this file from and use ‘Read’ for the Permission Level add ‘NETWORK SERVICE’ to the ACL of the share source of this file and use ‘Read’ for the Permission Level use a ‘Custom account’ for the LDAppApi Application Pool, one which has sufficient access rights for the selected share: More details about this error are available in this logfile: C:\Program Files\LANDesk\ManagementSuite\log\DistributionApi.dll.log

The Set registry value action allows you to set a registry value on devices. General Type Set registry value Name Actions are easier to comprehend and manage over time when they have a suitable name that accurately expresses what they do. Key For example HKLM\My\Registry\Key . Name The name of the registry key. Type The type of the registry value: SZ, DWORD, QWORD, MULTI_SZ, EXPAND_SZ, BINARY Value The value of the registry key. Advanced Context The level at which the action is executed User , Device or Elevated user . For elevated user, the action will be executed under the current user, but it's granted temporary permission to modify the local system. Use 32bit registry key on 64 bit systems If selected, Application Workspace first checks 32-bit registry locations for the specified registry key. If the registry key isn't found, it searches 64-bit locations

...

Connectors Microsoft Configuration Manager Microsoft Configuration Manager 2012R2 and higher are supported. Microsoft Deployment Toolkit Microsoft Deployment Toolkit (MDT) 2012, 2013 and higher are supported. Microsoft MDT has a few requirement: For all deployment situations, the Windows ADK for Windows 10, version 1809 or later, is necessary. Ypu cannot create a deployment share without it. User-driven installation (UDI) and zero-touch installation (ZTI) scenarios require Configuration Manager version 1810 or later. Ivanti Endpoint Manager Ivanti Endpoint Manager 2017.3 Service Update 3 and higher are supported. Micro Focus ZENworks Configuration Management ZENworks 11.4.x and higher are supported. Operating System Setup Commander is supported on the following Windows operating systems: Microsoft Windows 10 x86 or x64 Microsoft Windows 11 x86 or x64 Microsoft Windows Server 2008 (R2) Microsoft Windows Server 2012 Microsoft Windows Server 2016 Microsoft Windows Server 2019 Microsoft Windows Server 2022 You need Administrative privileges to

Application Workspace certificate and IdP configuration Create a Self signed certificate First, we need a self-signed certificate to sign the SAML 2.0 message that the Application Workspace identity provider will issue. Navigate to Manage > System > Certificate and click Create in the table toolbar. In the Create certificate dialog box: In Type , select Self signed and click Next . In Overview , enter a description like “Certificate used for signing SAML messages” and click Next . In Self signed , for the Common name field, the domain name does not need to be a valid one. A common name like "liquit-idp" should be sufficient in most situations. In the Days valid and Key size fields leave the default values. Create a SAML 2.0 identity provider Now we can create a new identity provider: Navigate to Manage > Authentication > Identity Providers and click Create in the table toolbar. In the Create identity provider

Setting up the Microsoft Teams integration This flow is supported in Application Workspace 4.3 and higher. You need to enable token exchange on your identity source in order to have the Application Workspace for Microsoft Teams application autheticate your users. To start rolling out Application Workspace for Microsoft Teams you need an Microsoft Entra ID (Azure AD) identity source set up. For the instructions on how to set up the Microsoft Entra ID (Azure AD) identity source, see Microsoft Entra ID . Initiating the wizard Open the Microsoft Entra ID (Azure AD) identity source and navigate to the Microsoft Teams tab. Click Setup the Microsoft Teams app to initiate the wizard. A new popup opens, prompting you to sign in to Azure Portal (if you are not already signed in). The account you use to sign in should be able to provide administrative consent on Azure App registrations. If the