Expression Dialog Boxes for Standard Rules
(Windows only)
These dialog boxes let you create or edit the standard rule expressions in an inventory rule. The type of expression that you add or edit determines the dialog box that appears.
Standard rule expressions are static, which means that they do not update based on the selections that you made when you created the rule. With a static rule, if there are changes to a software application, the rule does not update dynamically to reflect those changes.
You can use standard rule expression in a detection rule, which determines whether specific software is installed on a client computer. You can also use them in an applicability rule, which determines whether a client computer has the correct environment for installation of the software.
Each expression requires you to supply different information to define it.
Expression dialog box | Description |
|---|---|
64-bit Windows Installed | Checks the client computer to determine whether the computer is running the 64-bit version of Windows. You do not have to specify any information to set up this expression. |
File Version | Checks the client computer for the file version of the software program that you specify. Specify data for this expression as follows:
|
MSI Product Code | Checks the client computer for the MSI product code that you specify. The MSI product code is a unique identifier in the form of a GUID that represents a particular release of a software application. Enter the MSI product code for the software that you want to detect. |
MSI Upgrade Code | Checks the client computer for the MSI upgrade code that you specify to determine that no newer versions of a software application are installed. |
MSIX Package ID | Checks the client computer for the specified MSIX package ID. |
Multilingual User Interface Installed | Checks the client computer to determine if the computer uses a multilingual user interface. You do not have to specify any information to set up this expression. |
Processor Type | Checks the client computer for the processor type that you specify. You can choose from the following processor types:
|
Registry Key Exists | Checks the client computer for the registry key that you specify. You need to specify the path to the registry key. You can also specify the registry entry. The expression supports wildcards in the registry key. |
Registry Key To File Version | Checks the client computer for the specified version of the registry key and path. You can use operators. For example, you can use the less than operator to look for a version that is less than the specific version you choose. For example, to set up a rule that looks for version 5.5 of Exchange Server, specify the information as follows:
|
Registry Key Value | Checks the client computer for a registry value that you specify. You can search for the entire string of the value or a substring. Specify data for this expression as follows:
|
Registry Key Version | Checks the client computer for the registry key version that you specify. For example, to determine whether a certain version of Internet Explorer 6.0 SP2 is installed on a client computer, use the Registry Key Version expression.In that case, you would set up a detection rule that supplies the following information:
In some cases, you might want to look for more than one version for a single registry key version. In that case, create multiple Registry Key Version expressions—one for each version that can be found. For example, specify one expression with version 6.00.3663.0000 and one with version 6.00.2900.2180. |
Registry Key/File Path to File Version | Checks the client computer for the version number of a file. The expression uses a registry key path that you specify, along with the registry entry and file path to search for. For example, to check for Microsoft Access 9.0, specify the version information as follows:
|
Registry Key/File Path to Product Version | Checks the client computer for the product version number of an application. The expression finds the version number by using a registry key path, a registry entry, and a version that you specify. You can use operators with the version. For example, you can search for a specific version or for a version that is less than the version number you specify. |
Windows Language | Checks the client computer for the Windows language type that you specify. For example, you can set up a rule that checks whether the French version of Microsoft Office 97 is installed on a client computer. In that case, set up a detection rule that searches for Microsoft Office 97. Within the detection rule, specify a standard rule that specifies the French Language ID. To use the Windows Language expression, you need the Language ID of the language that you want to search for. |
Windows Version | Checks the client computer for a specified Windows version or a computer role. You can also specify Windows Server suite types to check for. When the rule checks for Windows Version or computer role, all the items you specify must be found. If all the items are not found, the rule does not evaluate as true. You can set up the rule to check for one or more of the following Windows Server suite types:
The Match all specified suite types option lets the rule evaluate as true only if all the selected suite types are found.To check for Windows versions and computer roles, select the Check Windows/version and/or machine role check box and enter data in the following fields:
|