Uniquely identifying the same machines and separating machines with similar properties is a tough challenge for any vendor with an endpoint footprint. We choose to share the way vRx approaches that to explain why sometime it may fail.
Here are some use cases we're looking to solve:
| # | OS | Machine Type | Scenario | Challange |
| 1 | Mac | Physical | The machine is uniquely identified using hardware properties. | |
| 2 | Windows | Physical | The machine is uniquely identified using hardware properties. | |
| 3 | Windows | Physical | Hardware was changed, and the machine is duplicated but active | Identify the same machine after hardware change |
| 4 | Windows | Virtual | The machine is uniquely identified using hardware properties. | |
| 5 | Windows | Virtual | The machine was copied or imaged. There are two machines. Only one is active. The second one can't register | Create a new asset when a virtual machine was aggressively copied or imaged |
| 6 | Linux | Physical | The machine is uniquely identified using hardware properties. | |
| 7 | Linux | Virtual | The machine is uniquely identified using hardware properties. |
Here is the way we mitigate the two challenges:
and this how machines are registered in a normal scenario:
