with a particular NS agent version, but I can't seem to find it. Your solution is interesting, as the client would keep it's guid locally, and therefore reassociate itself in the db.

I'm still searching for that issue, but you are at the latest agent version right?

We are running version 6.0.2403 which I believe is the latest version.  I have a query I found on the knowledgebase for forcing the NS to accept the data a computer submits next so I am running that against machines one at a time for now.  There has to be a better way.
 

declare
 @computer char(20)
set
 @computer=''
UPDATE
 [ResourceUpdateSummary]
SET
 [DataHash] = NULL
WHERE
and
 [InventoryClassGuid] IN (SELECT [Guid] FROM [Dataclass] WHERE [Name] LIKE 'AeX HW%' OR [Name] LIKE 'AeX SW %' OR [Name] LIKE 'AeX OS%' OR [Name] LIKE 'AeX EU%') resourceguid = (select guid from vcomputer where name = @computer)

I think I have a better query:

UPDATE [ResourceUpdateSummary]
SET [DataHash] = NULL
WHERE [InventoryClassGuid] IN (SELECT [Guid] FROM [Dataclass] WHERE [Name] LIKE 'AeX HW%' OR [Name] LIKE 'AeX SW %' OR [Name] LIKE 'AeX OS%' OR [Name] LIKE 'AeX EU%')
and exists (select guid from vcomputer where exists (select *
from inv_aex_ac_identification
where [os version] = '5.2'
and [system type] = 'win32'
and [os type] = 'professional'))

I will check that out to see.  Thanks for the suggestion.  My question is why does the AD import have a default machine type anyway?

That does seem to be the issue.  I will have to figure out how I want to handle it.  Thanks.

I'm waiting to hear back from my AE about how to handle this, and exactly how to set it up so that the system type will not be blanked out if it is already valid, but anything already populated will remain.