mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 15:05:57 +03:00
[GH-ISSUE #183] Enhancement request: Dynamically create Clients and Sites from agent deployment #2053
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#2053
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 @JRM-SC on GitHub (Nov 17, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/183
We have several dozen clients, some with multiple sites each. Pre-configuring each client and site then a specific agent deployment is a bit tedious with the smaller 5 to 10 user locations.
It would be very useful to have a generic agent deployment for which you can specify the client name and site name strings as arguments and allow the RMM to create the Client/Site if they don't already exist and add the new agent.
Something like:
/Client-Name "Example Client" /Site-Name "New Site"
@wh1te909 commented on GitHub (Nov 17, 2020):
The dynamically generated exe is just a wrapper around the generic binary that simply bakes the command line arguments into the generic exe so you don't have to pass them.
If you choose the "Manual" method from the Install Agent menu, you will see the command line needed to pass to the winagent-vx.x.x.exe which is the generic binary, as well as the download link for the generic exe. You'll need to use the client and site ID's instead of the names for now, until I add the ability to pass the client/site name and create if doesn't exist. So for now you can just use the manual method to figure out the client/site id's for each client and then set the token expiration for a year or whatever and you pretty much have a generic deployment minus the dynamic client/site creation.
@JRM-SC commented on GitHub (Nov 18, 2020):
Thanks @wh1te909, I've actually used the manual deployment method for our larger clients dropping the winagent on their local file server. Would be great to see the automatic site creation since I can script out a mass installation using Client/Site names in our current remote access system.
@dinger1986 commented on GitHub (Feb 21, 2021):
@JRM-SC is this still a feature you require? we do it by having one generic client on tactical and all goes into there then move it into the correct client.
@JRM-SC commented on GitHub (Apr 6, 2021):
@dinger1986 I would do it this way if I could mutli-select agents and bulk edit/move them to a new Client or Site.
@dinger1986 commented on GitHub (Apr 6, 2021):
fair enough, I have managed to do it fine with over 500 agents deployed.
@JRM-SC commented on GitHub (Apr 6, 2021):
Definitely not saying it can't be done but it's not the fastest process editing each individual agent and changing the location. We're sitting at 475 systems with TRMM installed out of 1140 in our Connectwise instance.
Below are some screenshots of how Connectwise Control handles multi-select and bulk actions as an example.
@sadnub commented on GitHub (Jan 10, 2022):
This is now possible using the tactical api in a PS script. You can wrap the installer with it and create the client/site and pass those variables to the installer for the agent.