Jump to content

bradpcmac

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count
    < 500 Agents
  1. This is the document I found: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/070/240/050/040/020/180 I haven't finished reading through and testing things from that document, but I was going to ask @DarrenWhite99 if I had the right document, too. @Dtpartners, sounds like you and I are trying to effectively do the same thing.
  2. Big Picture End-to-End functionality: In Automate, I set an EDF for a computer, which amounts to setting its "subscription" level (Basic, Pro, etc...). Based on that computer's "subscription", the customer needs to get certain files synchronized to it. My Current & Proposed Solution: I have a batch file that uses WinSCP to synchronize certain directories on an endpoint according to what value(s) are passed into the batch file as parameters. I have tested my batch file, and it is working correctly when I run it manually from any computer. I'd like to use Automate to handle the scheduled running and updating of this script for a particular group of endpoints. I already have the Group and AutoJoin Search setup and working within Automate. I also have created the EDFs that can hopefully be used to pass the correct parameters into my batch file ("Basic", "Pro", etc...). My idea is that I would keep one central copy of my batch file somewhere on the Automate server (we use an on-premises server) and then have Automate copy that script to the endpoint if the script has been updated since the last time the endpoint checked in. That way, if I need to change functionality of the batch file, I just have one place to do it (the Automate server). That's where I'm stuck first. Is it possible to store a file on the Automate server, have the Automate Agent check to see if that file is newer than a local file, and then download & replace the local file on the endpoint if it needs to be updated? Then, the next part of my Automate Script would need to run that batch file (now copied locally on the endpoint) and pass in parameters which are determined by the EDF values I set in Automate. Is it possible to run a batch file with parameters passed in? On the endpoint I need to regularly execute something like: sync.bat Basic this will run my script and sync the "Basic" files "Basic" is a dynamic value that we can change in Automate via an EDF if the customer changes subscriptions I appreciate any help you can give, even if it's just a piece of this puzzle 🙂
×