There are two types of Custom Inventory rules:
• |
Conditional rules: These rules test whether conditions exist on devices. When a rule returns true, the KACE Agent reports the item as an Installed Program. When the rule returns false, the item does not appear as an Installed Program. |
• |
Value Return rules: These rules obtain data from devices. If the value exists, the KACE Agent reports the item as an Installed Program and sets a corresponding Custom Inventory Field. |
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
2. |
For example, the appliance first verifies whether an application is present on a device before deploying that application. In some instances, however, installed programs do not register in Add/Remove Programs or in standard areas of the registry. In such cases, the appliance might not be able to detect the presence of the application without additional information from the administrator. Therefore, the appliance might repeat the installation each time the device connects. Custom Inventory rules can prevent this repetition. |
4. |
5. |
To prevent the file from being copied to Replication Shares, select Don’t Replicate Associated File. This setting is useful for large files that you do not want users to install from Replication Shares, such as software suites. |
6. |
7. |
After the Agent reports the results, the device’s detail page shows the results under Software in Installed Programs and Custom Inventory Fields.
NOTE: The applications with Value Return rules that set a Custom Inventory Field also appear as Installed Programs. |
If results are not what you expect, verify that the device has been inventoried recently. The inventory time is shown in the Last Inventory field of the device detail page.
Use the correct syntax for function names and arguments in Custom Inventory rules.
Conditional and Value Return rules use the following syntax:
For specific information on functions and their arguments see:
Enter the functionName followed by an opening parenthesis, enclose the arguments with a closing parenthesis. No spaces are allowed between the name of the function and the opening parenthesis.
Enter argument syntax for all rules except command and regex (regular expression) as follows:
• |
For example, the following syntaxes are the same:
For example, if the user want to test against the registry value in which the value name is "test,value", the user would need to escape the comma in this case because registry value name is not the last argument in the Custom Inventory (CI) function.
• |
An unmatched literal open parenthesis needs to be escaped as {{op}}. When the parser is tokenizing the arguments for the function, it counts the number of open and close parentheses to determine the end of the function and argument. Therefore, an unmatched literal open parenthesis would throw off the count, and cause the argument value to be parsed incorrectly. If a literal open parenthesis is needed as part of the argument value, it should be represented with {{op}}. |
For example, if the user wants to echo the string "Hello ( World", then the CI should look like the following:
If a literal close parentheses is needed as part of the argument value, it must be represented with {{cp}}.
For example, if the user wants to echo the string "Hello ) World", then the CI should look like the following:
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center