"In theory" - no it's not. In practise..... a lot of white-box makers don't bother to set a serial or UUID in the bios. And sometimes (as you've seen) you can get duplicates. Sometimes you can flash the bios, and update this field. Depends on the bios / motherboard / chipset / manufacturer... That's why there is the option of UUID, MAC or Name in the script. If two systems are reporting the same MAC, then you have serious issues. Every network interface should have a uniquie MAC address. Are these machines "virtual", by chance ? Maybe you copied a VM and ended up with the same MAC ? If they're physical machines, I would be worried !!! Pull the NIC and check the MAC (usually on a sticker) - or if they're onboard NICs, check in the BIOS.
FYI - OAv2 gets around this by concatenating the UUID + MAC + Name. THAT combination oughta be distinct !!! And "yes", I am planning a "merge systems" option - for when you change a network card or rename the PC, etc. Systems are also flagged in the DB as "production", "retired", etc. So if you reinstall a system and use the same name, before you audit it after reinstalling, simply change the flag in OAv2 to "retired" and you won't get massive amounts of false positive alerts.
_________________ Support and Development hours available from [url=https://opmantek.com]Opmantek[/url]. Please consider a purchase to help make Open-AudIT better for everyone.
|