Custom Properties Settings

The Custom Properties Settings defines scripts that can be launched during a session to determine additional properties of the local agent or remote device before the context is first evaluated.

1. Local Agent Custom Properties
2. Remote Windows Device Custom Properties
3. Remote Linux, IGEL or NoTouch Device Custom Properties
4. Creating Custom Properties

Local Agent Custom Properties

When defined for the local agent, scripts are launched on Logon, Reconnect (or Unlock), and Service Start.

The following controls are available for the Local Agent:

• Embedded Script - Defines the script that will be evaluated on the local agent.
• Embedded Script Language - Set to either PowerShell, VBScript or Batch, and defines the scripting language used by the embedded script.
• Delay execution until properties are available - When checked, will execute the script after the all properties have been determined. The properties are available either from the Windows Registry, or as environment variables within the script.
• Hash returned property values - When checked, any returned custom properties are converted to a SHA256 hash.
• Persist custom properties across reconnects - When checked, the script is only evaluated on Logon and Service Start. Any custom properties that are created remain unchanged if a user Reconnects to a virtual session. When unchecked, any custom properties are discarded when the session is disconnected and the script is relaunched on a Reconnect.
• Override PowerShell execution policy - When checked, any PowerShell scripts are launched with an execution policy set to Unrestricted.
• Bypass Microsoft AppLocker policy - When checked, any PowerShell based Microsoft AppLocker rules are bypassed by the executed script.
• Run as System - When checked, the script is launched as the System user. When unchecked, the script is launched as the user logging into the session.
• Wait for the process to terminate up to timeout - Defines a timeout period after which the Logon or Reconnect process will no longer be held up if the script has not completed.

Remote Windows Device Custom Properties

When defined for the Remote Windows Device, scripts are launched on connecting Windows devices at the start of the virtual session.

The following controls are available for the Remote Windows Device:

• Embedded Script - Defines the script that will be evaluated on the remote Windows device.
• Embedded Script Language - Set to either PowerShell, VBScript or Batch, and defines the scripting language used by the embedded script.
• Hash returned property values - When checked, any returned custom properties are converted to a SHA256 hash.
• Override PowerShell execution policy - When checked, any PowerShell scripts are launched with an execution policy set to Unrestricted.
• Wait for the process to terminate up to timeout - Defines a timeout period after which the process will no longer be held up if the script has not completed.

Remote Linux, IGEL or NoTouch Device Custom Properties

When defined for the Remote Linux, IGEL or NoTouch Device, scripts are launched on connecting Linux based devices at the start of the virtual session.

The following controls are available:

• Embedded Script - Defines the script that will be evaluated on the remote device.
• Hash returned property values - When checked, any returned custom properties are converted to a SHA256 hash.
• Wait for the process to terminate up to timeout - Defines a timeout period after which the process will no longer be held up if the script has not completed.

Creating Custom Properties

Custom Properties scripts can create a custom property by writing either LOCAL_CUSTOM_<NAME>=<VALUE>, or REMOTE_CUSTOM_<NAME>=<VALUE> to the output. On Windows, this can be achieved by calling Write-Host in PowerShell, WScript.Echo in VBScript or echo within a Batch script. On Linux based clients, this can be achieved in bash using echo.

Custom Properties scripts can stay resident in memory for the lifetime of the session, perhaps by entering a loop or by registering for events. Custom properties can be created in the usual way, or deleted by outputing DELETE LOCAL_CUSTOM_<NAME> or DELETE REMOTE_CUSTOM_<NAME>. After all properties are emitted to the output, a single line stating CONTINUE should be written to the output.

The Wait for the process to terminate up to timeout option should be unchecked for resident scripts. Any custom properties scripts that are still executing will be terminated when it is no longer needed.