Filters Filters consist of the following elements: a filter name, filter rules, machine classes, operating system types, and connection types. Filter Rules Filter rules are comprised of a condition, match, value triplet. A filter can have multiple filter rules. The logic used to evaluate multiple filter rules is based on the Rule Aggregate option. If the Rule Aggregate option is set to AND (All Rules), all rules must evaluate true for the filter to return true. If the Rule Aggregate option is set to OR (Any Rule), the filter will return true if any rule evalutes true. The Rule Aggregate option applies to all rules in a filter. It is not possible to specify AND logic for some rules and OR logic for other rules. Table 1 lists the possible conditions and provides example values. Condition Value Group Membership Tests for membership in specified group. Example: Value: Accounting Returns true for users that are members of the accounting group. Primary Group* Tests value against user's assigned Primary Group. Example: Match: Is (Exactly) Value: Domain Users Returns true for users with Domain Users assigned as the Primary Group. User Name Tests value against user's logon name. Example: Match: Is (Exactly) Value: GPBurdell Returns true if the user's logon name is GPBurdell. TCP/IP Address Tests 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: Match: Is (Exactly) Value: 192.168.1.1 Returns true if the client machine has IP Address 192.168.1.1. Example: Match: Begins With Value: 10.1 Returns true if the first two octets of the client IP Address is 10.1. Host Name Tests value against the fully qualified TCP/IP hostname. Example: Match: Is (Exactly) Value: atl-001.xyz.com Returns true if the client machine has atl-001.xyz.com assigned as the TCP/IP hostname. Computer Name Tests value against the NetBIOS computer name. Example: Match: Is (Exactly) Value: ATL-001 Returns true if the client machine is named ATL-001. MAC Address Tests value against the address of the network adapter. Example: Match: Is (Exactly) Value: 00306E053085 Returns true if the client's network adapter has address 00306E053085. Example: Match: Begins With Value: 00306E Returns true if the client's network adapter has an address that begins with 00306E. Since the first six digits of a MAC address identify the vendor, this filter would return true for network adapters manufactured by Hewlett Packard. Domain Tests value against the domain the client machine is a member of. On Windows 95, Windows 98, and Windows ME, tests value against the workgroup the client machine belongs to. Example: Match: Is (Exactly) Value: XYZ Returns true if the client machine is a member of the domain or workgroup XYZ. Logon Domain* Tests value against the domain the user is logged on to. Example: Match: Is (Exactly) Value: ABC Returns true if the user is logged on to domain ABC. Logon Server Tests value against the name of the logon server. Example: Match: Is (Exactly) Value: ADC01 Returns true if the server named ADC01 processed the user's logon. Site** Tests value against the name of the Active Directory site the client machine resides in. Example: Match: Is (Exactly) Value: Default-First-Site-Name Returns true if the client machine resides in site Default-First-Site-Name. TS Client Name Tests value against the NetBIOS name of the client machine connecting to the terminal server. Example: Match: Is (Exactly) Value: ATL-001 Returns true if the client machine connecting to the terminal server is named ATL-001. TS Session Name Tests value against the session name assigned to the client machine connecting to the terminal server. Example: Match: Is (Exactly) Value: RDP-Tcp#48 Returns true if the client machine connecting to the terminal server is assigned session name RDP-Tcp#48. Example: Match: Begins With Value: RDP Returns true for all client machines connecting to the terminal server via the RDP protocol. Example: Match: Begins With Value: ICA Returns true for all client machines connecting to the terminal server via the ICA protocol. Table 1: Filter Rules NOTE: Filter conditions denoted with a single asterisk can only be used on Windows 95, Windows 98, and Windows ME clients if the KXRPC Service is installed. Filter conditions denoted with a double asterisk require an Active Directory domain infrastructure and full Active Directory support on your clients. Full Active Directory support is included as part of the base operating system on Windows 2000, Windows XP, and Windows 2003. On Windows NT 4.0, Windows 95, Windows 98, and Windows ME, you will need to install the Active Directory Client Extension to have full Active Directory support. The Active Directory Client Extension, commonly referred to as the DSClient, is available from Microsoft. Machine Class Allows filters to include or exclude different machine classes. Available choices are Desktop/Laptop, Terminal Server, Member Server, and Domain Controller. The Desktop/Laptop machine class will return true for all client machines that are not Terminal Servers, Member Servers, or Domain Controllers. Operating System Allows filters to include or exclude different operating systems. Connection Allows filters to include or exclude different network connection types. Available choices are LAN and Dial-up. The logic used to determine the connection type is based on active Remote Access Service (RAS) connections. If the client machine has one or more active RAS connections, it is assumed the user is on a Dial-up connection.