Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Location
  • Agent Count
    750 - 1000 Agents

Recent Profile Visitors

453 profile views
  1. I get an error loading the script to view. It imports fine¿ Restarted Control Center, rebooted etc..
  2. I don't think unless someone else comes up with it, this will get updated.
  3. You can set the LTAdmin account password to whatever you like. You need to define your accounts per client. It is used with the Probe. Pushing agents. Running scripts. Executing commands. " LTAdmin accounts have essentially the same access as root when it comes to ability to access tables, make changes, etc. "
  4. @Matthew Mclaughlin @danialbulloch thanks for this thread. I am having the same issues copying from the unc path on the server to the client. Question does the Server have to be in the same Client location as the workstations? They are the same domain.
  5. @danialbulloch is the latest and greatest version at the top? I started with the scrip supplied by connectwise and modified it to point to a share on our network. I seem to be having issues using the copy command to transfer the file from the share to the client. I get the error in the debug that there are permission issues. Moving forward I copied the iso to the path on the client manually and ran the script and it behaves like it is running, but never stops and never installs. I need to debug again and see where it's actually failing. I am going to take a look at yours and hope
  6. I just had a conference call this morning with them and posed the same complaint/question. They said it was an issue with credentials. Each time an operation was made it was requesting authentication from the server (ours is hosted). They claim this will be resolved in the update scheduled for EOM. Thanks everyone for input.
  7. Anyone know of any repositories for Automate plugins? I already utilize http://www.plugins4automate.com. Any suggestions? Thanks!!
  8. Is there any way to find out what exact device is failing? We are new to automate. I am using a custom monitor pinging network devices. All I get in the alert is a site name. Aside from going to every device in the probe and selecting the notify box.. is there any way to determine what failed ping?
  9. Ours is constantly locking up. We are cloud based. It regularly sits spinning and you have to kill it and restart (desktop). We are told it is a know issue and they refuse to help.
  10. I am running this as a remote monitor. When I test is i get the following: Failed Result:Exe Monitor Missing I verified the path, and manually with no parameters I get: If I add parameters and run manually a cmd window opens and closes and I never see any results.
  • Create New...