Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. 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.
  3. Yesterday
  4. 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!
  5. 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
  6. 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
  7. 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.
  8. 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. 😉
  9. Thanks for the reply. Which agent version are you currently running?
  10. Very nice! Look at you sharing some secrets with the world! 😉
  11. 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
  12. @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.
  13. Last week
  14. 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
  15. You realize you're asking the question wrong? The question is how can you do it from ONE computer from the backend. Once you can do that, you can do it from all computers with some tweaking. Step 1) Hit the google "How to clear browser cookies from command line" Step 2) Test in Labtech CMD Prompt and generalize for all computers Labtech Automation is meant for those who can approach this type of out of the box thinking, the more you apply yourself to it the easier it'll be to think that way.
  16. Via labtech any ideas how I can delete a particular cookie from firefox and Internet explorer on a lot of computers? If not an individual cookie how about clearing the cache/cookies from all of them? Thank you
  17. An alternative to the VBS - Uses the LabTech PowerShell Module (LTPoSh) https://slack-files.com/T0SD04DSM-F8RA68F53-da5f31ba6a Just set the server and locationid on lines 9/10. The locationid can also be specified from the command line as a parameter.
  18. Hi, Here is a thought, you may need to try changing the device type manually and see then, but to be Automate I must say that either Labtech should identify type or at least to edit and complete the probe template, I am new in Probe Templates, I hope I could figure them out, I think these templates will help me much more, as of you too, Adam
  19. @timwiser I've been banging my head on this script for a little bit... it installs, but then like @rattrap17 says the server key doesn't work (I get a failed checkin and sleep combo for eternity). Support says my server password is no good. I tried @rattrap17's method of grabbing the password but now I get reports of: LTService v190.161 - 8/14/2019 11:10:45 AM - Error running SQLite command - SQL logic error or missing database too many terms in compound SELECT::: LTService v190.161 - 8/14/2019 11:10:47 AM - Send Info1LTSVC - Invalid Operation. Duplicate Key found. Key:i::: Any help would be much appreciated.
  20. I haven't seen this specific scenario before and we have about 20 CentOS servers. We used to have problems with the agent just stopping completely and needing to be restarted. We haven't had this problem since the latest agent updates though.
  21. My coworker was testing our walkthroughs and ran the Agent_Uninstall.exe to cleanup an install and shortly afterwards attempted to reinstall the Labtech / Automate Agent but nothing would happen. This occurred on two servers in our lab. We initially tried multiple things and found that the .msi would install without any issues but the .exe would not. From there we ran Agent_Install.exe /Log log.txt and output what was happening into a text file. The log outputted the following error - System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. Further down in the message i noticed at RemoteAgentBootstrapper.RemoteAgentBootstrapper.setupSecondaryAgentMsi() which made me realize that the .exe was just installing an .msi with parameters. We started looking in C:\ProgramData\Package Cache\ and found about 4 folders. 2 that had LabTechRemoteAgent.msi and 2 that had LabTechRemoteAgent.exe. One of the folders that had .exe also contained a state.rsm file. Just as a hunch we moved the state.rsm file to the desktop and then the .exe started installing normally every time afterwards. I initially looked here - https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/040/060 but soon realized that it was not going to help us. I hope this helps others that face this issue. ~Sean K
  22. Its complicated. You can create Internal monitor set and check Window is activated or not. You need only Event ID to get the status
  23. Is %userdomain% available? \\domainname\netlogon should work just as well as \\specificdc\netlogon A possible option to force the variable to be processed is to just use a command line copy with Shell As Admin. The shell will definitely expand the variable if the File Copy As Admin function doesn’t.
  24. @Dayrak, you need to identify which group is controlling the monitor (All Agents?), open the group, select the Computer tab, then the Remote Monitors tab. Select the monitor from the list at the bottom of the window, edit the settings and then hit Update.
  25. Has anyone found a solution to this that does not involve all that manual re-entry? Regards
  1. Load more activity
×
×
  • Create New...