Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Agent Count


    MSP Automate Engineer
  1. The MAC address format may actually be AA:BB:CC:11:22:33 as well. It depends on the agent/OS (typically I've seen the Mac and Linux agents stored this way). Checkout the agent history signup table on your database. I think it's called h_agentsignup. Something very similar to that though. In there you can actually see as well if it's blocking it from signing back up after you implement. If it is, it should show up as MAC Blacklisted, as well as show the new IP address it is coming from.
  2. James, I use the following script: I have it set to run daily on my Automate server directly. It not only removes all agents which have not checked in within the last 90 days, but it also delivers an e-mailed report to me with all of the agents which were removed which ends up looking like this when it's delivered to me: The script attached should be totally sanitized, so it is safe to import without fear of it overwriting another script with the same ID or anything. I have a separate group which contains just my Automate server which I run this script on (as well as others similar to it that I only want to run on my Automate server). If you do something similar, you either need to update the advanced settings to include your username by adding the parameter, LTRUNBYUSER=YOURUSERNAME|, also as shown below. Or just modify the script on lines 19+24 to send the e-mail directly to whatever e-mail address you want instead of using the e-mail address associated with the username of the account which ran the script. If you don't do either, it will try and pull the e-mail address of the root user, which should be the default user that schedules scripts on groups when none other is specified, and so you won't actually receive the report in e-mail format. Agent Removal over 90 days.zip
  3. It's now 2.0 compatible? Awesome. I guess your contributions got merged fairly recently? It used to be 3+ for full functionality, although I had seen you were adding items to it periodically over the past few weeks/months. I will give that a shot moving forward. Thank you!
  4. Well that's lovely...I didn't realize that was the case about having to be logged in now for any of the custom URLs like that to actually work. Thanks for the heads up + info on using the default location .msi installer with the "LOCATIONID=xx" command line option as a workaround. I was primarily using the custom URLs to give to techs who have the ability to login anyway. This definitely impacts clients that I had given direct links to though. The issue we saw that necessitated this was that when creating a new client and/or new location without any agents added to it yet, was that they were unable to actually see the location in the web CC to download a custom installer from until an agent was actually added to the location. We couldn't find a permission setting which allowed it to be seen otherwise outside of our Super Admin user accounts, or when giving the Access permission for 'Locations > Show All'. We have some clients/locations which we hide/deny access to otherwise, and so that user permission was not an option for us to allow for all. For example, with this example company, ZZ COMPANY, and the location zzcompany, without any agents part of the location. When viewed from the web portal page, you can't even select a location for that company as a non 'Super Admin' user or user without the Locations > Show All permission set. When logged in as the 'Super Admin' user, or a user with the Locations > Show All permission set, it would then show up like this.
  5. It changed with a recent patch. Yeah... It's now: https://automate.server.com/Labtech/Deployment.aspx?installType=msi&ID=1 Substitute your server fqdn instead of automate.server.com and the location ID of the location you want to deploy for at the end instead of 1.
  6. Why not do something like this: Create a search that searches just for that software + also for the EDF NOT being checked. Create a second search that searches just for that software + also for the EDF actually being checked. Create a group, limit the group to only add endpoints from the first search where it's finding the software + no EDF checked. Create a second group, limit the group to only add endpoints from the second search where it's finding the software + EDF checked. Create a one-liner script that does "ExtraData Set Value" for whatever your Extra Field you created is (presumably it's a computer EDF, so ensure it has the -1 at the end), and put %computerid% in the ID box, and then set the Value to 1. Something like this below as shown in screenshot. A value of 1 with the checkbox EDF will be "checked/True" while a value of = should be "not-checked/False" Add a script to the first group to run that script you just created, like every few hours or something, so that it checks the box of that EDF. It will then remove it from the first group so that the script doesn't run on the endpoint anymore. The second group will now add the agent that had the script run on it as the EDF box is now checked.
  7. We also utilize Webroot. In addition to these exceptions, as I've heard that Path & File exceptions are hit or miss, I also add the MD5 for the LTSVC, LTSvcMon, and LTTray to our global exclusions list under Webroot's Wbe Console - Global Settings > File & Folder Overrides > Whitelist. Those MD5's usually change with every patch, so when I apply the latest patch, I also get the MD5 of each file on an updated agent using powershell. PS> Get-FileHash $env:windir\LTSvc\LTSvc.exe -Algorithm MD5 PS> Get-FileHash $env:windir\LTSvc\LTSvcMon.exe -Algorithm MD5 PS> Get-FileHash $env:windir\LTSvc\LTTray.exe -Algorithm MD5 Currently for LT11 Patch 14, those MD5's are: LTSvc - 0CA0FD2640A9A05E1C5BFFEA23037132 LTSvcMon - 572CE0D0C2D22CDB02ED0BDBFF3E083E LTTray - 6F05B0A800ABD0B51EFF85DA40F014CA If you're by chance still on LT10.5 Patch 14, those MD5's are: LTSvc - A1C314D530002D136F1453CA20A9A609 LTSvcMon - 94284503C9BC48CA773D2284772333A0 LTTray - 7D632F019DF18B7CABE4C26D036F7752
  • Create New...