To be more exact, the following is the UUID that gets repeated in our network:
03000200-0400-0500-0006-000700080009
It's not a bug in the OpenAudit script. Different machines in our network actually have this same UUID. (You can look it up on Google and realize it appears quite a few times, in spite of the fact that a UUID is supposed to be unique world-wide, and pretty much forever.) As mentioned earlier in the thread, the reason for this recurrence is that some motherboard manufacturers, in particular BIOSTAR, appear *not* to be setting the UUIDs of their products properly.
I modified the vbs script (this is for version 1 of OpenAudit though) so that it keeps using UUID, but handles this special case using Name + Domain. I prepended a text tag ("UUIDFIX#") for each special case, so as to distinguish them easily on the reports whenever they appear. This section of code is shortly after the comment "# Make the UUID #" :
Code:
' Defaults below here account for oddities
if ((isnull(system_uuid) OR system_uuid = "") AND (system_model <> "") AND (system_id_number <> "")) then system_uuid = "UUIDFIX1." + system_model + "." + system_id_number end if
if (isnull(system_uuid) OR system_uuid = "" OR system_uuid = ".") then system_uuid = "UUIDFIX2." + system_name + "." + net_domain end if
if system_uuid = "00000000-0000-0000-0000-000000000000" then system_uuid = "UUIDFIX0." + system_name + "." + domain end if
if system_uuid = "FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF" then system_uuid = "UUIDFIXF." + system_name + "." + domain end if
' The following UUID can be found on different PCs with BIOSTAR motherboards
if system_uuid = "03000200-0400-0500-0006-000700080009" then
system_uuid = "UUIDFIXR." + system_name + "." + domain
end if