EDIT: I double checked the wiki article, which was last modified in 2014 and the enhancement was identity probes and sensors. Given the age, I don't believe that article is very applicable to what I describe below.
I'm looking for some detail explanation on how this works (ref wiki below).
Enhanced Device Identification for Discovery in DHCP Environments - ServiceNow Wiki
I'm trying to understand how/when/where beneficial functions take place from Classification to Identification to Exploration during discovery to ensure when information is updated on a CI record that information cape from the intended target.
We've been scanning our VPN network for user class computers and recently noticed details like name, model, assigned to, short description, etc. changing on CI records. Sometimes one thing changes like name, sometimes multiple things are updated, include or excluding name. I've even seen examples where Serial number was changed but nothing else, but I only stumbled upon one such occurence of this so far.
What I assumed was happening during long 5+ hour discovery schedules is that Machine A with IP address .xxx.xxx.xxx.1 goes through some level of discovery and then gets disconnected from VPN. Machine B joins the network and is given IP address xxx.xxx.xxx.1. Machine A rejoins the network but their tunnel is gone so they have a new IP. Discovery is still running and now its still asking xxx.xxx.xxx.1 for information (which is Machine B) but is updating the record for Machine A (which was found during identification by serial number and class).
I know from talking to the network team that our IP leasing for VPN devices is very fluid to ensure there are not long unutilized IP leases. We've turned off WLAN and VPN networks discovery for now.
I have a HI ticket opened but wanted to get some feedback here as well. We're on Fuji Patch 10 I believe.
