page. Does the custom logout report status back - If enabled, the logout page will wait for the status report. Otherwise, the logout page assumes a successful logout after a few seconds. Does the custom logout use a secure connection - If enabled, the logout URL and redirects on the service provider are considered secure. A secure connection is important especially in scenarios where embedded content is supported by specific browsers. Metadata tab The URL and XML fields in this tab cannot be edited here, they just display the existing information. To import metadata from URL, XML or a local file you must first click Update from metadata and the following dialog will be displayed: Here you can choose to enter the URL where the IdP SAML configuration is stored, copy the content of the metadata XML or import the metadata XML from a local folder on your computer. After you click

This is the default Application Workspace starting point. Here you will find all applications, files and other IT resources made available to you by the system administrator. In Workspace you can: Start managed applications configured by your system administrator. Add your own personal apps. Filter through apps based on easy to access filters, tags and teams. Share personal apps, websites and other resources with your coworkers. Define which applications should be started automatically. View reviews of applications and websites written by your coworkers. Report potential issues with an application directly to your IT Department. Side Menu overview Filters These are predefined filters designed to help you find applications easily. When selecting a filter in the Side Menu , only applications assigned to that filter will be shown. Name Applications filtered All All applications New apps Only applications you have not yet started Favorite apps Only applications you have favorited Personal apps

This feature is available only for the Universal Agent . Agent settings can be configured globally here, and exceptions can be set at the context level. This allows for easy management of the agent’s behaviour after it has been deployed on devices. If settings are configured to Local agent configuration they will adhere to the settings defined in the agent.json. See Agent Configuration for all options in the agent.json file. You need to refresh the Agent , to apply the changes made in the Agents Settings screen. Workspace Agent To configure the Workspace Agent on a Windows machine, see Agent Configuration . Application Workspace Launcher section Modify the behaviour of the Application Workspace Launcher . Option Description agent.json setting Enable Liquit Launcher If Application Workspace Launcher should be enabled launcher\enabled Open Liquit Launcher at startup Defines when Application Workspace Launcher is started: Enabled - Start when device is connected to

This connector type allows you to set up a connection to Microsoft Azure Virtual Desktop (ARM or legacy) to import the applications defined there as ready-to-use applications within Application Workspace for distribution. Prerequisites A Microsoft Entra ID (Azure AD) username and password to connect to Microsoft AVD. A template type credential within the Recast Software Credential Store that can provide the username for the Remote Desktop application. A common format for the username is "${Identity.UserName}". If your service account is MFA-enabled, you need to use either the Conditional Access or Trusted IP feature in Microsoft 365 to bypass MFA. Once you have configured one of these features, proceed to configure the service account on the connector. For more information about the Overview , Entitlements , Synchronization Profile , Releases and Managed packages screens, see Connectors . Settings screen Scope - The type of resources that will be synchronized. Username - The

Variables give you the tools to be as dynamic as possible, and can be used within actions and filters. Variables can currently be defined on 3 different levels; Variables (Zone) Contexts Packages (Snapshots) The inheritance flows top-down and variables can be overwritten. This means a variable defined at the zone level can be overwritten in contexts and/or packages. This allows you to change the value of variables based on the context(s) of a user or device. The syntax of a variable is ${ } System Variables The following system variables are predefined in Application Workspace and are detected by the Agent . Some of them are only available starting a specific version of the Agent and it is specified where applicable. Note that the paths used as examples in the table below, might not match your Application Workspace System . Variable Operating system Output (Example) ${AllUsersProfile} only Windows C

Deployments are used to sequence a set of application installations during the imaging process of both virtual and physical devices. For more information about starting or enabling deployments, see Agent Configuration for the Liquit Workspace Agent and Agent Configuration for the Application Workspace Agent . Notes After a deployment runs, it is disabled and the Agent configuration file is reverted to the previous state. The launcher is not available while deploying. Deployments list This list displays all deployments currently available in the Application Workspace System . Selecting multiple rows from the table To select multiple adjacent rows, click on the first row, then hold down the Shift key and click on the last row in the range; all rows between will be selected. To select multiple non-adjacent rows, hold down the Ctrl key (or "Command" on Mac) and click on each row you want to select individually. To select multiple adjacent

This version is no longer supported, please upgrade to the latest version Support lifecycle for the Liquit Workspace product is available here . 3.9.3507 Bugfixes Permalink to Credential Store is broken. Production package action sets can be dragged. Microsoft System Center Configuration Manager connector produces error message: "The call is ambiguous between the following methods or properties". 3.9.3349 Bugfixes The filter defined in the User Portal is incorrectly used in Offline mode. 3.9.3251 Bugfixes Okta connector can be created as push connector which isn’t supported. Action sets order can be changed when applying update from Liquit Setup Store. 3.9.3112 Bugfixes Workspace connector can give a permission denied error. 3.9.3069 Changes Add support for Private Network Access RFC for browsers. Bugfixes System Updates sometimes incorrectly reports that no update is queued for a server. Number of purchased licenses are now always

As the name suggests, User company does not filter devices, but rather users based on their company. General Type User company 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 company 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 Wait action allows you to set a delay before proceeding with the next action/action set. General Type Wait Name Actions are easier to comprehend and manage over time when they have a suitable name that accurately expresses what they do. Seconds The number of seconds Application Workspace should wait. Filters Here you can define conditions which determine if the action will be executed. For more information, see Filters . Agent It requires the Agent to be running. Supported platforms General Web No Windows Yes MacOS Yes

After extracting the setup files from the download ‘Inv_View_2018_language_Win_platform_bit.zip zipfile, you will find a setup.exe in the root directory. This is a ‘ bootstrapper ‘ which installs these Visual C++ prerequisites: Microsoft Visual C++ 2008 Redistributable – x86 Microsoft Visual C++ 2008 Redistributable – x64 (64-bit systems only) Microsoft Visual C++ 2010 x64 Redistributable (64-bit systems only) Microsoft Visual C++ 2010 x86 Redistributable Microsoft Visual C++ 2012 Redistributable (x64) (64-bit systems only) Microsoft Visual C++ 2012 Redistributable (x86) Microsoft Visual C++ 2015 Redistributable (x64) (64-bit systems only) Microsoft Visual C++ 2015 Redistributable (x86) And then runs .. x64\inventorview\InventorView.msi (64-bit systems) or ..x86\InventorView\InventorView.msi (32-bit systems). Therefore this .MSI file (Installation Package) is selected automatically when you download and process ‘Autodesk Inventor View 2018’ from within the ‘Setup Store’. Doing so, you can use the configuration wizard

The Access Manager license is required for this connector. This connector type allows you to setup a connection to Okta to import the applications defined there as ready to use applications within Application Workspace for distribution. Prerequisites The domain name of the Okta tenant you wish to use. An application token from Okta to use for identification. To generate the Okta token, follow the instructions provided by the okta Developer guides . If the connector is not used for some time, the token can be invalidated by Okta. For more information about the Overview , Entitlements , Synchronization Profile , Releases and Managed packages screens, see Overview . Settings screen Okta Domain - The domain name of the Okta tenant, for example liquit.okta.com . Token - The token that will be used to authenticate to Okta.

Use Variable value to filter based on the value of a certain variable within the Application Workspace System . General Type Variable value Name The name of the variable, without "${}" Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with, Greater than, Less than Value The value of the Recast Software variable Agent It is available on devices with or without an Agent running. Supported platforms Platform Supported Web Yes Windows Yes macOS Yes

Get-LiquitZone Synopsis This command displays a list of all the zones available within Application Workspace . Alternatively, you can select a specific zone. Note that this command displays also the license usage information. Syntax Get-LiquitZone [-LiquitContext ] [ ] Get-LiquitZone [-ID] [-LiquitContext ] [ ] Get-LiquitZone [-EntityRef] [-LiquitContext ] [ ] Get-LiquitZone [-Search] [-LiquitContext ] [ ] Get-LiquitZone [-Name] [-LiquitContext ] [ ] Get-LiquitZone [-Primary] [-LiquitContext ] [ ] Examples Example 1: Get-LiquitZone Get-LiquitZone This command displays all the zones defined within Application Workspace . Example 2: Get-LiquitZone Get-LiquitZone -ID 00000000-0000-0000-0000-000000000000 This command displays the selected zone. Parameters Name Value Description Required Default value Search This parameter serves a similar purpose to the search box found in the zones table from the Application Workspace UI. It enables users to search multiple columns within the table, such as Name and Virtual host. When a search term is provided, the parameter filters records by matching values in

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

We recommend installing multiple servers within a single Application Workspace System as this creates redundancy so that there is no down time for web services when a single server fails or during updating the system. Recast Software installations are licensed per zone . This means that additional servers within a single Application Workspace System can be installed without the need for an extra license. To add additional servers to an existing Application Workspace System , all you need to do is install a new Application Workspace Server and point the database information during the setup to an existing database. The Application Workspace Server installation will skip the zone creation step and will instead install as an extra server. Do not copy an existing server.json from another server, as this file includes information that defines the trust information between the database and the server instance. Add the required changes to a server

If you want to install the Oracle BI Publisher Desktop, there are some extra steps you have to take. You can download BIPublisherDesktop64.exe or BIPublisherDesktop32.exe from the Oracle website . This setup contains an MSI which you have to extract manually. How to manually extract the MSI Run the downloaded executable for 64 or 32-bit. When the InstallShield Wizard pops up, you must look for the extracted MSI. Search in your C:\Users\[username]\AppData\Local\Temp\ for “Oracle BI Publisher Desktop.msi”. You will find it in a temp directory with a name like: {5DF6BC0C-C343-4C9B-B917-DD25767B272B}. Note that the name differs every time you start the setup. Copy the MSI to your desired location on your computer or network. Cancel the InstallShield Wizard. Setup Commander and Setup Store wizard Now you can use the extracted MSI in Setup Commander. Right-click on the MSI

entitlements for all connectors. Some connectors support importing entitlements from the remote system. This screen is available only when the connector is created using the synchronized method. Import entitlements section With the import entitlements functionality enabled, you are able to add matching policies to match an identity (user, group, device or device collection) configured in the remote system with an identity known within Liquit. Add matching policy dialog box Overview tab Identity Source - The Application Workspace identity source to match users and groups from the remote system. Applies To - Which Application Workspace identity types (user, group, context, device, device collection) inside the selected identity source should be matched. Property - The property of the Application Workspace identity to use when matching with the remote system. Value transformation tab Compare - What operator needs to be used on the property selected in the Overview tab. Match - The regex used to match part or

InstallShield setups can use a Silent response file for installations. While a standard installation requires user input through dialogues, a silent installation retrieves this input from an InstallShield Silent response file (.iss file) without prompting the user. This kind of InstallShield setup supports a recording mechanism, using the “/r” switch. Doing a manual installation (preferably on a clean VM in which the prerequisites are installed), will create a c:\windows\setup.iss file. After copying this file into the same directory as the setup.exe file, you can run the setup again (on a clean VM) using the “/s” switch. This will read the setup.iss file read the selections you’ve made in the recording phase and then run a silent installation. You can find more information about how to Create the response file in the InstallShield 2014 Help Library.

As the name suggests, User city does not filter devices, but rather users based on their city. General Type User city Compare Equal, Not equal, Contains, Doesn't contain, Starts with, Ends with Value For example: New York Agent It is available on devices with or without an Agent running. You can view the city 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 Prompt user action allows you to display a message or question to users. General Type Prompt user Name Actions are easier to comprehend and manage over time when they have a suitable name that accurately expresses what they do. Message Type the message or question you want to display. Icon Select the pictogram to be displayed in the message dialog box: Default Information Question Warning Error Buttons OK OK / Cancel Yes / No Advanced Cancel/No Action Choose what happens when the user clicks No , Cancel or closes the message dialog box: Error - display an error message. Skip action set - skip the current action set to which this Prompt user action belongs. Skip action sets - skip all action sets of the same type as the one to which this Prompt user action belongs. Skip package - stop processing the current package without an error. Wait for input If this option is