We've seen a few instances where duplicate entries for the same device appear in the DNSFilter dashboard, specifically under Roaming Clients. This can occur for a variety of reasons, which we wanted to outline to help users understand and manage these occurrences more effectively.

Causes of Duplicate Entries

• Registry Changes: If a device’s client ID registry entry is modified or removed, such as during a reinstallation or upgrade, the DNSFilter agent may re-register the device with a new ID, resulting in a duplicate entry.
• Multiple Versions Installed: Sometimes, both the standard and whitelabel (DNS Agent) versions of the DNSFilter agent are accidentally installed on the same device, which creates multiple entries in the dashboard.
• Reinstallation of Different Versions: When a device has had multiple agent versions installed over time, each version might create a new entry if reinstallation or updates are not managed carefully.

To address these duplicate entries, we recommend the following steps:

1. Delete Older Entries in the Dashboard:
   • If duplicate entries persist, review the versions and delete any outdated or unnecessary entries directly from the DNSFilter dashboard. Be sure to retain the most recent or correct entry to avoid disruption.
2. Identify Duplicate Entries Proactively:
   • Regularly audit your Roaming Clients list to catch duplicates early, particularly after upgrades or reconfigurations.
3. Check for Multiple Versions:
   • Verify whether both the standard DNSFilter agent and the whitelabel DNS Agent are installed. If so, uninstall one version to prevent duplicate entries.
   • Use the following commands to uninstall specific versions if you are on Windows:

For the standard DNSFilter Agent:

• $Prod = Get-WMIObject -Classname Win32_Product | Where-Object Name -Match 'DNSFilter Agent' $Prod.UnInstall()

For the whitelabel DNS Agent:

• $Prod = Get-WMIObject -Classname Win32_Product | Where-Object Name -Match 'DNS Agent' $Prod.UnInstall()

If you’re encountering issues with duplicate entries despite following these steps, or if you need help troubleshooting specific devices, please comment below for additional assistance. We can connect you to support to provide logs from affected devices can help us investigate and resolve the issue more efficiently!