Appendix A: Filter Rule Conditions and Examples
Filters give administrators the added flexibility of conditionally applying configuration settings. Filters allow you to provision resources based on a variety of conditions such as user group or username. For example, you might want to map drives to users based on the department in which they work. ProfileUnity also allows users to create context-aware filters that provision resources based on the location of your user.
As mentioned in the Utilizing Filter Management section in this guide, filters can have multiple filter rules. These rules are made up of a Condition, Match, and Value triplet. The following table lists the conditions to choose from and some examples of how to use them.
Filter Rule Condition | Description |
---|---|
AD User Group Membership | Tests for user membership in specified user group. Example
|
AD User Primary Group | Tests a value against user’s assigned Primary Group. Example
|
Azure User Group Membership | Tests for user membership in specified user group. Example
|
Machine Group Membership | Tests for membership in the specified machine group. Example
|
Username | Tests a value against a user’s logon name. Example
|
IP Address | Tests a value against the IP address assigned to the client machine. If multiple IP addresses are assigned to the client, the first four IP addresses are tested. Example
Example
Example
|
Host Name | Tests value against the fully qualified TCP/IP hostname. Example
|
Computer Name | Tests a value against the NetBIOS computer name. Example
|
MAC Address | Tests a value against the address of the network adapter. Example
Example
|
Domain | Tests a value against the domain the client machine is a member of. Example
|
Logon Domain | Tests a value against the domain the user is logged on to. Example
|
Logon Server | Tests a value against the name of the logon server. Example
|
Site | Tests a value against the name of the Active Directory site the client machine resides in. Example
|
TS Client Name | Tests a value against the NetBIOS name of the client machine connecting to the terminal server. Example
|
TS Session Name | Tests a value against the session name assigned to the client machine connecting to the terminal server. Example
Example
Example
|
OU User | Tests a value against the name of the Active Directory OU the user's account resides in. Example
|
OU Computer | Tests a value against the name of the Active Directory OU the client machine resides in. Example
|
View Client Name | Tests a value against the name of the client machine connecting to the VMware Horizon session. Example
|
OS Architecture | Tests a value against OS Architecture. OS Architecture is 32 for 32-bit OS and 64 for 64-bit OS. Example
|
View Client IP | Tests a value against the IP address of the client machine connecting to the VMware Horizon session. Example
|
View Client MAC | Tests a value against the MAC address of the client machine connecting to the VMware Horizon session. Example
|
View Client Protocol | Tests a value against the display protocol used by the client machine connecting to the VMware Horizon session. Example
|
View Client Type | Tests a value against the client type of the machine connecting to the VMware Horizon session. Example
|
View User Domain | Tests a value against the domain name of the user connecting to the VMware Horizon session. Example
|
View User Name | Tests value against the username of the user connecting to the VMware Horizon session. Example
|
View Machine Domain | Tests value against the domain name of the machine connecting to the VMware Horizon session. Example
|
Environment Variable | Tests environment variables. This selection required multiple values. The | (pipe) character should be used as a separator. Example
|
Registry Value | Tests registry values. This selection required multiple values. The | (pipe) character should be used as a separator. Example
|
Registry Value Exists | Tests if registry value exists. Example
|
Registry Key Exists | Tests if a registry key exists. Example
|
File | Tests a file. This selection requires multiple values. The | (pipe) character should be used as a separator. Example
|
Directory | Tests the directory. This selection requires multiple values. The | (pipe) character should be used as a separator. Example
|
ICA Client Address | Tests the ICA client address. Example
|
ICA Client Name | Tests the ICA client name. Example
|
Service Exists | Tests if a service exists. Example
|
Service Running | Tests if a service is running. Example
|
Process Running | Tests if a process is running. Example
|
Day of Week / Time of Day | (For use with the English version of the Client only) Tests for a particular time block. Enter the Value as a “Day|Time” pair separated by a vertical line or pipe. Use short day names: Sun, Mon, Tue, Wed, Thu, Fri, or Sat. The time should be specified using a 24-hour clock with hours from 0 to 23. Example
|
LDAP Attribute | Tests for the value of an Active Directory attribute. Enter Value as an “Attribute|Value” pair separated by a vertical line or pipe. Example
|