Description
- Detection processing
- Detect and evaluate (evaluation schedule will not take effect)
Once done with the detection, the Collector will immediately evaluate the detected data. This means, that the Collector will save any changes to the Objects tree and to the Installations register. This option is selected by default. Evaluation schedule will note take effect in this case.
- Detect and schedule evaluation
The Collector will perform detections and will not evaluate the detected data. It will only schedule their evaluation. If you use several Collector instance in your computer network, you can have some instances detect computers only and for example one instance evaluate the detections. This will speed up data collection (and delay the evaluation thereof). If you want to use scheduling, we recommend that you use this option.
- Use the PING command to determine if a computer is switched on
-
- before detection with the "Agent over TCP/IP" method
This option enables the validation of whether or not a computer is present in the network using the PING command for detections with Agent over TCP/IP.
- before detection with the "without Agent" method
This option enables the validation of whether or not a computer is present in the network using the PING command for detections without Agent.
These options are enabled by default. We recommend disabling them, only if the PING command cannot be used in your computer network, which would make the Collector regard all computers as switched off.
- Detect computer again in
- N minutes while the computer is switched off
Enter the number of minutes to elapse before the Collector tries to detect a computer that is switched off.
- N minutes in case of detection error
Enter the number of minutes to elapse before the Collector re-tries to detect a computer whose previous detection resulted in an error.
- Process in a single block
-
The Collector processes requests in blocks. It will process the maximum number of requests you enter in this field and puts the waiting status at the end of the block.
- N computer detections
Enter the maximum number of detections to be performed by the Collector within one block.
- N detection evaluation operations
Enter the maximum number of scheduled detection evaluation operations. The operations are generated by Collector instances which use the Detect and schedule evaluation option. The Console generates operations for re-evaluation of software detections when new Software products library is loaded.
- Waiting status between the processing of blocks (minutes)
Enter the number of minutes for the waiting status between the individual blocks.
- Only perform detections for computers matching the filter
-
Enter the filter which defines computers to be detected by this Collector instance.
For example, if you want this Collector instance to detect only computers located anywhere in the object "ALVAO Subsidiary", use the following filter:
EXISTS(
SELECT *
FROM tblNodeParent NP JOIN tblNode N ON NP.lintParentNodeId=N.intNodeId
WHERE NP.lintNodeId=D.lintComputerNodeId AND N.txtName=N'ALVAO Subsidiary')
This is a conditional expression in an SQL query sent to the database. This query selects the detection requests. The example above includes the alias D which represents the tblDetect table.
- Only perform evaluation operations for computers matching the filter
Enter the filter which defines computers to be evaluated by this Collector instance. The filter uses the same format as the filter used for detection.
Note:
Computers located in the tree structure under an object of the type Warehouse are never detected.
Did not find what you were looking for? Ask our technical support team.
|