mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #685] Update or Remove duplicate agent #2380
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2380
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cmiscloni on GitHub (Sep 2, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/685
By reinstalling the agent, a duplicate computer appears on console, add the possibility to update or remove it in settings.
Thanks
@silversword411 commented on GitHub (Sep 12, 2021):
I noticed in mesh options there's a feature that "removes disconnected agents"
You might be able to set that to clean agents after x time not connected, but that might kill valid agent's
@cmiscloni commented on GitHub (Sep 12, 2021):
The problem is when we 're reinstalling a computer (same computername) , a second agent is create. Maybe if it's possible to create a background task which find the duplicate name and keep only the most recent ?
@dinger1986 commented on GitHub (Sep 12, 2021):
Is this for mesh or tactical?
@cmiscloni commented on GitHub (Sep 12, 2021):
Tactical
@nr-plaxon commented on GitHub (Sep 13, 2021):
Something along this maybe: #708
@bbrendon commented on GitHub (Sep 23, 2021):
Sounds great but how would you know its a duplicate?
PS. Don't say hostname because I've seen plenty of idiots with duplicate host names on their network.
@silversword411 commented on GitHub (Sep 24, 2021):
By MAC address, then hostname. Isn't that what everyone else does? ;)
@nr-plaxon commented on GitHub (Sep 24, 2021):
MAC address by itself would work. Who puts a physical NIC to a different host nowadays… Maybe limit this to agents marked as clients and skip servers. Showing a list of duplicates in the process of the maintenance task so the user can cancel would also be a safety net.
@cmiscloni commented on GitHub (Sep 24, 2021):
by IdentifyingNumber (serial)
@silversword411 commented on GitHub (Sep 24, 2021):
No, because there's machines with "to be filled in by OEM" out there
@dinger1986 commented on GitHub (Oct 15, 2021):
Can probably close this also as covered in #708 as @nr-plaxon mentioned. Agreed best doing it on mac address is the only way or manually is the other option if thats added to mass delete.
@silversword411 commented on GitHub (Nov 29, 2021):
You now have a manual method of bulk deleting old agents:
github.com/wh1te909/tacticalrmm@2c8f207454https://github.com/wh1te909/tacticalrmm/pull/830/commits/3f3ab088d233734db0375681dd66fba2ed518154
By: agentver or days since last checkin
Will be in next release.
@jmoran-shafer commented on GitHub (Dec 6, 2023):
+1