...
When you create a discovery you have an option to "assigndevices_devicesassigned_to_org". This means that any devices discovered for this discovery will be assigned (have system.org_id set to) your chosen Organisation.
...
From this release onward, we will take this into account for devices for a certain defined subset of match rules. Thise These rules are:
- match_dbus
- match_fqdn
- match_dns_fqdn
- match_ip
- match_ip_no_data
- match_serial
- match_serial_type
- match_sysname
...
If you don't normally set 'assigndevices_devicesassigned_to_org', then it will have no effect. We only check using the OrgID if it has been set in discovery (or manually in an audit script).
If you do normally set 'assigndevices_devicesassigned_to_org', then the OrgID will be used to further refine the match.
If you subsequently change the OrgID of a device , post after discovery then you will likely have a new device created the next time the discovery runs. In this instance, you should probably just unset 'assigndevices_devicesassigned_to_org' before running subsequent discoveries. This is because (in this instance) you have told Open-AudIT "these devices from this discovery below belong to Org X", but then changed the Org of the device. You have provided conflicting changed the stored devices information. In this case - there is no no longer a device belonging to Org X, so we create a new one.
...