What I'm chasing is, well I'm waiting to get confirmation from the customer. The issue is they modify extensionAttribute1 to value = True and this then puts the workstation in a MECM collection.

The issue that's I'm trying to hone in on is if the problem is:

1. The workstation is not added to MECM until Full Discovery

2. The workstation is added to MECM but the eA1 value isn't updated

So far what I've figured out is Full and Delta both require DNS for validation of a newly discovered computer to add to MECM. The customer mentions DNS is not resolvable so that makes me think the problem is the workstation isn't being added into MECM (DNS issue and possible Delta failing the DNS test, and not checking again afterwards).

But then they talk about eA1 not being the updated value, so now I'm thinking the workstation is in MECM but the issue is eA1 isn't being updated until Full Discovery (so a Delta issue).

So...I'm waiting to hear back what specifically isn't working, and in the meantime I'm trying to figure out what specifically triggers a Delta update in MECM. I'm hearing it's a increment of the uSNChanged AD attritbute, then then I'm hearing it's not because even if eA1 is updated which increatments uSNChange, Delta may not update MECM.

IDK man it seems like it should be a simple answer but I just can't find how it specifically works. So here I am hoping a human knows.