Common Management Validation Logic type
Common Management Validation Logic type
The following Validation Logic Types are available for use with Computer Management and User Management Profiles and Profile objects. Some Validation Logic Types allow the use of the * and ? wildcards.
The asterisk (*) wildcard means that at least one occurrence of the specified characters must exist in the entry field. When a profile or profile object element is being validated based on an entry field using the *, validation will return true and valid if the specified characters prior to the asterisk exist anywhere in the text field.
For example, if the specified Active Directory group is [ AC* ], then any group that begins with AC, followed by any other characters will be valid for the validation.
The question mark (?) wildcard is used often used as a placeholder for unknown data. One or more ? may be used in a text field in conjunction with other characters. If the pattern of characters matches the field being validated, where a ? represents any other character, the validation will return true and valid.
For example, if a Computer Name is specified in the validation entry field as [ SHP??01 ], then any computer with a name that starts with SHP and is then followed by any two characters plus 01. A computer name SHPAB10 would match and validate true for this example.
Network Membership
Computer Domain
|
|
Note: Validation Logic type allows use of wildcards. |
Select Computer Domain to execute a configuration element for all computers that belong to the specified Domain. Find the Computer Domain Validation Logic type under the Network Membership category. In the Select Domain box, enter the name of the Domain. Optionally press the Browse button to locate the Domain. The supplied Computer Domain value is compared against the domain the client machine is a part of during the logon process and must match for the configuration element to be processed.
Examples:
|
BENE |
Validates true for all computers in the BENE domain |
|
BE* |
Validates true for all computers in any domain beginning with the letters BE |
Computer Group
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select Computer Group to execute a configuration element when the client computer is part of the specified Active Directory Group. Find the Computer Group Validation Logic type under the Network Membership category. In the Select Group box, enter the name of the Computer Group or press the Browse button to locate it. If the computer logging on is part of the supplied group, the configuration element and/or profile will be processed.
If Include child groups is selected, the configuration element will also execute when the client computer is in a group that is a member of the specified Active Directory Group. The domain must be configured with Windows 2008, Windows 2008 R2, Windows 2012, Windows 2012 R2, or Windows 2016 domain functional level.
Examples:
|
AdminGrp |
Validates true for all computers in the AdminGrp. |
|
OntarioGrp\* |
Validates true for any computer in the OntarioGrp including any nested groups of the OntarioGrp |
OU (Computer)
|
|
Note: Validation Logic type allows use of wildcards |
Select Organizational Unit (Computer) to execute a configuration element for all computers belonging to a specific OU. Find the OU (Computer) Validation Logic type under the Network Membership category. In the Select Organizational Unit box, enter the name of the OU or press the OU Browser button to locate it. The supplied OU value is compared against the OU the client machine is a part of during the logon process and must match for the configuration element to be processed.
Select the box Include child OUs to include all nested OUs of the selected parent in the validation logic rule.
Examples:
|
\Florida\Boca\Accounting |
Validates true for any computer belonging to the \Florida\Boca\Accounting OU. Child OU's will be included if the "Include child OUs" box is selected. |
|
OntarioGrp\* |
Validates true for any computer in the OntarioGrp including any nested OUs of the OntarioGrp |
|
\Florida\Boca\Tech* |
Validates true for any computers in any OU that begins with the letters Tech and also belong to the \Florida\Boca\ OU. |
Site
|
|
Note: Validation Logic type allows use of wildcards |
Select Site to execute a configuration element for all computers that belong to the specified Site. Find the Site Validation Logic type under the Network Membership category. In the Select Site box, enter the name of the Site. The supplied Site value is compared against the site the client machine is a part of during the logon process and must match for the configuration element to be processed.
Examples:
|
BENE |
Validates true for any computer belonging to the BENE site. |
|
BE* |
Validates true for any computer in a site that begins with the letters BE. |
|
ST??-01 |
Validates true for any computers in a site that begins with ST followed by any two characters and then a -01. |
Computer Information
Computer Name
|
|
Note: Validation Logic type allows use of wildcards |
Select Computer Name in order to execute a configuration element for a specific computer. Find the Computer Name Validation Logic type under the Computer Information category. In the Select Computer box, enter the Computer Name or press the Browse button to locate the computer name. The supplied Computer Name is compared against the Computer Name of the client during the logon process and must match for the configuration element to be processed.
Examples:
|
PC221 |
Validates true for the desktop computer named PC221. |
|
*LAPTOP* |
Validates true for any desktop computer with LAPTOP in its name. |
|
*221 |
Validates true for any desktop computer ending with 221 in its name. |
|
PC* |
Validates true for any desktop computer starting with PC as its name. |
|
PC2?? |
Validates true for any desktop computer starting with PC2 in its name and is followed by two additional characters. |
|
A??-PCxxx-ACCTG |
Validates true for any desktop computer belonging to the ACCTG department, in building A, on any floor (??). This particular example denotes the granularity possible when used in conjunction with the corporate computer naming standards. |
Host Address
|
|
Note: Validation Logic type allows use of wildcards |
Select Host Address in order to execute a configuration element for the specific name. Find the Host Address Validation Logic type under the Computer Information category. In the Value box, enter the Host Address. The supplied Host Address is compared against the Host Address of the client during the logon process and must match for the configuration element to be processed.
The Host Address can identify a specific Host Address or a set of Host Addresses using wildcards.
For example, if a portion of the Host Address was used to distinguish between different office buildings, a wildcard can be used when validating the Host Address to deploy printers based upon in which building the computer is located.
Examples:
|
loc031-pc221.bldga.acme.com |
Validates true for the specific computer whose Host Address is loc031-pc221.bldga.acme.com. |
|
loc031-pc221.bldga.* |
Validates true for the computer in building A, whose Host Address begins with loc031-pc221.bldga. |
|
*.bldga.* |
Validates true for any computers that are in Building A. |
|
*.bldga.acme.com* |
Validates true for any computers that are in Building A and part of the Domain Amoco |
MAC Address
|
|
Note: Validation Logic type allows use of wildcards |
Select MAC Address in order to execute a configuration element for a computer with a specific MAC Address. Find the MAC Address Validation Logic type under the Computer Information category. In the Value box, enter the MAC Address. The supplied MAC Address is compared against the MAC Address of the client during the logon process and must match for the configuration element to be processed.
This type of validation gives the ability to specify a specific computer on the network based on the MAC Address built in to the network adapter. This gives a simple way to address a specific machine regardless of the computer name (which is vulnerable to change). Validating on a MAC Address may also be useful if your network uses IPX/SPX as a protocol.
To determine the MAC Address for a computer's network adapter, run IPCONFIG /ALL. The MAC Address will be defined as the Physical Address for the network adapter.
Examples:
| Mac Address | VL Mac Address Value |
|---|---|
|
00-50-56-C0-00-10 |
005056C00010 (no hyphens) |
|
00-50-56-*-*-* |
Will validate for all MAC addresses that begin with 00-50-56 |
TCP/IP Address
|
|
Note: Validation Logic type allows use of wildcards |
Select TCP/IP Address in order to execute a configuration element for the specific machine based on the TCP/IP address. Find the TCP/IP Address Validation Logic type under the Computer Information category. In the Value box, enter the TCP/IP address. The supplied TCP/IP address is compared against the TCP/IP address of the computer during the logon process and must match for the configuration element to be processed. The TCP/IP Address validation type will accept IPv4 and IPv6 addresses.
The asterisk (*) and question mark (?) wildcards may be used to match TCP/IP addresses. This wildcard technique and simplified string manipulation should be effective on most networks. Keep in mind that you are not required to specify complete octets. Specifying 192.168.1* would attempt to match the first two octets completely and the first character of the third octet to the client's TCP/IP address.
Examples:
|
192.168.100.5 |
Validates true for the computer whose TCP/IP address is 192.168.100.5. |
|
192.168.100.* |
Validates true for any computers whose TCP/IP address matches the first three octets. |
|
192.168.* |
Validates true for any computers whose TCP/IP address matches the first two octets. |
|
192.168.1??.5 |
Validates true for any computers whose TCP/IP address matches 192.168.1xx.5, where xx is any number. |
|
10::1 |
Validates true for the computer whose TCP/IP address is 10:0:0:0:0:0:0:1 |
True subnetting is supported in the TCP/IP Address value field. Use true subnetting values to selectively specify certain groups of IP addresses. Specify the IP address and subnet mask in the TCP/IP value entry. The subnet mask can be specified in either dotted decimal format or by specifying the number of mask bits.
Examples:
|
10.0.0.4/255.255.255.0 |
Validates true for the computers whose IP address is in the range or 10.0.0.1 - 10.0.0.254. |
|
10.0.0.4/24 |
Validates true for the computers whose IP address is in the range or 10.0.0.1 - 10.0.0.254. |
|
10.0.0.4/255.255.255.240 |
Validates true for the computers whose IP address is in the range or 10.0.0.1 - 10.0.0.14. |
|
10.0.1.4/28 |
Validates true for the computers whose IP address is in the range or 10.0.1.1 - 10.0.1.14. |
|
10.0.0.39/28 |
Validates true for the computers whose IP address is in the range or 10.0.0.33. |
To determine the IP Address for a computer, run IPCONFIG.
File Exists
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select File Exists in order to execute a configuration element for a computer that has the existence of a specific file. Find the File Exists Validation Logic type under the Computer Information category.
In the Value box, enter the file name (including path) of the file to be checked. If the file exists in the path specified the configuration element will be processed.
File Version
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select File Version in order to execute a configuration element for a computer that has a specific file and version of that file (regardless of the user that logs on to the computer). Find the File Version Validation Logic type under the Computer Information category. The file's version information is normally embedded into the file and can be seen on the Version tab of the Properties for the file.
The File Version validation type requires three validation values to complete its configuration. The required values are File, Operator and Version. Enter the name of the file (including path) whose version will be compared against into the File box. Enter the comparison operator into the Operator box. Enter the comparison operator to be used in the compare operation. Enter the comparison value into the Version box.
The available compare operators for the Operator field are < (less than), <= (less than or equal to), <> (not equal to), = (equal to), > (greater than), >= (greater than or equal to).
The file's version is extracted and then compared against the information specified by the operator and comparison version. If the comparison (performed during the logon process) returns a TRUE result the configuration element will be processed.
Example:
|
File: |
C:\Program Files\Microsoft Office\Office10\Winword.exe |
|---|---|
|
Operator: |
<= |
|
Version: |
10.0 |
If the version of the Winword.exe file is less than or equal to 10.0, the configuration element will be processed.
IPv4 Range
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select IPv4 Range in order to execute a configuration element for any computer with an IP address within the range specified. Find the IP Range Validation Logic type under the Computer Information category. In the Range boxes, enter the beginning and ending IP addresses. The supplied range of IP addresses is compared against the IP address of the computer during the logon process and must match for the configuration element to be processed.
Examples:
|
192.168.100.5 - 192.168.100.50 |
Validates true for the computer whose IP address is between 192.168.100.5 and 192.168.100.50, inclusive. |
To determine the IP Address for a computer, run IPCONFIG.
IPv6 Range
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select IPv6 Range in order to execute a configuration element for any computer with an IP address within the range specified. Find the IP Range Validation Logic type under the Computer Information category. In the Range boxes, enter the beginning and ending IP addresses. The supplied range of IP addresses is compared against the IP address of the computer during the logon process and must match for the configuration element to be processed.
Examples:
|
10::1 - 10::10 |
Validates true for the computer whose IP address is between 10:0:0:0:0:0:0:1 and 10:0:0:0:0:0:0:10, inclusive. |
To determine the IP Address for a computer, run IPCONFIG.
Registry Key Exists
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select Registry Key Exists in order to execute a configuration element for the specific computer if the specified Registry Key is found in the registry. Find the Registry Key Exists Validation Logic type under the Computer Information category.
In the Key box, enter the Registry Key name. If the Registry key exists, the configuration element will be processed.
Registry Value Exists
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select Registry Value Exists in order to execute a configuration element for the specific computer if the specified Registry Key and Value is found in the registry. Find the Registry Value Exists Validation Logic type under the Computer Information category.
In the Key box, enter the Registry Key name. Enter the registry key value in the Value entry. If the Registry key and value combination exists the configuration element will be processed.
Registry Value
|
|
Note: Validation Logic type does not allow the use of wildcards |
Select Registry Value in order to execute a configuration element for a computer with a specific registry value. Find the Registry Value Validation Logic type under the Computer Information category.
The Registry Value validation type requires four validation values to complete its configuration. The required values are Key, Value, Operator and Data. Enter the registry hive and key to be checked into the Key box. Enter the name of the entry within the specified key to be checked into the Value box. Enter the operator to be used in the compare operation. Enter the data to be compared against into the Data box.
The available compare operators for the Operator field are < (less than), <= (less than or equal to), <> (not equal to), = (equal to), > (greater than), >= (greater than or equal to).
The supplied validation values (Value, Operator and Data) are used to form a condition that is applied to the specified Key. If the comparison (performed during the logon process) returns a TRUE result the configuration element will be processed.
Example:
|
Key: |
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectX |
|
Value: |
Version |
|
Operator: |
< |
|
Data: |
9.0 |
If the installed version of DirectX is less than 9.0, the configuration element will be processed.
Virtual Environment
Select Virtual Environment in order to execute a configuration element on a client running a virtual environment. VMWare virtual machines are currently supported.
Select the VMWare virtual machine check box to execute a configuration element on a VMWare virtual environment.
Platform Type
Select Platform Type in order to execute a configuration element on a machine running a specific Operating System platform, x32 or x64 operating system. If the computer is running an operating system platform that matches one of the platforms selected, the configuration element will be processed.
Windows 10 Release ID
Select Windows 10 Release ID in order to execute a configuration element when a computer has or doesn’t have a specific Release of Windows 10 installed..
In the Windows 10 Release ID column, select one or more Release Id's. If a Release ID is not specified, enter it into the Others box. Multiple Release ID's can be entered into the Others box delimited by commas.