Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


LoneWolf last won the day on November 15 2019

LoneWolf had the most liked content!

Community Reputation

16 Good

My Information

  • Location
    The Mitten State, USA
  • Agent Count
    1000 - 1500 Agents


    Craft beer aficionado
    Mechanical tinkerer
    RMM Administrator - IT Engineer
    LabTech Certified Professional

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Rafe Spaulding, THANK YOU! I didn't think about them being a remote monitor (and of course, they didn't show as internal monitors, because they aren't). Webroot's monitors have just been too inaccurate to be worthwhile for us at any rate, so we monitor it by other means. Thanks again for your assistance. P.S. A reminder to me that it's okay to feel like a dope, as long as you learn something from it. 😅
  2. To those of you who use Automate and Webroot: We have times when we wish to manually upgrade Webroot, or deactivate it and remove it from a system. During that time, there is a temporary condition where the Webroot process is not found, generating a ticket with the following title: "service wrsa is process wrsa not found for <computer>" The Service Monitor detected that the service wrsa is Process wrsa Not Found I have been unable to figure out what generates this alert so I can stop it from creating tickets. Does anyone have any suggestions? There's nothing actionable on this, and we just want to cut down the noise.
  3. Hi all, I've settled into a new workplace, and I'm working on cleaning up their Automate install. However, due to the way it was previously administered, I'm concerned that groups and sub-groups may have been moved around in improper ways. I've also experienced cases where I've found duplicate groups, which concerns me (in those cases, I've kept the lower numbered group, and moved any sub-groups of the one I haven't kept into it). Without standing up a testbed Automate install on another box (or as a VM), does anyone have the list of default Automate 12 Groups and their [tree] structure? I'd like to ensure there are no anomalies and if I find them, bring groups that are not custom back to how they are as an out-of-box configuration.
  4. It's a yes-and-no thing. You can still create Client and Location tabs. This is still incredibly useful for me. You cannot create Computer tabs. For this, I create new EDF "tabs" with EDFs in them. I'm unsure about the other areas, I've never used them. But for me, this still makes Custom Tabs a useful (though incomplete) plugin. Custom Tabs does sometimes add random EDFs I didn't choose (and have to remove) to a tab, so that's a little odd.
  5. We are using DUO for our 2FA; with the plugin, it works with the thick and thin client. In order to look at SSO, we're looking at leveraging the current LDAP option of Connectwise, with Azure AD sync on our end so we aren't limited to the method of using Connectwise SSO only on the web, or only with Connectwise accounts. While it isn't strictly listed as a supported option, we have already heard of other Automate clients using this method.
  6. Darren, I've seen your work and used some of it; you totally have my trust. I'm reading everything, and should be able to use this to implement. I really appreciate your help and the time you took to give it. This thread goes in my bin for teaching me how to expand my knowledge. Thanks again!
  7. Is there a common theme of what operating system the agents are running? Having this issue for me (at the time, since resolved) was largely due to Windows 7 systems with a very old Windows Update Agent version, causing issues bringing those systems up to date. Also note: From what I was shown by Automate support, you should have one approval policy for Microsoft updates. If you are doing third-party patching, you should have additional policies, one for each third party application you are updating.
  8. @ZenTekDS Here is a copy. It should import into a folder called "Partner Scripts". Thorough Disk Cleaner v2.5.zip
  9. Apologies for my lack of MySQL experience; I know that at least two-thirds of the people here know it better than I do, so I'm requesting your help. I know this is probably pretty easy for many. I have custom DRV - Free Space Remaining monitors that I have created based on our thresholds. Sample: Drives.Size > 20480 and Drives.FileSystem not in ('CDFS','UNKFS','DVDFS','FAT','FAT32','NetFS') and Drives.Letter IN ('C') and Drives.Model not like '%USB%' and Drives.free < 2048 and missing=0 and internal=1 What I'd like to do is an "and not in" and specify a Role group, in this case any HyperV Host Servers, located in the following group: Groups -> Server Roles -> Windows Servers Core Services -> Windows HyperV Host as we have separate internal monitors for this role. My limitation as a sysadmin and not a DBAdmin is not knowing either the syntax, and how to dig down and find the appropriate tables in the Automate database (note: I do have SQLYog, have done some exploring, can run basic queries). How do I translate what I know I need to do onto the end of this monitor to exclude members of this group?
  10. I use a (modified by me) version of the Thorough Disk Cleanup Script by Squatting Dog Development. My version also detects IIS and cleans the log files, and cleans SBS log files (if that OS is detected) as well. It also provides a selectable option to empty all recycle bins (selectable because we all know someone that got the bright idea of using the Recycle Bin as a filing cabinet). If anyone wants a copy, I'll be happy to attach it.
  11. Like most of you, we have moments when we retire a system because it is removed from a network without our knowledge. In these cases, like most of you, we move it to a group where it is supposed to automatically offboard (we have scripts and such to do these things) if it comes back online. However, if we do not receive communication within a set period of time, we retire the system manually. My issue is this: Every now and again, a system that is retired gets given to a family member or someone pulls said system from the refuse pile somewhere and turns it on again. In this case, the system of course re-onboards itself into Automate and out of the retired systems. Does anyone have a monitor or something set up that allows them to be notified when this action happens? I have onboarding scripts that notify us when a new system is set up, but I don't know if there's any way to monitor this change on client systems. If so, I'd like to set things up so one of our distribution groups will get an e-mail so we'll be aware of it.
  12. This is a serious improvement, DarrrenDK. Nice work.
  13. Darren, It was just for my understanding. Thanks for the answer, I appreciate it. Also, the advantage is that right now, Windows XP Agents will be broken by Patch 11 (which has been yanked, but I'm unsure if this will happen again when it is released). I want to keep XP/2003 class agents from updating off of Patch 10, so this is very helpful.
  14. Darren, Dumb question -I'm assuming one has to add a monitor target (e.g., "All Agents") to this after import?
  15. I've just been asked to see if I can implement some form of monitoring for when a server experiences a blue-screen crash. I already know that I can't quite do this in realtime (after all, the system does a kernel dump, then reboots the system, during which it is unavailable). I certainly can monitor for a dirty shutdown event ID 6008, and I've implemented a remote monitor to this effect, but I'm wondering if there's a better way, or something that provides a little more information, so I'd like to pick everyone's brains (I promise, I won't take any pieces out 😉). What are the conclusions you have drawn in trying to proactively monitor such situations, and what solutions have you implemented?
  • Create New...