Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Oh alright, thanks. The old AV is from another MSP service that can be told to uninstall itself so the uninstall isn't an issue
  3. Can you upload just the powershell piece of this without the need for connectwise automate I prefer to handle this manually or include it in the zip.
  4. Today
  5. Use the MSI, transfer it to the agent, execute the MSI with: msiexec /i "C:\Full\Path\To\File.msi" /qn It's up to you to write an uninstall script for any existing AV that may be present, and you may want to do that first before installing a new AV.
  6. We install almost all of our extra apps with Chocolatey, seems to work very well. I can export the install function and the a sample script that passes the various variables like app name.
  7. I have entered the subjects "NOEMAIL" for all my monitors that I do not wish to receive emails for, and have entered |!NOEMAIL in the ticketing config subject monitor, but still continue to receive emails for these monitors. Where am I going wrong here?
  8. Yesterday
  9. So I am implementing both Automate and Trend Micro Corp II AV (wfbs) and just thought I would see if anyone has an install script for the Trend Micro Corp II AV. If not I'm sure I can figure it out. Thanks
  10. It went through fine without the quotes on MaraiDB, but I noticed it highlighted in SQLyog so I figured I would mention it, in case there are potential issues with other mySQL versions.
  11. Ahh thanks man. This is fixed. On the Name one I usually do `Name` but when I SQLSpy'd the inject for a monitor from Automate it was just Name and not `Name` so I just directly copied/adapted it /shrug
  12. Insert INTO groupagents ( GroupdID ,SearchID ,Name The SQL statement has a typo on GroupID. Might also be good to add quotes around the Name column (`Name`).
  13. Yeah @HickBoy it's sounding like everyone hosted isn't able to run this...weird. Anyway, adding that comma before the group ID will not work...that group ID is the first value so would be no comma since the comma is the separator to define multiple different values for different columns. Okay @Namik make an EXE monitor and use this line... "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -command "& {(new-object Net.WebClient).DownloadString('https://raw.githubusercontent.com/dkbrookie/Automate-Public/master/CVE/CVE-2019-1182/Powershell/CVE-2019-1182.ps1') | iex}" See the rest of the settings here in this screenshot: https://gyazo.com/208dd0394e75eef7ec202553da7a126f Nice! Will test this out, thanks @chris_bb! ❤️ you bigwoof @bigdog09 -Rookie
  14. Last week
  15. I am also unsuccessful at importing. Can't see the monitor anywhere although it looks like it is importing. I am hosted too. Did we loose the ability to import sql? Had no problems before.
  16. FYI, I was unsuccessful at importing the SQL statement. Could you please provide some screenshots of the actual monitor so I could manually create it instead as I am having trouble deciphering some of the sql allowing me to recreate it. I also tried modifying the following line with no luck. /*GroupID*/856 /* 856 is the group ID for "Service Plans\Windows Servers\Managed 24x7" */ to /*GroupID*/,856 /* 856 is the group ID for "Service Plans\Windows Servers\Managed 24x7" */ NOTE: I am on hosted automate w/CW and no longer have direct access to SQL to view any errors.
  17. Hey guys and gals, We have been using Automate for a couple of years, but haven't really 'dug-in' to learn how to properly setup our monitors, alerts and ticket emails. We may or may not have changed a bunch of the default settings when we were first implementing Automate... not really sure at this point, but we are just starting to (try to) make use of the ticketing system. There are tons of monitors that send emails for EVERY SINGLE ticket created and we can't seem to weed out the ones that are emailed to us by clients and the ones that were created from the Agent. Is there any way to have the monitors create tickets and NOT send emails? I have looked at the alert templates, monitors, and ticket configurations - and have read a lot on here, and a lot of useless documentation to no avail as to where to even start. Any help would be appreciated!
  18. Very nice! My only concern is that Get-CimInstance doesn't appear to be supported on earlier Powershell versions, which caused the script to fail on some of my Windows 7 machines. $osVers = (Get-CimInstance Win32_OperatingSystem).Caption Can be replaced with $osVers = (Get-WmiObject win32_operatingsystem).Caption
  19. Hello, We implemented Automate recently to use it internally, and segmented our different locations as different clients in order to organize the groupings a little better, but in hind sight, it appears that this will create a few hiccups here and there, including the following issue. I am customizing a copy of the Ticket Summary report so it will show the same ticket data, but from all clients in one report so we can see all our ticket numbers in one report. I have been able to change most or all of the data binding fields to a data field that appear that they will be pulling overall numbers, instead of based on each client. My problem, is the numbers don't match up when running it this way, as opposed to the sum of each set of numbers from all clients. When I click Print Preview, I also still get the Document Map tab on the left, with the list of clients. Is there something I need to change on the detailBandClient section, or perhaps replace it with a different band and copy all the objects to the new band? If there's any additional info you would like to see, please let me know. I'm still new to the Report Designer, so I'm not sure which direction I need to go to solve this yet. Thanks, Andrew
  20. i just have a quick question and couldn't find the answer within the available Blue Prints on the Connectwise University site.. Attached is a screen grab of the policy settings when Daytime Patching is enabled. What is the purpose of the highlighted section. Initially i thought it was a "reboot" prompt, but I'm not entirely sure and want to make sure I add the relevant info to my policy. Thanks.
  21. Waking up to a love letter from @rookie. I knew today was going to be a good day. FYI - Rookie is a hidden gem in the MSP community. Slide into his slack DMs with an Automate related love offering and he's bound to return the favor. 😉
  22. Thanks for the reply. Which agent version are you currently running?
  23. Very nice! Look at you sharing some secrets with the world! 😉
  24. Hey all, I've been active in the community for a few years now but have never really posted in the forums. I've put together a script/remote monitor to address the latest RDP vulnerability from Microsoft and figured I've learned enough from the MSPGeek community it can't hurt to give some back. This first link is a SQL inject that will create a remote monitor on your "Service Plans\Windows Servers\Managed 24x7" and "Service Plans\Windows Workstations\Managed 8x5" groups. What groups it installs the monitor on are just defined on the inject with the GroupID so if you just look at the inject it's easy to change that GroupID to whatever you want before you run it. !!!WARNING!!!! - You're running a SQL inject on your DB...this can be dangerous, proceed at your own risk. Read through the inject, make sure you're comfortable with what it's doing. This monitor is also live pulling a powershell script from MY github. This means if I decided to have a bad day and change the powershell script in my github to something malicious then I could effectively run my malicious code on ALL of your machines. I'm not malicious, but ya know...be smart, be safe! Feel free to host the powershell script at your own location and just swap the URL on the monitor. Lastly, I've tested this on several machines in my environment, but that doesn't mean there can't be an issue I haven't ran into yet. If you find a problem, let me know so I can fix it! Download Links SQL Inject: https://github.com/dkbrookie/Automate-Public/blob/master/CVE/CVE-2019-1182/SQL/CVE-2019-1182_Remediation.sql Powershell: https://github.com/dkbrookie/Automate-Public/blob/master/CVE/CVE-2019-1182/Powershell/CVE-2019-1182.ps1 Script breakdown... This script is outputting either !ERROR:, !WARNING:, or !SUCCESS: with details on the state of the install process. If you set the monitor alert template to create a ticket (I have it set to Default - Do Nothing so just change to what you want) it will output the Powershell results right into the ticket. The keywords from the script output above are to use in a state based remote monitor in Automate so this will go through what that looks like briefly. The script checks the OS of the machine and figures out the correct KB number it needs to have installed to patch this vulnerability. Once it finds the right KB, it checks to see if the KB is installed or not. If it's not installed, it will install it with no reboot so this is safe to run mid-day. That means right from the monitor CHECK it is actually installing the remediation, so there is no separate script attached. The patch download/install is all self contained in the monitor check itself. !FAILED: will only output if the machine is eligible to receive the CVE-2019-1182 patch and something in the script actually failed and needs attention !WARNING: will only output if the machine is not eligible for the CVE-2019-1182 patch. The reason I've chosen the all managed servers/workstations groups is so you can highlight all of the machines quickly/easily in WARNING state that do not have this patch available to them. This would be a good time to use this as leverage to get your clients to upgrade some machines !SUCCESS: will only output if the patch has been verified to be installed Monitor breakdown... The monitor will be named "CVE-2019-1182 Remediation" The monitor runs every 4hrs but you can change this to whatever you want FAILED state: Looks for the keyword "!ERROR:" from the powershell output WARNING state: Looks for the keyword "!WARNING:" from the powershell output SUCCESS state: Looks for the keyword "!SUCCESS:" from the powershell output Enjoy! -Rookie
  25. @DarrenWhite99 Apart from activating this monitor, activated "LT - New Computer Detected* ". I receive a list of every device ( phones, some network devices and some number) how can i explain to this monitor to return only ( computers) which has been connected to the network.
  26. Hi Cubert. Yes, we use the SQL Query Analyzer a lot, specially now as the RDP access has been removed by ConnectWise. But this is only for queries, as you can not use this for altering the CWA tables. Which we also like to do, specially when occasionally something gets wrong in the tables. Is there going to be an update or new tool, which gives us this functionality. SQL Update Statement possibilites ! greets, Thomas
  1. Load more activity
  • Create New...