Find a perfect or best match for a target
The perfect match option is enabled by default in Remote Control. This option is used to find a perfect match for a target, where 4 criteria are used to find a match. The criteria are Virtual Product Data (VPD), UUID, MAC_ADDRESS, and COMPUTERNAME. A perfect match is defined as finding a target in the database where all 4 criteria are matched successfully. However, if any of these values change for a target, 2 further properties can be used to find a match.
- match.change.notification - Can be used if any of the criteria values change for the target.
- match allow.data.changes - Can be used if only one of the criteria values change for the target. This option is defined as a best match.
- match.change.notification
-
- True
- This value is the default value. The target saves its details locally to a file called
tgt_info.proprties. This file is in the target working directory that is
defined by the WorkingDir property in the target registry. When the target
contacts the server, it sends its old details and its new details. The old details are used to find
a perfect match for the 4 criteria.
- 0 matches.
- If no match is found, a new hardware key is generated and a new target entry is created in the database.
- 1 match.
- If a match is found, the details of the matched database entry are updated.
- > 1 match found.
- If more than one match is found, the first match is used. This scenario is unlikely to be found.
- False
- The old target details are not sent to the server and the new changed details are used to try to find a match. However, if only one of the 4 criteria has changed and the match.allow.data.changes property is set to true, a best match is looked for.
- match.allow.data.changes
- This
property is used to try to find a best match for a target in the database.
- True
- This value is the default value. When set to true, a best match is successful if all but 1 of
the 4 criteria match an already registered target.
- 0 matches.
- If no match is found, a new hardware key is generated and a new target entry is created in the database.
- 1 match.
- If a match is found, the details of the matched database entry are updated.
- > 1 match found.
- If more than one match are found, create a new hardware key.
- False
- If the perfect match process is enabled and no match is found for all 4 of the target criteria, the best match option is not considered. Depending on the value of match.change.notifications, if no match is found then a new target entry is created in the database.