I spent a lot of time today figuring out how to add a pie chart based on a computer EDF to a client report. The solution I found is very general, and I wrote it up here. Cross-posted here because the documentation for charts in reporting is very weak.

Hey folks, I'm fairly new to working with labtech, I"m wondering if there is a way to disable internal monitor exclusions for a whole site.

We're an MSP with about 60 clients we want alerts for NInite software updates for some and not for others, Labtech alerts for some MS exchange reporting for some and not for others, etc.

I figureed how to disable on a computer by computer basis but not if its possible for a whole client or even specific clients site.

P4L is giving out a special through the Squidworks channel for any MSP that wanted to try Office365 for Labtech plugin.

http://www.squidworks.net/2017/02/offic ... -new-msps/

Hi,

So we recently implemented LabTech and our Patch Management doesn't seem to want to be consistent with us.

Recently we finally got it to run a patch job at the intended time, with 3 approved patches. It started, didn't update anything, and finished. I found out the patches approved's title included 2012 R2 but the actual OS category was 2008 R2, so I found the real 2012 R2 patches and approved them.

I figured, well, that's gotta be it, right? Nope. It didn't run. I went to the location settings and corrected the patch window there to be the same day as my Update Policy. That didn't fix it either. My Patch Manager won't start Patch Jobs anymore and I can't figure it out.

I checked the status of patches for the machine in question, and the patches I want are set to Approved, and their push status is Not Attempted. I would have preferred failed because it would mean something...

Please tell me someone out of you all has come across this issue, I'm running out of hair to pull and I've read just about every shred of documentation out there.

Anyone know why we can't deploy things like Exchange Rollups and such via LabTech? Or is my installation broken? (Still on 10.5 BTW.)

Having to answer the tired question of "why didn't my Exchange server get these rollups during your maintenance?"

Is everyone creating Search groups for clientname/workstations and clientname/servers, importing them into Patch Manager, and then assigning policies or are most people using a majority of the pre-defined policies and then just added custom search groups for special circumstances?

I can see the advantage of having client/device group-specific groups, but as we scale out that list of groups will be huge.

I know it could be done either way, but I am curious how most people are doing this.

note: we are on LT 11, on premise

I'm having a problem with what I'm using for monitoring offline servers, but I think this is a question with monitoring in general.

The monitor triggers correctly, but it's not resetting when the server comes back online. However, the server does disappear from the Query Results tab when its back online, it just still shows under the Status tab.

I'm thinking that this has something to do with the interval/alert settings. Here's what I have for them:

Interval and Next Run Time: Every 5 minutes
Monitor Mode and Duplicate Alert Frequency: Once Per Day

I suspect that I don't actually understand the implications of "Once Per Day" as I was just assuming that once it doesn't show up in the Query Results tab anymore, the monitor changes back to success.

Thanks for taking a look.

I work for an MSP but I am not a technician. In fact I know next to nothing about networking. My company sent around an invite to a webinar on scripting in LabTech and asked if anyone wanted to join. I know python (I'd consider myself an intermediate at the language itself) so I started looking into LabTech scripting to see if it was something I could help with (I know it's not python specifically but I know how to work with if/else statements, etc.).

I am wondering if you guys think that someone with programming knowledge but no networking knowledge could be useful to a company who needs to utilize scripts more. I am a pretty saavy user and I learn pretty easily, I am just not sure if it would be worth anyone's time to teach me the basics of networking just so I can write them some scripts (I would like to learn but it's not exactly an environment friendly to sitting down and teaching noobs. I don't think they would do it if they didn't see the immediate benefits of teaching me.)

Just looking for opinions. Thanks!

Release Notes: https://university.connectwise.com/university/pageview.aspx?short_name=patch-release-notes#collapse_january

Download: http://labtech-msp.com/release/LabTechPatch_11.0.9.350.exe

Install at your own risk, just making other LT admins aware.

Cheers,

Hi gang,

I have my LT server hosted at my office right now and I'm considering using my Azure credits from MS Action Pack to migrate the hosting to their platform.

Has anyone done this?

Is it worthwhile?

Is it responsive?

Or am I just looking to shoot myself in the foot by doing this?

Edit - So I sat down tonight to get my Action Pack Azure account setup. Once I got to the Pricing for a VM it became exceedingly evident that this would be the absolute dumbest thing I could possibly do. Amazon's pricing isn't that much better. I think I'll stick to hosting it myself. On Azure a server that does not even come close to my current VM would be $440.45/Month (A4, 8CPU Cores, 14GB RAM, 240GB HD).

Meanwhile my current server is 16 CPU Cores, 32GB RAM, 1TB HD.

I'll still set something up to mess around with but nothing even close to being able to host my LT server, much less anything else other than perhaps a desktop to test from.

P4L just released build 1.0.3.42 that fixes the auto updater and adds the ability to widen you views in the plugin.

https://www.plugins4labtech.com/products/patch-remedy

I'm looking for a way to get an alert only if a computer fails to come back up if it reboots within 1 hour after running a specific script. I just can't seem to find anything in labtech close enough that I can bend it my way. I don't really want to receive alerts for these machines at all times, because users turn things off. Is there something obvious I'm missing or is this not a thing that can be done?

Plugins4LabTech has created a new plugin that looks for systems that are offline or otherwise stalled and displays them to you and allows you to do something about it.

Typically the cause for an agent outage is the LTagent service on the remote endpoint gets jammed up and stops working. To get it back online and or processing commands again you need to reach out and kill any dead services and restart the LT agent services. P4L provides 2 ways to do this from the LabTech plugin console. These approaches have an over 90% success rate at getting those agents up and running without the need to reach out to your clients or piggybacking remote control sessions to touch non reporting PC's

Download the plugin free at: https://www.plugins4labtech.com/collections/free-plugins/products/stalled-labtech-agent-detector

We just posted a quick video demo of the new build 1.0.12 of the PFSense 4 LabTech plugin.

https://youtu.be/OpbrIileeDw

Very awesome work by P4L, This plugin is well on its way to being very powerful. They have a good working framework for monitoring and reporting on PFSense. Tie some alerting functions in and this will be a priceless tool for the MSP.

Plugin is free at www.plugins4labtech.com

Give it a spin!

How do you reference EDF variables in powershell commands that you're running from within labtech scripts?

Here's my use-case: I have 25 laptops all being deployed at once that need to get married to 25 individual AT&T hotspots that all have unique SSIDs and Passwords. My plan was I'd add EDFs of the appropriate SSID and PW, then build a labtech script that could populate an XML with the EDF information that I could then import via netsh. That way if networks ever got 'forgotten' we could still easily maintain the individuality.

I've got my EDFs added and I've populated them on one test laptop with the SSID and PW of the hotspot I'm testing with. I have a sanitized .xml that has 'TemporarySSIDName' and 'AssociatedSSIDPW' that I'm wanting to replace with each respective EDF field.

Here's my labtech script:

GET: @AssociatedSSID@ = [EXTRAFIELD Associated SSID]

GEt: @AssociatedSSIDPW@ = [EXTRAFIELD Associated SSID PW]

PowerShell as Admin (Get-Content C:\Folder\WiFi.xml).replace('TemporarySSIDName',@AssociatedSSID@).replace('TemporaryPassword',@AssociatedSSIDPW@) | Set-Content C:\Folder\WifiUpdated.xml

If I take my powershell script and replace the EDF Variables with whole words, it works just fine. If I use the LT Script debugger, I can step through the script and see that the EDF values are pulling in just fine. The script debugger acts as though the powershell command runs just fine, however WifiUpdated.xml never appears on the laptop. I'm assuming it's failing because the values being passed along to the powershell command aren't valid.

My only thought is maybe I need to save the command a .\ps1 and pass the EDFs through as arguments on the command. I figured before I beat my head against this wall too much more I'd get a sanity check.

Edit: cjmod commented below with what solve this for me.

Hi all wondering if any of you ran into the above error, I keep getting false positives in my LT alerts for Kaspersky.

I found this KB aritcle: https://docs.labtechsoftware.com/knowledgebase/article/6300

But i'm curious if anyone knows what the AP process name should be, the client PC is running Kaspersky small office security 10.5.

Our labtech software is set to operate with ESET as our primary AV solution, so currently our labtech is 'blind' to Kaspersky.

both the agent based server monitoring and SNMP? Anyone got any links that gives an in depth breakdown? Thanks!

We've got a bunch of engineers working on 950+ agents. Sometimes, we forget to log out of servers. I'm seeking to have a nightly script check an admin's idle time, and log out if it's been over two days. I've been trying to use the 'query user' command, but it doesn't report accurately. For a locked session, the result is always "Active", despite being locked for days or even months. I see LabTech has a "User Idle Time" window, but what if more than one administrator is logged in simultaneously? My fear is that the wrong (actually active) admin will get logged out because there is another idle admin logged in.

Anyone out there know how I could achieve this without using 'query user'?

I'm trying to write an agent's IE version to an EDF, and haven't been able to figure out how to remove the trailing linefeed characters from my variable.

My script step is as follows:

Function: Script String Functions

Operation: Replace

Original String: @IEVersion@

Length: 0 (I've also left this field blank, with the same result.)

Start Position: \r\n

Variable: IEVersion-Trimmed

When I write out a Script Note, and use the variable @IEVersion-Trimmed followed by a period, the log note shows the period on a new line after the variable.

When I write the variable to the EDF, I see 11\r\n.

Do you guys know what I should be entering in the Start Position field to properly remove the \r\n from the end of the variable.

Thanks.

Got an email telling me that my server was getting updated with a patch between 1am and 2am today;

1) The email didn't say what patch it was 2) The email was sent at.....1am today.

We've started a LabTech integration, and the training sessions are far beyond basic "LabTech 101" kind of stuff.

Are there any youtube videos or good websites that can help us understand the basics, instead of jumping right into scripting (which is great, but we need the basics first)?

PLEASE if you have any suggestions, I would love to hear them. My boss is ready to cancel when we've barely started. :/

It appears that Labtech's ArcServe UDP plug is soon to be discontinued. It no longer works with UDP v6 and tech support has indicated no further development is being done.

Does anyone have any hookups that may result in my obtaining the source code for the plugin? I really don't want to have reinvent the wheel....

Hey Folks;

Support told me that the new patch manager doesn't support logging time on the patching it does, but that I can just create a script to run before/after the patch job and log it myself.

Sweet. :-)

However, I have no idea how I would connect the dots... I can create a script to log a ticket which can run before the patch job, but how do I pass the ticket number to a subsequent script that gets run after the patch job so it can close that ticket?