Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

LoneWolf last won the day on March 20

LoneWolf had the most liked content!

Community Reputation

13 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. 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!
  2. 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.
  3. @ZenTekDS Here is a copy. It should import into a folder called "Partner Scripts". Thorough Disk Cleaner v2.5.zip
  4. 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?
  5. 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.
  6. 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.
  7. This is a serious improvement, DarrrenDK. Nice work.
  8. 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.
  9. Darren, Dumb question -I'm assuming one has to add a monitor target (e.g., "All Agents") to this after import?
  10. 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?
  11. I am receiving the following error output when running the script in Powershell ISE (I have attached the text). This occurs whether or not I have commented out the Lenovo updating or added the HP limit (we don't have many of either systems). It happens after the HP serials are submitted, and I receive a message stating "HP API says to wait xxx seconds before requesting the result"; there is some delay before I get all of this. If I comment out the Update-MissingHPWarranties line, the script functions. The output was long enough that I felt an attachment was better than just pasting a vomit of text. Does anyone have any ideas? ScriptError.txt
  12. I'll look into that. In these cases, the alerts I've set up are problems that likely won't auto-heal anyway, as they're indicative of drive failures. They won't heal without actual action taken on our part. I've not had an alert flood with this setup. However, for conditions that can auto-heal, you have very good points. Thank you.
  13. This can be done remotely, and while the server is online, it does not require a restart. It's also recommended that you perform any ESM firmware updates, as sometimes these (the backplane or iDRAC) will take note of these Seagate drives and change the fan profile to improve cooling of them. The Seagate Cheetah 300/600GB SAS drives were particularly problematic. They run very hot and have a very accelerated death rate. The ES68 firmware can help this, but if you've gone a long time without it, expect the drives to go predictive failure at some point. I've had 3-4x the failure rate of other SAS drives with this family. That monitor is meant to identify that type of drive for your remediation.
  14. Have you tried upgrading to PS5? Maybe it will help. I only tried mine on Windows 10. Personally, I'd rather do Win7 to Win10 upgrades manually. There's too much cruft and too many things that can go wrong on a Windows 10 install. I'd honestly rather clean-install Windows 10. For me, this makes sense for feature upgrades, but I probably wouldn't automate a Windows 7 to 10 migration.
  15. Okay, so at some point when Automate 11 came out, with all of this new patching, I realized a glaring hole. Yes, it's great that it displays this patching compliance stuff, but there's no monitor to say "If patch compliance falls below xx% on System A, open ticket to remediate" so we can take care of the issue. So I spoke with one of the better Automated support folks, and he helped me build an internal monitor for such things. In this case, the monitor is supposed to tell if compliance drops below 75% -but not if compliance equals zero (which can happen for other reasons, so I want a different monitor for that. Here's the overall meat of the monitor: compliancePNG.PNG Here's my problem. The monitor opens tickets as it should; but then the tickets sometimes resolve themselves even when a system is not back in compliance, which is a problem. I want to ensure that there isn't something wrong with the MySQL conditions, which isn't my strong point. If anyone could assist, that would be great, because then I'll export the monitor (once proven working) and provide it here, something I think would be useful for us all. Can anyone think of a reason why this would be reporting incorrectly? Note -I can't guarantee it's incorrect all of the time but it definitely is some of the time.
  • Create New...