mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #652] Enhanced agent search #2361
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#2361
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 @silversword411 on GitHub (Jul 29, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/652
Related kind of to: https://github.com/wh1te909/tacticalrmm/issues/650
Right now, you can't search by the detailed data in systems.
Items to include in the "search" box (maybe only after enabling an "advanced search" checkbox) might include:
Public IP
Private IP
Hardware Details (PC Model)
Processor type (finding older machines/BIOS firmware flash requirements)
HDD Model (firmware updates required for x HDD type)
OS (Windows 7/10/11)
OS "Version" eg 10.0.19043
Not sure if you could have a search structure to be able to query a specific wmi data field in the assets tab:
Assets-Operating System-Organization: HP (searches for all agents with the data field matching that)
or Assets-Disks-Model: "KXG50ZNV256G TOSHIBA"
kind of thing
@bradhawkins85 commented on GitHub (Jul 30, 2021):
Could this also be related to #553
Would be great if these sorts of things could be included in the "Session Group" searches as well.
@silversword411 commented on GitHub (Aug 12, 2022):
That looks too easy...even I might be able to put the kitchen sink in there now! LOL
How hard would it be to have an "advanced" checkbox so we could list a ton of fields...that would probably slow search. Hence it wouldn't be searched by default (probably result in too many matches as well)