Abstract: An endpoint machine has a unique endpoint identifier based on a configurable set of hardware attributes for an endpoint type. The endpoint agent running on that machine has an associated software identifier registered with the endpoint management solution upon install. The management server generates the unique endpoint identifier and provides it to the endpoint agent. Periodically, checks are run on the endpoint by the endpoint agent to determine if any of the hardware attributes have changed. If so, the endpoint identifier and the new hardware attribute values are sent to the management server, which uses the information to recognize the endpoint as the same endpoint or to detect a clone of known endpoint. If the endpoint type is unknown or does not exist, the unique software identifier may be used to facilitate the identification process, including the ability to detect a cloned machine.

Abstract: An endpoint machine has a unique endpoint identifier based on a configurable set of hardware attributes for an endpoint type. The endpoint agent running on that machine has an associated software identifier registered with the endpoint management solution upon install. The management server generates the unique endpoint identifier and provides it to the endpoint agent. Periodically, checks are run on the endpoint by the endpoint agent to determine if any of the hardware attributes have changed. If so, the endpoint identifier and the new hardware attribute values are sent to the management server, which uses the information to recognize the endpoint as the same endpoint or to detect a clone of known endpoint. If the endpoint type is unknown or does not exist, the unique software identifier may be used to facilitate the identification process, including the ability to detect a cloned machine.