Why does the Endpoint Beta Console show multiple entries for the same endpoint?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Why does the Endpoint Beta Console show multiple entries for the same endpoint?

L2 Linker

We are currently working with the upgraded version 25.12, but the Beta Console continues to display multiple entries for the same endpoint.

I have reviewed the available documentation and community articles, which indicate that this issue was resolved in earlier releases (for example, version 25.2). However, despite being on 25.12, we are still experiencing the same behavior.

Has anyone encountered this issue in version 25.12, or can confirm whether there are additional configuration steps, known limitations, or patches required to fully resolve it?Field_Content_versions_oct20__068Vy000019QQCXIA4.pngField_Content_versions_oct20__068Vy000019QDqcIAG.png

1 accepted solution

Accepted Solutions

L5 Sessionator

@Sumitha Sudheer​  There are few possible scenarios that could explain the duplicate entries in Endpoints Beta page:

 

1. Agent version was earlier than 25.2; Versions below 25.2 had a bug (you referred to) that caused the agent to be re-registered, resulting in duplicate rows.

2. Bad connectivity from the agent side. If the agent registered but wasn't able to connect due to a bad network, it may re-register, which will again cause duplications.

3. Using imaging of an existing VM with an agent on multiple instances.

4. The client manually uninstalled the agent from the computer and installed it again. The My Computer ID will persist, but Endpoints Beta re-register.

View solution in original post

2 REPLIES 2

L5 Sessionator

@Sumitha Sudheer​  There are few possible scenarios that could explain the duplicate entries in Endpoints Beta page:

 

1. Agent version was earlier than 25.2; Versions below 25.2 had a bug (you referred to) that caused the agent to be re-registered, resulting in duplicate rows.

2. Bad connectivity from the agent side. If the agent registered but wasn't able to connect due to a bad network, it may re-register, which will again cause duplications.

3. Using imaging of an existing VM with an agent on multiple instances.

4. The client manually uninstalled the agent from the computer and installed it again. The My Computer ID will persist, but Endpoints Beta re-register.

L1 Bithead

Hello @Patrick Booth​, quick question: After activating Endpoints (non-Beta) following the upgrade to agent version 25.12, do we still see the same duplicate re-registration issue, or does it get resolved?

  • 1 accepted solution
  • 103 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!