mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #459] Upload files back to the TacticalRMM server #2227
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#2227
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 @davidrudduck on GitHub (May 2, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/459
Originally assigned to: @wh1te909 on GitHub.
In certain use cases, we need to automatically retrieve a file (or the results of a script) and bring them back. It would be preferable to have it able to bring back to a somewhere on the TacticalRMM server particularly in cases where the remote site may have IP restrictions on certain transfers. This way we can whitelist our subnet and not run into issues.
For example, either a PowerShell based PUT command to push a file to a URL or a command in TRMM that will facilitate picking up a file from an agent and storing it in $FileStore/$ClientName/$SiteName/$AgentName/
In our use case, for example, we might want to execute a program that creates a ZIP file and then once that program finishes have that file uploaded back to us.
@wh1te909 commented on GitHub (May 7, 2021):
I am thinking to make this easier for you, to just build this into the agent and then you can call the exe from whatever script you want something like this
\path\to\program files\tacticalrmm.exe -m uploadfile -filepath "C:\somepath\somefile.zip"this way you don't have to know the token client site etc since the agent already has that info
or would you rather create the put payload yourself in the script?
@davidrudduck commented on GitHub (May 10, 2021):
Where do you envisage the files would end up using this method?
I actually think this is an elegant way of approach it - and controlling where and how the file goes back.
@wh1te909 commented on GitHub (May 10, 2021):
there is already a base folder setup with proper perms
/rmm/api/tacticalrmm/tacticalrmm/private/where the rmm stores files, i can just have it go there into a folder calledfilesand if you want too i can have it create subfolders for client/site, like/rmm/api/tacticalrmm/tacticalrmm/private/files/clientname/sitename/yourfile.zip@silversword411 commented on GitHub (May 31, 2021):
Sounds like a good idea to keep them separated. Going to expose these in the admin as well?