Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


bigdog09 last won the day on February 22

bigdog09 had the most liked content!

Community Reputation

21 Excellent

My Information

  • Location
  • Agent Count
    1500 - 2000 Agents

Recent Profile Visitors

287 profile views
  1. bigdog09

    Should we Update to version 2019 ??

    2FA is very important. There's no such thing as a truly "trusted" network anymore. The perimeter is dead and the zero trust model is what you should be shooting for.
  2. bigdog09

    Should we Update to version 2019 ??

    There haven't been any major complaints that I've seen. There are some issues carried over from patch 12 that are still lingering, but nothing new introduced in 2019.2 that we're aware of. The biggest complaint I've seen is a minor aesthetic issue. If your Client/Group list is too long to fit in the view, then there is a visible scroll bar. Functionally it works the same as it always has, but in the past the scroll bar was invisible. When that's the biggest complaint, then it's pretty safe to assume that the patch is fine.
  3. bigdog09

    Should we Update to version 2019 ??

    If you're on, then you're ok. However, installing the hotfix and installing 2019.2 is the same exact process, so you might as well get on the latest considering it's stable and the most secure for the time being. Security flaws are patched in almost every release, so while holding off for a couple of weeks is a smart approach... you should always be willing to install the latest patch once it's been confirmed that it's stable. Especially considering that CWA12 > CWA2019 isn't a major release, just a name change.
  4. bigdog09

    Should we Update to version 2019 ??

    If he's truly on the latest build of patch 12, then he's fine. There was a hotfix released to amend the issue. @Technigogo Automate 12 and Automate 2019 are the same exact product, just different patches. There wasn't a major release, they just updated the patch naming scheme to match the rest of the CW suite. 2019.2 is essentially Automate 12 patch 14.
  5. Thanks @dpltadmin. I've got your posts sourced on the OP now.
  6. bigdog09

    RMM Security Best Practices

    It should be in the wwwroot folder, so most likely c:\inetpub\wwwroot\robots.txt
  7. bigdog09

    RMM Security Best Practices

    Here are a couple of SQL queries to help make sure that your users are set up correctly in Automate. Make sure that all of your user accounts are being audited for everything they're doing. The logs don't take up much space, so it's worth it to audit everything. -- Auditing not set to Everything SELECT `users`.`Name` FROM `users` WHERE `AuditLevel` != 5 AND `users`.`Name` != 'root'; You should limit your SuperAdmins. Like @danrdj said, just because they have the admin title it doesn't mean that they need full access. Run this below to find your current SuperAdmins and make sure there isn't someone on that list that doesn't need to be there. -- Users have SuperAdmin SELECT `users`.`UserID`, `users`.`Name`, IF((BIT_OR(`userclasses`.`Permissions`) & (1 << 0) = (1 << 0)), 'True', 'False') AS 'SuperAdmin', COUNT(`userclasses`.`name`) AS 'Class Count' FROM `users` LEFT JOIN `userclasses` ON FIND_IN_SET(`userclasses`.ClassID, `users`.`ClientID`) WHERE `users`.`Name` != 'root' GROUP BY `users`.`UserID`;
  8. Sure thing. The goal of this thread is to inform people on the state of each patch good and bad. 2019.2 is slightly less of a priority now that they have hotfixes in place, but there are still good benefits that comes with the new patch. I try to source all the issues back to Connectwise statements or detailed comments in this thread. Please feel free to post any 2019.2 in here and I'll cite them on the OP.
  9. bigdog09

    RMM Security Best Practices

    Most people should be using the default. User-agent: * Disallow: / I'm sure several people already understand what robots.txt is and does, but I'll elaborate a bit for those that might be out of the loop. When web robots crawl your site the standard is to first look for <domain>/robots.txt to see if there are any rules that it needs to abide by. This is an industry standard that's been around since the 90s. Some websites use it to prevent certain sections of their website from being indexed online and therefore not searchable in a search engine. In Automate's case we don't want anything indexed, so you'll want to make sure that your robots.txt matches the above text. Granted there are exceptions to every rule, so it's possible that someone out there has a good reason to have a more customized robots script, but I can't think of any reason. This is obviously an oversimplification, so I'll link a more detailed overview below. For more information: http://www.robotstxt.org/robotstxt.html
  10. Sorry for the late response, but @Ban-Hammer is correct. Follow the link that he provided or the link under the Patch name in the OP to download it. Patching a CWA server is actually relatively easy, so I'll add the steps below and edit them into the original post. - Download the patch to the CWA server (patch is linked in the OP or if you're on Slack then open up a DM to yourself and type `!patch 19 2` to get an auto-response with the patch link.) - Right click the .exe and select properties - Click the "unblock" option at the bottom and then click ok - Right click the .exe again and select 'Run as Admin' - Allow the prompt to finish and verify that it says the patch installed correctly - Open the Control Center (it should auto update to the latest CC therefore making you initially log in twice - If not then you need to adjust the dashboard settings to enable that) - When The Control Center loads go to Help > About - Verify that the version installed matches the version that you're trying to install (v19.0.58 (Patch 2) in this case) If you have any problems with any of the steps above then reach out to the Slack community and/or CW support. (Try us in Slack first). Please update to Patch 2019.2 as fast as possible because your server AND agents need to be updated soon to avoid any problems in the near future. The patch 12 hotfix would work the same way, but the stability of 2019.2 is solid enough that I would just go ahead and upgrade.
  11. @jamberston I'm not sure if anyone answered your question in the announcement thread since it's locked, but upgrading to 2019.2 will not affect your XP/2003 machines. That was a bug feature that was introduced in 12.11, but they've since recanted and fixed that in 12.12 and newer. As long as you skip patch 11 and just straight from 12.10 to 2019.2, then you'll be fine.
  12. Can't really justify green lighting 2019.1, but its third production release ( seems to be relatively stable, so it's been moved to the middle of the road category. Safe to install, probably won't give you any fuss, but definitely not one you should assume is trustworthy out of the gate.
  13. Try this: $Path = "C:\inetpub\logs\LogFiles" $Daysback = "-120" $CurrentDate = Get-Date $DatetoDelete = $CurrentDate.AddDays($Daysback) Get-ChildItem $Path -Recurse | Where-Object { $_.LastWriteTime -lt $DatetoDelete } | Remove-Item You can adjust the file path to the log files and the amount of days in the top two sections. If you want to add it to an Automate script to schedule, then use: Function: Execute Script Script Type: PowerShell Script to Exexute: <paste above script with adjustments if needed> Script Parameters: <leave blank> Script Credentials: Run as Local Agent Variable: powershellresults The the current script the variable is pretty arbitrary because it's just going to return 'OK', but you're welcome to make the script a little more verbose to return better results.
  14. I was actually about to link the Executioner script. I haven't seen it fail before, so I'm curious what's going on. You probably know this already, but the magic behind the executioner script works like this. If Automate is installed, then it will uninstall it and remove the folders and reg keys associated with it. Then it recreates those same folders and reg keys with no information in them Finally it restricts the permissions of those folders/keys so that not even SYSTEM has the authority to read/write/delete them What really seems like a head scratcher in your case is the fact that it runs as a scheduled task, so even if by some miracle it was able to auto-install again, the next time that task runs (hourly I believe) it will go through the same process again. It doesn't make sense at all that they would keep coming back. When you notice them in CWA are they showing as online or offline? Online would make zero sense, but it they were showing as offline then it's possible that you have an extremely robust installation script that keeps fighting against the executioner script creating an endless loop of mutilation and restoration. First step I would take is hopping on one of the problematic machines where the executioner script isn't working and check to see if the scheduled task is on and running. The task is called 'CWAutoMaintenance.' If that's not on the machine, then the script did not run correctly on the machine.
  15. What's the end goal here @vulcan4d? I'm sure that there is a better way than the Thanos approach.