[GH-ISSUE #1780] Agentless Agent listing for inventory purposes #3053

New issue

Open

opened 2026-03-14 06:22:30 +03:00 by kerem · 4 comments

kerem commented

2026-03-14 06:22:30 +03:00

Owner

Originally created by @P6g9YHK6 on GitHub (Feb 29, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1780

Is your feature request related to a problem? Please describe.
Tactical currently has currently no inventory management feature to add non compatible devices to the database.

Describe the solution you'd like
To help with inventory management it would be nice to be able to add "agents" to the console manually without an installation on an end device.
Where there would be no "agent" installed on the device there would just be a blank slate of editable fields to allow us to write all the informations ourselves about certain devices that are not "manageable" like switches, router, unsupported OS versions, ETC, ETC.
This would help centralise some knowledge on infrastructures that would go beyond TRMM.

This could also obviously exploit the current reporting feature for inventory management.
A lot of features would be disabled on these "agents" like mesh, tasks, checks, alerts etc.

Some other native feature could still be leveraged like url actions to access things like rdp, web ui, other internal tools, etc

Describe alternatives you've considered
external tools.

Originally created by @P6g9YHK6 on GitHub (Feb 29, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1780 **Is your feature request related to a problem? Please describe.** Tactical currently has currently no inventory management feature to add non compatible devices to the database. **Describe the solution you'd like** To help with inventory management it would be nice to be able to add "agents" to the console manually without an installation on an end device. Where there would be no "agent" installed on the device there would just be a blank slate of editable fields to allow us to write all the informations ourselves about certain devices that are not "manageable" like switches, router, unsupported OS versions, ETC, ETC. This would help centralise some knowledge on infrastructures that would go beyond TRMM. This could also obviously exploit the current reporting feature for inventory management. A lot of features would be disabled on these "agents" like mesh, tasks, checks, alerts etc. Some other native feature could still be leveraged like url actions to access things like rdp, web ui, other internal tools, etc **Describe alternatives you've considered** external tools.

kerem commented

2026-03-14 06:22:36 +03:00

Author

Owner

@Slouserg commented on GitHub (Apr 12, 2024):

i would love to see that.

@Slouserg commented on GitHub (Apr 12, 2024): i would love to see that.

kerem commented

2026-03-14 06:22:41 +03:00

Author

Owner

@ZzBombardierzZ commented on GitHub (May 17, 2024):

+1 from me

@ZzBombardierzZ commented on GitHub (May 17, 2024): +1 from me

kerem commented

2026-03-14 06:22:46 +03:00

Author

Owner

@P6g9YHK6 commented on GitHub (May 29, 2024):

Another use of this could also to set checks that would run on another defined endpoint and report the results here

@P6g9YHK6 commented on GitHub (May 29, 2024): Another use of this could also to set checks that would run on another defined endpoint and report the results here

kerem commented

2026-03-14 06:22:51 +03:00

Author

Owner

@silversword411 commented on GitHub (Feb 23, 2026):

@silversword411 commented on GitHub (Feb 23, 2026): Similar https://github.com/amidaware/tacticalrmm/issues/677