To address this problem, you'll need to identify the non-unique network adapters found in your existing Client Automation environment, and remove it from the MDB before running the coracleanup utility:
Note: Before proceeding with this solution, a full database backup is recommended, as changes will be made to the database to resolve the issue.
Step 1: Identify the non-unique adapters present in the database.
Run the following against the mdb for Client Automation in SQL:
select mac_address, count(*)
group by mac_address
having count(*) > 10
order by count(*) desc
Here's a sample result set you might see:
Based on the output, we need to remove at least the following network adapters:
Use discretion when determine which addresses to remove. It is not necessary to remove every duplicate adapter, as some duplication can be expected when computers are re-imaged or upgraded, and not all obsolete computer objects are cleaned up in Client Automation.
Step 2: Remove the duplicates from the database.
Run the following against the same MDB database used to identify the duplicate network adapters, in order to cleanup the existing duplication in the database:
Note: The statements below follow through from the sample results in Step 1. Be sure to use the appropriate MAC addresses based on results specific to your environment.
delete from ca_discovered_hardware_network where mac_address in (
With the duplication removed, now the database is prepared for running a coracleanup.