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

If you want to deploy AutoCAD 2018, there are two ways to do this. Silent installation via deployment If you want to deploy all components of the install at once, you first have to make a deployment install. Start the setup and follow these steps to create an administrative image. Then you can install AutoCAD with using the following commandline: .ImgSetup.exe /W /q /I ImgAutoCAD2018.ini /language en-us Silent installation of all prerequisites If you want to install all the prerequisites and components separately, you have to install the following components: .NET Framework Runtime 4.6 Img\3rdParty\dotNetFramework\46\dotNetFx46_Full_x86_x64.exe /q /norestart Microsoft Visual C++ 2008 SP1 Redistributable (x86) Img\3rdParty\x86\VCRedist\2008SP1\vcredist_x86.exe /q Microsoft Visual C++ 2008 SP1 Redistributable (x64) Img\3rdParty\x64\VCRedist\2008SP1\vcredist_x64.exe /q Microsoft Visual C++ 2010 SP1 Redistributable (x86) Img\3rdParty

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 .

If you want to create an application for PDFCreator, you can download it in the Setup Store. If you install PDFCreator, you automatically also get PDF Architect. If you don’t want to install Architect, use the following command-line parameters. For more information on the switches for PDFCreator, see the PDFCreator user guide . Silent installation Starting version 3.2.1, silent installations are supported only as part of the business editions "PDFCreator Business", "PDFCreator Terminal Server" and "PDFCreator Custom". So if your system is Domain joined, you won't be able to install PDFCreator Free. See the corresponding release notes on the pdfforge website .

Use the Agent type filter to create a rule based on the type of the Agent running on devices. General Type Agent type Compare Equal, Not equal Agent type Universal Agent Windows Agent - also know as Workspace Agent Agent It requires the Agent to be running. Supported platforms Platform Supported Web No Windows Yes macOS Yes

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

Get-LiquitTask Synopsis This command displays all the tasks defined in the zone or server. Alternatively, you can use this command to select a specific task. Syntax Get-LiquitTask [[-ID] ] [-Search ] [-Name ] [-State {Queued | InProgress | Success | Failed | Cancelled | Suspended | Continue}] [-LiquitContext ] [ ] Get-LiquitTask [-Server] [[-ID] ] [-Search ] [-Name ] [-State {Queued | InProgress | Success | Failed | Cancelled | Suspended | Continue}] [-LiquitContext ] [ ] Get-LiquitTask [-ScheduledTask] [[-ID] ] [-Search ] [-Name ] [-State {Queued | InProgress | Success | Failed | Cancelled | Suspended | Continue}] [-LiquitContext ] [ ] Examples Get-LiquitTask Example 1 $taskList = Get-LiquitTask -State Failed This command generates a list of all the failed tasks in the current system. Get-LiquitTask Example 2 $server = Get-LiquitServer -id 00000000-0000-0000-0000-00000000 Get-LiquitTask -Server $server This command retrieves all the tasks running on the specified server. You cannot get a list of tasks running on a satellite server by this method. Parameters Name Value Description Required Default value ID The GUID belonging to

Below is a complete list of all possible settings and their description. Name Type Description UI equivalent agent.cache.autoclean If enabled, the stale content from the local cache of devices is automatically deleted if one of the following conditions are met: the content is superseded by a new version. the content is no longer entitled to a user and the period of time set in the agent.cache.expirecontent has passed. Agent settings > Cache > Clear cache automatically agent.cache.enabled When an identity is entitled to a package, the package is automatically downloaded and cached on the end-user device. It will remain there even after the session ends, as long as the end-user is entitled to it. When the entitlement is removed, the cache is cleaned depending on how agent.cache.autoclean and agent.cache.expirecontent are configured. Agent settings > Cache > Enable caching agent.cache.expirecontent The

As the name suggests, User job does not filter devices, but rather users based on their job title. General Type User job 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 job title of a user: on the local device in User Menu > User Portal > Diagnostics > User 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

Use Network ping to filter based on the reachability of a hostname or network address on an Internet Protocol network. General Type Network ping Host For example server.domain.net Reachable Yes, No Advanced Context The level at which the action is executed, User or Device Ping timeout Timeout a ping request in milliseconds; increasing the timeout can negatively impact the refresh time when the host is unreachable Ping attempts Number of ping attempts before considering the host unreachable; increasing the attempts can negatively impact the refresh time when the host is unreachable Agent It requires the Agent to be running. Supported platforms Platform Supported Web No Windows Yes macOS Yes

This example shows how to configure an Application Workspace connector using the LOCAL identity source. In the source Application Workspace zone, create a new user in the LOCAL identity source called Test . Assign a Connector type access policy to the newly created Test user. Entitle the Test user to all the packages that you want to export later. You can do that in Manage > Users > Test user > Packages screen or in Manage > Workspace > Packages > desired package > Entitlements screen. In the destination Application Workspace zone, create an Application Workspace type connector with the following parameters: In the Overview tab: Direction Pull Synchronization method Synchronize Stage Development Package name prefix RecastSoftware In the Settings tab: URL the URL of the source Application Workspace zone, Username insert "LOCAL\Test" (the username of the user configured at steps 1-2) Password insert the password of the Test user (the user configured at steps 1

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

Backup The following (data) directories are required for a successful backup of an Application Workspace Server : Name Default Path Configuration C:\Program Files (x86)\Liquit Workspace\Server\Server.json Content Store C:\ProgramData\Liquit Workspace\Server\Content Agent configurations C:\ProgramData\Liquit Workspace\Server\Agents We recommend you backup the Application Workspace database before backing up the servers, because the Content Store on disk and in the database are interconnected. Restore Restoring the database Shut down all Application Workspace Server s. Restore the Application Workspace database. Start all Application Workspace Server s. Run Verify content on every server within the Application Workspace System . Restoring a server Restore all data directories specified in the Backup section of this article. Run Verify content on the restored server within the Application Workspace System .

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