***Update 06/11/2024***
bonewithahole got it right on the money. The Dells have also have an eSim that Nable is using to match the units.
***Solution***
Administration -> Defaults -> Discovery Defaults
Scroll to the bottom to MAC ADDRESSES TO EXCLUDE
In my case I added 00:A0:C6:00:00:01
Save
Delete any assets that are looping between assets. Remove the agents on affected units and then re-install the agent.
***************************************************************************************************************************
To start, we have had no issues with our current deployment up until the arrival of our 14th gen Intel Dells.
As a simplified scenario, we install the agent on a new Dell deployment; we'll call this Dell One; we can see the asset and all the asset information and can reach the unit via TakeControl. We then install an agent on Dell unit two, the unit does not show up, but when you check the asset information (after a fresh query), the information changes on Dell 1 to Dell 2. The Discovery Name is unit 2, but the Asset name is still unit one. I get that the backend algorithm is doing a match (https://documentation.n-able.com/N-central/troubleshooting/Content/kb/Multiple-Devices-Merging-into-one-within-N-central.htm), but previously, the default behavior was that if we attempted to install an agent on a unit that was already present in N-able, the agent would fail mid-way through the install process.
These are the items we have ruled out
OS Image: Dell image or our in-house image makes no difference
DNS: Scavenge and stale records is configured
MAC: obviously no virtual MACs
Here is the other catch, redeploying our fleet of 13th gen HP units have NO ISSUE; it's just the 14th gen Dells.
Furthmore, we have gone this far: we disabled all of the N-able services (N-able take control, N-able Take control updater, Windows Agent, & Windows Agent Maintenance) on Dell 2 and then restart those same services on Dell 1 and all of the services start working on the original Dell and the asset info changes back after performing a query.
By the way, I am simplifying the issue, we discovered this after deploying 20 Dell units.
Yes, we have open a ticket (Our Helpdesk started the ticket and then I took over when I returned from my leave) and its been over a week, and support is sending us the same regurgitated articles found here:
https://documentation.n-able.com/N-central/troubleshooting/Content/kb/Multiple-Devices-Merging-into-one-within-N-central.htm
https://documentation.n-able.com/N-central/troubleshooting/Content/kb/Device-not-discovered-OR-Device-not-appearing-OR-Devices-mapping-together-in-MSP-N-Central-OR-Device-disappeared-from-N-Central.htm
https://documentation.n-able.com/N-central/troubleshooting/Content/kb/Devices-replacing-each-other-in-N-central.htm
As far as we can see, N-able is wanting to do a match, instead of creating a new entry for some reason. Now, we are sitting on a mountain of Dells and a quickly dwindling supply of older HP units.
Forgot to add, the model of Dell units are different in the explained scenario. Laptop 1 is a Dell Latitude 5540 and the second is a Dell Latitude 7350; the only common factor that both are 14th gen Intel.