mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #1553] Background "Pending Deletion" for offline deleted Agents #2919
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#2919
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 @ssteeltm on GitHub (Jul 6, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1553
When we delete an agent from dashboard and its offline, it deletes from rmm, but in that PC the agent still installed, and then when online again would try to reach RMM server and generate this message with auth error:

An ideia would be to keep this auth on database, marked for delete/uninstall, so when the agent whos been deleted from dashboard and was offline, comes online it will reach rmm server, auth ok, and have the instruction to uninstall, like it would do if it was online in that time.
@plao commented on GitHub (Aug 19, 2023):
Would be nice, yes