These conditions use client and session attributes to target actions. These conditions look for a match within the logged on user’s session or client. For example, a client Screen Resolution condition could be configured so that a particular application can only be used on all clients with a screen resolution of 1024x768 and above.
|Condition||Description||Computer Trigger||User Trigger|
|Published Application Name||A condition based on the use of a particular published application.||No||Yes|
|Client Connection Protocol||A condition based on whether the user connection is by console, Independent Computing Architecture (ICA), Remote Desktop Protocol (RDP) or PC over IP (PCoIP).||No||Yes|
|Client IP Address||A
condition defined by the endpoint’s IP address entered into the
IP Address 1 field. A range of IP addresses can be defined using
the Between radio button and IP Address 2 field.
For ranges, the IP address is not treated as a whole number but based upon the value of each octet. For example, if the range was from 184.108.40.206 to 220.127.116.11, 18.104.22.168 would pass but 22.214.171.124 would not as the third octet is not within the set range.
|Client NETBIOS Name||A condition for the connecting device identified by its NETBIOS name.||No||Yes|
|Client Screen Resolution||A condition based on the screen resolution of the connecting device. A specific resolution or a range can be used to define when an action applies. This condition is available for Remote Desktop Protocol (RDP) and Independent Computing Architecture (IDP) clients only. It will not work on the console.||No||Yes|
|Client Color Screen Depth||A condition based on the color screen depth of the connecting device. Use the slider and radio buttons to select the required value or range of values. This condition is available for Remote Desktop Protocol (RDP) and Independent Computing Architecture (IDP) clients only. It will not work on the console.||No||Yes|
|Client Computer Domain||A condition for a defined network of client computers. Use the Name Resolution Type drop-down to specify whether the condition uses the DNS Domain or Windows Domain naming conventions. The domain entered in the Match field must be in the format used in your organization for the selected naming convention. For example, a DNS domain name could be testing.xyz.local whereas the Windows domain name would just be testing.||No||Yes|
|Client Computer Group||A condition based on an Active Directory client computer group.||No||Yes|
|Citrix Client Settings||A
condition based on attributes of the connecting client.
The Client OS condition is not compatible with the Network Disconnected trigger.
The Client Version condition uses the version number used in the marketplace, rather than the build version number. For example, Citrix Receiver 126.96.36.199 relates to build version number 188.8.131.52461.
The Client Encryption attribute condition is not compatible with Citrix XenDesktop.
The NetScaler Session Policies and NetScaler Hostname conditions are not compatible with Citrix XenApp.
The Client Version, Client Encryption, NetScaler Session Policies and NetScaler Hostname conditions require the following to be installed:
The Citrix PowerShell Broker Snap-in on the client. This snap-in can be installed on the client by running Broker_PowerShellSnapIn_x86.msi or Broker_PowerShellSnapIn_x64.msi from the Citrix installation media.
For Citrix XenApp, PowerShell 3.0 or later on the server.
For Citrix XenDesktop, PowerShell 3.0 or later on the Virtual Desktop Agent client.
For further information see Add a Citrix_ Client Settings Condition.
|Citrix vDisk Client Settings||A condition to determine whether a Citrix vDisk is in use and, if so, whether it is running in Standard or Private mode.||No||Yes|
|VMware Variables||A condition based on attributes of the broker or connecting client. This condition is available on all User triggers, except Pre-Session and Pre-Desktop triggers.||No||Yes|
- In the Policy Configuration navigation tree, create a new node or select an existing node under the Logon Pre-Desktop sub-trigger.
Click Conditions > Session & Client > Citrix Client Settings.
The Citrix Client Settings dialog displays. If required, enter a description and any additional information relating to the Citrix Client Setting in the fields provided on the General tab.
- Select the Client Settings tab.
Select the Citrix Client Settings condition criteria from the following:
Attributes Description Clients OS Match the client’s operating system, such as Android, iOS, Mac or Windows. Client Type Match the type of client, such as a phone, tablet or other device Client Version Match the version number of the Citrix Receiver client. This uses the build version number, rather than the version number used in the marketplace. For example, Citrix Receiver 184.108.40.206 relates to build version number 220.127.116.11461. To view the build version number, see the About box within the Citrix Receiver. Client Encryption Match the client encryption type from Basic, Logon Only, RC5 (40 bit), RC5 (56 bit) and RC5 (128 bit).
The encryption levels available for XenApp and XenDesktop are Basic and RC5 (128 bit) only.
NetScaler Session Policies Match NetScaler session policies. Separate multiple policies with commas NetScaler Hostname Match the hostname of the NetScaler.
The Citrix PowerShell Broker Snap-in is required for the Client Version, Client Encryption, NetScaler Session Policies and NetScaler Hostname conditions. This snap-in can be installed on the client by running Broker_PowerShellSnapIn_x86.msi or Broker_PowerShellSnapIn_x64.msi from the Citrix installation media.
- Click OK.
Was this article useful?
Copyright © 2019, Ivanti. All rights reserved.