Free Report – Patches installed in the last 30 days on all agents

2017-11-08T02:34:19+00:00September 13th, 2017|

This report was requested in the LTG forums and I can definitely see the benefit in it. The report will display any hotfix that has a finished date in the last 30 days. The report should not ignore empty agents, meaning that if you have an agent in this report and it is blank it means it hasn't done [...]

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

2018-09-24T23:51:53+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 [...]

Adding a LabTech/CWA Role Definition for Bitlocker

2017-07-19T00:26:07+01:00July 19th, 2017|

A task for this morning that I thought I'd share the outcome to! I like having things in roles, it makes detecting them and scripting with them a lot easier. [crayon-5ed0c2084a37a786714760/]  

Computer Audit with Installed Software Report

2017-11-08T02:36:25+00:00June 29th, 2017|

This report was requested on LabTech Geek's Slack. It displays a detailed overview of a computer, with details about the computer's identification, hardware information, latest performance, service history, software summary, overall drive information, network information, and software. I hope you enjoy. Now before you download this, the report is provided free of charge for your use at your own risk. I [...]

Report – Remote Access Audit grouped by User

2017-11-08T23:46:33+00:00June 20th, 2017|

This was something that was requested in the LabTech Geek Slack. I have put together the basic data structure, it will need to be "prettified" but it's a good starting point with the data, relationships and bands built for you already. Please ensure you manually verify this, it is provided as is and untested. Audit Remote Access - Group [...]

Remove return characters \r\n from ConnectWise Automate/LabTech Variables

2017-05-25T14:47:51+01:00May 24th, 2017|

A simple method when these are plaguing your script. It hit me again to day in the form of a script that wasn't doing what I expected, it wasn't until I looked at the output in a multi-line view did I see it was throwing in a return character in the middle of a command. You can fix it [...]

LabTech System Variables not working following a server migration

2017-05-12T22:46:36+01:00May 12th, 2017|

I saw someone post this resolution in the LabTech Geek Slack and thought it was worth posting! This occurs because triggers that are in the SQL database sometimes don't get transferred across, these "trigger" on each add or update of a row and add variables like LTRUNBYUSER. The resolution: -Stop IIS -Stop LabTech Database Agent service -Open SQLYog (from [...]

Patch Compliance Report – Including Compliant Devices

2018-06-28T23:45:55+01:00April 20th, 2017|

UPDATE 28th June: New report released to fix changes recently made to views and the template. Please re-download and re-publish. I have seen this requested in numerous places, and ConnectWise asked people to put in a feature request so I just decided to make one and release it. I have modified the current report to include a new section [...]

Advanced Scripting – Debugging and dumping all available variables in a script to a log

2017-03-28T01:55:24+01:00March 28th, 2017|

For those who have developed LabTech scripts before, especially complex ones, it's sometimes very difficult to debug scripts or even find the certain name of a variable you are looking for. Sometimes you will know the actual value from a script that you need, but not know the variable name. This is further complicated by all the variables not [...]

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 [...]

Software Install/Uninstall Report; comply with PCI-DSS and other well known standards

2019-11-30T21:27:19+00:00February 26th, 2017|

As I'm sure people who are working in the MSP/IT Sectors will agree, there are a lot more compliance requirements nowadays. A requirement I have seen a lot in most security standards is a process to review and record software installed/uninstalled on a machine - this report helps with that. The report uses data stored in LabTech to pull out [...]

Report Center – Patching Compliance Report not running

2017-02-26T17:02:40+00:00February 26th, 2017|

This has happened to a few people. If you are running the report and it is empty, it's highly likely that your patch calculations are not running daily. There are two ways to get these running: Go into Help > Server Status and click here: Note, if you hover over this it will tell you the last time it [...]

Problems with permissions and creating a custom view for reporting

2017-03-28T02:04:59+01:00November 29th, 2016|

If you've created a custom view that you are using for the report centre and it is not working on the report, throwing errors like: "Error loading report data" or "Error loading datasource" or maybe any error relating to permissions, then you should make sure that the name of your custom view is prefixed with a v_ otherwise you [...]

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

Load More Posts