Pulling data from a Microsoft SQL Server or any ODBC compatible data source from inside an Automate Script

2020-12-28T15:27:18+00:00January 6th, 2021|

Did you know that it was possible to poll databases / datasets outside of the Automate database? All that is needed is a System DSN (OBDC Connection) on the agent you wish to query from, and you can then reference that in the following script function:On the agent, open the ODBC Data Source Administrator and go in to the [...]

Restrict or prevent an Automate script running during certain time frames

2020-12-28T15:12:10+00:00January 4th, 2021|

Happy new year, everybody!Today I am sharing a cool trick that you can use inside the Automate Scripting Engine to prevent scripts from running if the current time falls between a window that you set. This example can be run on any agent. This can be useful in situations where you say don't want a piece of software to [...]

Free Report – Get a second opinion on your patching

2019-12-10T18:33:52+00:00April 3rd, 2019|

For a good while now I have been relatively cynical of the "100% Compliant" statistic that I see on certain servers in the Patch Manager and I have been considering how best to approach finding problems with patching that were not otherwise being highlighted. I designed this report to follow an important Automate mantra; trust, but verify. This report [...]

RAWSQL Help and Tutorial – A how to, plus an internal monitor example to Detect Hung Servers and run Custom SQL in LabTech

2020-07-29T17:51:19+01:00September 6th, 2017|

The internal monitor referenced in this post can be downloaded here: LT - Offline Servers Custom - Hung Server I've been meaning to do a blog on RAWSQL monitors for a while - so here it is! The initial request is here https://www.labtechgeek.com/topic/4012-internal-monitor-for-over-x-amount-of-failed-logins-in-a-time-period The first request there is attached as a RAWSQL Internal monitor. Extract the .SQL from this and [...]

Diagnosing LabTech Report Center Scheduling E-mail/File Problems – an in-depth Analysis using Procmon, SQL, and Powershell

2017-03-01T09:34:58+00:00March 1st, 2017|

For a long time now, my LabTech has not been able to run scheduled reports. I've had a support case open since August 2016 for this issue. Independent to this, I've recently setup a LabTech Lab at home, a completely fresh install running LT 11 Patch 9, setup with exactly the same configuration of my live environment. I tested the [...]

How many commands do you have stuck executing in LabTech? It’s worth checking!

2016-11-01T01:33:32+00:00November 1st, 2016|

Another useful SQL snippet to post today, used to identify machines where commands are stuck executing. This usually is an indication of a problem with the LabTech service on the machine, but could also mean something more underlying is broken on the client. SELECT commands.computerid, v_computers.computer_name, v_computers.client_name, Count(*) AS NumOfCommands FROM   commands LEFT JOIN v_computers ON commands.computerid = v_computers.computerid WHERE  status = 2 GROUP  BY computerid ORDER  BY numofcommands DESC

Putting Labtech on a diet – working out your “noisiest” agents for Event logs

2017-06-19T02:52:54+01:00October 11th, 2016|

The eventlog table, housed in the back-end database of LabTech is in most cases going to be one of your biggest tables. What most people don't realise is that a lot of the space used in there can often be down to a few machines who have issues that can be logging multiple times a second into the event [...]

Go to Top