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, and as part of a request here: http://www.labtechgeek.com/forum/posting.php?mode=reply&f=2&t=3769#preview I thought not was a good time. The first request there is attached as a…
|
1 2 3 4 5 6 7 |
SELECT searches.*, computers.name, sensorchecks.name AS Test FROM searches LEFT JOIN computers ON computers.computerid = searches.computerid INNER JOIN sensorchecks ON searches.searchid = sensorchecks.sensid WHERE computers.name IS NOT NULL ORDER BY NAME ASC |
That’s how! This SQL query will bring you back a list containing all the groups a computer is a member of, including the SearchID that is joining them to said group.
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…
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
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…