Menu

Tree [ea00bd] master / util-dropFiles /
 History

HTTPS access


File Date Author Commit
 CreateDropFile.ps1 2019-05-29 theitguys theitguys [00796e] setting up new repo
 DeleteDropFile.ps1 2019-05-29 theitguys theitguys [00796e] setting up new repo
 ReadDropFile.ps1 2019-05-29 theitguys theitguys [00796e] setting up new repo
 ReadMe.txt 2019-05-29 theitguys theitguys [00796e] setting up new repo
 screenshot1.png 2019-05-29 theitguys theitguys [00796e] setting up new repo
 screenshot2.png 2019-05-29 theitguys theitguys [00796e] setting up new repo
 screenshot3.png 2019-05-29 theitguys theitguys [00796e] setting up new repo

Read Me

#
# ReadMe for the Drop Files post
#
original post:

https://ninjarmm.zendesk.com/hc/en-us/community/posts/360032358472-NinjaRMMAgent-Drop-Files-Scripting-Oh-my-

It's been a few weeks coming, but gradually I've been building up a tutorial for allowing scripts to talk to each other-even if ran at different times. The way I initially envisioned this was via "drop files", and so this example shows how to do this. If you find a better way, please share as I have.

The concept is that a "drop file" contains information that the same script running later, or a different script running later, can use. A ton of ways this can be used include: running tallies, noting something is done already, output of scripts, creating and collecting stats for Event Log, etc. A script can use the value(s) in a drop file to perform logical decisions on the target host, so the same script can be responsive to the variations in needs of endpoints collected under the same general umbrella of a "Policy". The only restriction is that the data in my particular example is in String form, and able to be passed on the command line of a Scheduled Action.

But, because the script itself can create it's own drop files, those can be binaries, CSV, you name it. Then, the subsequent scripts need only be pointed to these files by name, and not need to be in the command line.

This example was done on a Win7x64 VM with PSv4 on it, which should cover most all endpoints these days, as PS is up to v6 and Win7 has been sunsetted. The only assumptions made are that you know how to add Scheduled Actions to a Policy.

Written for NinjaRMM, but easily transferable to other RMMs.

Check us out on Slack here:

https://join.slack.com/t/ninjarmm-colab/shared_invite/enQtNDczNDQxMTE1MTM3LWY3ZjYwMTFhYzE0NjE3M2YzMDkxNGNhOTVjNzFkMjk1MGZmZjQzM2RiN2JjYWE2ZjVmNjg4MTQ3ZTJmMzVlODU




Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.