[GH-ISSUE #2108] Notification about recently added agents. #3258

New issue

Open

opened 2026-03-14 06:59:12 +03:00 by kerem · 1 comment

kerem commented

2026-03-14 06:59:12 +03:00

Owner

Originally created by @neosec-eu on GitHub (Dec 23, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2108

Is your feature request related to a problem? Please describe.
Many times we give away the script or binary for agent installation to our customers.
It would be nice if that can be realized either in the dashboard or via the normal notification pipeline or in both ways.

Happy holidays!

Originally created by @neosec-eu on GitHub (Dec 23, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2108 **Is your feature request related to a problem? Please describe.** Many times we give away the script or binary for agent installation to our customers. It would be nice if that can be realized either in the dashboard or via the normal notification pipeline or in both ways. Happy holidays!

kerem commented

2026-03-14 06:59:18 +03:00

Author

Owner

@ZzBombardierzZ commented on GitHub (Dec 23, 2024):

A workaround in the meantime could be to add a check that fails and alerts to a default onboarding client/site. For example, I have a client named Temp for all new devices, and then I move it accordingly, although same could be done in an onboarding site for each of your clients if you have a unique installation for each client.

From there adding a check that will fail with an alert would be pretty easy to do. Alternatively, it would be a bit more complex but you could do an onboarding task (so that it only runs once) which emails or notifies you however you prefer. If you did do the task, you'd probably want to enable the "run from server" option so the email info is coming from the server.

@ZzBombardierzZ commented on GitHub (Dec 23, 2024): A workaround in the meantime could be to add a check that fails and alerts to a default onboarding client/site. For example, I have a client named Temp for all new devices, and then I move it accordingly, although same could be done in an onboarding site for each of your clients if you have a unique installation for each client. From there adding a check that will fail with an alert would be pretty easy to do. Alternatively, it would be a bit more complex but you could do an onboarding task (so that it only runs once) which emails or notifies you however you prefer. If you did do the task, you'd probably want to enable the "run from server" option so the email info is coming from the server.