[GH-ISSUE #2389] Dynamic filter - or even static filter to further separate agents #3414

Open
opened 2026-03-14 07:17:41 +03:00 by kerem · 0 comments
Owner

Originally created by @Aghakoocholo on GitHub (Jan 19, 2026).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2389

Hello,
I really enjoy using the RMM—it works exceptionally well. I wanted to ask if you accept suggestions or ideas for potential improvements.
Specifically, I was wondering if it would be possible to add something like a Dynamic Filter or Dynamic Group feature to the RMM.

Use Case Scenario:
Currently, Tactical separates servers from workstations, but there’s no way to further filter, for example:

  • Virtual servers from host machines
  • Domain Controllers from other servers
  • Certain workstations based on hostname

Having this capability would be extremely helpful for automating tasks such as patching or rebooting. For example, I could:

  • Patch the host before patching the VM on it
  • Patch the Domain Controller before other servers
  • Patch the remaining servers afterward
    At the moment, all servers are patched together, and simultaneous reboots can cause issues.

If we could either manually create filters for automated tasks or dynamically generate them (e.g., if a server is a VM or has “Host” in its name), it would resolve about 90% of the challenges we currently face with Tactical.

Please let me know your thoughts and whether this could be feasible.

Thank you,

Originally created by @Aghakoocholo on GitHub (Jan 19, 2026). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2389 Hello, I really enjoy using the RMM—it works exceptionally well. I wanted to ask if you accept suggestions or ideas for potential improvements. Specifically, I was wondering if it would be possible to add something like a Dynamic Filter or Dynamic Group feature to the RMM. Use Case Scenario: Currently, Tactical separates servers from workstations, but there’s no way to further filter, for example: - Virtual servers from host machines - Domain Controllers from other servers - Certain workstations based on hostname Having this capability would be extremely helpful for automating tasks such as patching or rebooting. For example, I could: - Patch the host before patching the VM on it - Patch the Domain Controller before other servers - Patch the remaining servers afterward At the moment, all servers are patched together, and simultaneous reboots can cause issues. If we could either manually create filters for automated tasks or dynamically generate them (e.g., if a server is a VM or has “Host” in its name), it would resolve about 90% of the challenges we currently face with Tactical. Please let me know your thoughts and whether this could be feasible. Thank you,
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#3414
No description provided.