Managing Duplicate Device Entries in ControlUp

ControlUp users discuss options for cleaning up duplicate device entries, which occur frequently during customer device migrations. Suggestions include adjusting cleanup rules, using a PowerShell script to automate deletion of duplicates, and deploying the agent with the property REGISTERWITHNAME=1. A helpful user has shared their script to automate the cleanup process.

Read the entire ‘Managing Duplicate Device Entries in ControlUp’ thread below:

Goodday!

TLDR: Does anyone know an automated way to clean up duplicate device entries.

We have customers who are in the progress of migrating alot of devices. While reinstalling these devices show up with there new registration while the old one is still showing. Does someone know if there is a way to cleanup duplicate entries beside the standard cleanup rules. For know im lowering the cleanup rule based on days of inactivity. In the passed I have made an export compared duplicate serial numbers and deleted old ones. But this is a tedious job.

Is this a regular task or a once off?

quite regular, I have seen endpoints reregister themselves aswell when they have been turned of for a couple of days.

Just on a call will put some details together for you after

We have had the same issue, the problem is solved by automation with a PowerShell script triggered every 8 hours. It finds all duplicate device names, keeps only the one with the most recent last_communication, and instantly deletes all older copies in a single API call to https://api.controlup.com/edge/api/devices/delete. Result is that duplicates from migrations immediately disappear instead of hanging around for a while, the console stays clean, key users are no longer confused, and no one has to manually compare exports ever again. Works perfectly. I can share the script if you want.

Also doing the install with the command line REGISTERWITHNAME=1 (Agent version 2.17 or higher) will allow you to deploy a reimaged device and connect back to the same device in CU4D portal. As long as the device name stays that same

msiexec /i agentmanagersetup.msi /qn DEVREGCODE= TENANT=.sip.controlup.com ALLUSERS=1 PROXY=10.0.0.1:8080 PROXY_TEST_IP=1.2.3.4 GROUP=Finance ONLYSTARTONBOOT=1 REGISTERWITHNAME=1

https://support.controlup.com/docs/edge-dx-agent-distribution-and-installation-for-windows

You will not have to keep doing the clean up

The new deployment of the agent in our environment will also soon be rolled out with the property REGISTERWITHNAME=1. The solution regarding the API clears up the mess, but REGISTERWITHNAME shuts off the tap.

Thanks for sharing your insights! @member could you share your script? 🙂

Yep.

Continue reading and comment on the thread ‘Managing Duplicate Device Entries in ControlUp’.  Not a member? Join Here!