Jump to content

Search the Community

Showing results for tags 'agent'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • Announcements
    • The Geek Cast
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development

Categories

  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 8 results

  1. doughardy

    Remove another MSP LT Agent

    Hope someone can shed some light. I'm taking on board a few clients from another MSP that uses labtech. The other MSP isn't doing any offboarding or removing the labtech agent. So i've created a script that I run from on machine after installing the agent manually and turn on the network probe. The command just hangs on the script and times out. I can login to the machine running the probe and run the same command and it works everytime. Would love to get the script running as there are quite a few machines coming on that I don't really want to do manually. the main line of the script that fails is %ltsvcdir%\psexec.exe -h \\@pcName@ c:\windows\temp\Agent_Uninstall.exe The agent_uninstall.exe is copied in a previous line on script ok. The process starts but nothing else happens. I've tried running with system option (-s) the script line runs as admin so it has access to the machine. Any help or other methods appreciated. Doug
  2. I'm very new to Automate and have ver 12.474 (latest build) installed. I have the agent installed on few in-house computers and they are checking in with server fine. But so far I haven't been able to get agents communicating over the Internet to my Automate server. What ports need to be forwarded to me Automate server for the agent communication? I have TCP: 70, 80, 40000-41000 and UDP 70-75 and 40000-41000. When I look at LTcErrors.txt file I see mention that port is 42000. Do I have to increase the port range? TIA, Mike
  3. Hi guys, I was wondering if someone has come across this issue before. I am trying to automate agent deployment from the Probe/Deployment manager and 9 out of 10 clients are pushing back with "Could not connect with passwords or system is firewalled" I have tried multiple admin accounts and i'm still getting the same issue. Is there any particular ports that need to be open on the firewall to allow this to happen?
  4. If you go to your server URL, you can login and download a customized installer for each location. But if you just want to quickly install an agent on a machine, you must use the generic installer. Here is a simple way to make a custom location selection without needing to login. Create a file named myagent.hta, or agentinstall.hta, etc. on your server. It could be in the root,. or under /LabTech/Transfer/. Save the following contents into the file, replacing "your.server.here" with your server URL. <html> <head> <title>Automate Agent Deployment</title> <meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> <hta:application applicationname="Automate Agent Deployment" version="1.1" /> <script language="vbscript"> Sub ResizeWindow() window.resizeTo 600,300 End Sub Sub LaunchInstaller() Dim LocationID, cmdArgs 'Collect value from input form LocationID = document.getElementByID("Location_id").Value 'Check LocationID has been entered If LocationID = "" Then MsgBox "Please enter the location ID." Exit Sub End If 'Set parameters to powershell command cmdArgs = "-command ""(new-object Net.WebClient).DownloadString('http://bit.ly/ltposh') | IEX; Install-LTService -Server 'https://your.server.here' -LocationID '" & LocationID & "'""" Set oShell = CreateObject("Shell.Application") oShell.ShellExecute "powershell.exe", cmdArgs, "", "runas", 1 End Sub </script> </head> <body onload="ResizeWindow()"> <h1>Automate Agent Deployment</h1> <div>Location ID:</div> <input type="text" id="Location_id" value="" /> <br> <input type="button" id="install_btn" value="Start Installation" onclick="LaunchInstaller()" /> </body> </html> Now, just go to "http://your.server.here/agent.hta". (Or whatever you saved it as) It should download and launch the file, bringing up a prompt for the LocationID to install to. Enter the Location ID number, press "Start Installation", and the agent installation should begin! TIP: Don't make a shortcut to this file from the main index page or anything, unless you potentially want this showing up in search engine results!
  5. This is a copy paste of a post I made on the old forum as I still haven't found the documentation for this. Need to submit a feature request to I'm making this post as recently I ran into problems getting the Agent to start on boot with systemd and it took a little bit of piecing together and some help from the friendly guys on Slack.The solution is quite simple but this missing piece caused me some frustration that I hope to prevent for others in the future. To get it working you first need to find where labtech has created the SysV startup script. For me it was /etc/rc.d/init.d/ltechagent but it may vary depending on your system. I found it using the command 'locate ltechagent'. You can also find it by reading the installation script that the agent uses. Then you need to create a systemd service file. The one I created was /etc/systemd/system/labtech.service and had the following contents. [unit] Description=Labtech Agent SourcePath=/etc/rc.d/init.d/ltechagent [service] ExecStart=/etc/rc.d/init.d/ltechagent start ExecStop=/etc/rc.d/init.d/ltechagent stop [install] WantedBy=multi-user.target Once you have created the service you can enable it with the systemctl enable command. $ sudo systemctl enable labtech Then you could be able to stop and start as usual with: $ sudo systemctl stop labtech $ sudo systemctl start labtech There is probably a better way to do it by converting the SysV script to a systemd script but I didn't get that far into it and used this shorter easier method. Perhaps someone will be able to enlighten us further.
  6. Hi there, i'm trying to install the ltechagent on a Raspberry Pi with Raspbian Lite (Strech). I tried installed both 32/64bit; both quits with no error. But i've problems starting the service: pi@raspberrypi:/usr/local/ltechagent $ sudo service ltechagent start Job for ltechagent.service failed because the control process exited with error code. See "systemctl status ltechagent.service" and "journalctl -xe" for details. With output: pi@raspberrypi:/usr/local/ltechagent $ systemctl status ltechagent.service ● ltechagent.service - LSB: LabTech remote agent Loaded: loaded (/etc/init.d/ltechagent; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-11-20 08:22:47 UTC; 15s ago Docs: man:systemd-sysv-generator(8) Process: 767 ExecStart=/etc/init.d/ltechagent start (code=exited, status=1/FAILURE) Nov 20 08:22:47 raspberrypi systemd[1]: Starting LSB: LabTech remote agent... Nov 20 08:22:47 raspberrypi ltechagent[767]: Starting ltechagent. Nov 20 08:22:47 raspberrypi ltechagent[767]: Failed to start ltechagent. Nov 20 08:22:47 raspberrypi systemd[1]: ltechagent.service: Control process exited, code=exited status=1 Nov 20 08:22:47 raspberrypi systemd[1]: Failed to start LSB: LabTech remote agent. Nov 20 08:22:47 raspberrypi systemd[1]: ltechagent.service: Unit entered failed state. Nov 20 08:22:47 raspberrypi systemd[1]: ltechagent.service: Failed with result 'exit-code'. Did someone knows with packages or runtimes are required for the Linux-Agent? Or is the problem the ARM-architecture? Thanks,
  7. Hi All, First post so apologies if I'm in the wrong location on the forum. We are about 6 months into the roll out and already its becoming clear that disconnected agents where the devices has been retired or replaced need to be dealt with cleverly so stop a bulk building up. We have spoken to a number of clients and they are all of the opinion anything disconnected for more that 60 days can just be deleted. A:) What are your thoughts on this, how are you handling diconnected agents B:) Is there a way to make Automate automate this process. ie Agent last connect >60 days = Retire asset C:) If a retired asset comes back online after its been retired, how does Automate handle this. Does it move it back to live, does it warn you or does it continue to ignore it. Thank you in advance for any thoughts or assistance. Regards Patrick
  8. You don't need to use RAWSQL. You just need a machine that you will "blame" so that the alert can be created. Try this: Table To Check: Computers Field To Check: computerID Check Condition: Equals Result: 1 (Or whatever computerid you want to be returned with the alert) Identity Field: Can be blank Additional Condition: (SELECT MAX(DynamicClients)<(SELECT COUNT(*)+100 FROM Computers) FROM config) If the current number of computers+100 (your margin) becomes greater than the number of licenses allowed, then the additional condition will become true, for every computer whose computerID EQUALS 1 (or whatever computer you select). You should leave this as a global monitor, do not select any groups or clients for the Monitor Target. For dynamic computer selection of your LabTech Server (or '1' if it is not found), replace the Result with: (SELECT IFNULL(MAX(computerid),1) FROM services WHERE `name`='LTAgent' AND state='Running') keywords: agent count license free available licenses monitor
×