Managing Duplicate Windows Endpoints in ControlUp DEX Console

The team discussed a possible issue with duplicate Windows endpoints in the DEX console and how to handle them. A unique uid is created when the agent is deployed and can cause duplicate machines if the agent is reinstalled or the machine is reimaged. It was suggested to let the cleanup process take care of this, but there may be a way to register by name to avoid duplicate entries. More details can be found in this thread: https://controlupcommunity.slack.com/archives/C0467CPGDM4/p1688761816455149

Read the entire ‘Managing Duplicate Windows Endpoints in ControlUp DEX Console’ thread below:

Any ideas on what might cause a Windows endpoint to show up with three entries in the DEX console, assuming it’s consuming 3 licenses?

Was the machine reimaged?

There is a uid in the C:\programdata\Avacee\sip_agent\cachefiles that is unique per agent. Its created when the agent is deployed and is a random guid. If the machine is reimaged or the agent is reinstalled you’ll get duplicate machines.

it may have been for testing. i’ll ask. is there a mechanism for it to remove stale entries if it seems the same host name more than once? I know we can configure the auto remove setting

You can let the cleanup take care of it naturally.

k, thx Landon

I’m sure someone has some cleanup script somewhere but duplicate machines CAN be valid with windows machines on different "home" networks.

This can be handled by having the machines register with name

And as Landon says if you have the maintenance enabled in setting double entries will be removed after the set period

Details on how to register by name are in this thread. https://controlupcommunity.slack.com/archives/C0467CPGDM4/p1688761816455149

Continue reading and comment on the thread ‘Managing Duplicate Windows Endpoints in ControlUp DEX Console’.  Not a member? Join Here!