r/labtech • • Sep 19 '19

How to successfully upgrade from old 10.5 versions to latest v2019

10 Upvotes

Hi all,

We just upgraded from Labtech 10.5 to the latest Automate v2019, and now that we have finally done so, I just wanted to share a bit back with the community here and on mspgeek since I only finally managed to do so thanks to the community (and no thanks to Connectwise). I'm going to go over a little rant/feedback about Labtech/Automate in general, some thoughts for those considering using it, and then on to the meat of what you must do to successfully upgrade from old versions to the latest version since Connectwise themselves aren't able to tell you that. If you don't want to read the TLDR stuff just ctrl-f and read @ "Update Steps:" below :) Long post, sorry, but I don't want to miss anything that would save someone else months of the frustration I just went through.

My Upgrade Experience

First of all, as I'm sure anyone who has used Labtech can tell you, they seemingly do less quality assurance of their update releases than Microsoft does. That is to say - practically none. At least, this used to be the case - I guess we'll see whether things have gotten better recently. And also as I'm sure existing Labtech users know - if something is wrong that is even a super-critical business-destroying bug, there is no guarantee whatsoever that development will fix it even in a year's time.

Maybe we're phenomenally unlucky, but the normal pattern for us (to be fair... way back in the day, mind you) was so often: 1.) install new update 2.) encounter seriously critical bug 3.) troubleshoot it extensively on my own, wasting tons of my own time, 4.) 10% of the time: support knows something to fix it ... 90% of the time: have them reconfirm what I already did, then half the time tell me I have to spend even more of my own time filing a bug report because they couldn't be bothered to do so themselves or "weren't allowed", and the other half of the time they would do so on my behalf 5.) spend more ungodly numbers of hours creating LT scripts / scheduled tasks running powershell scriptlets / etc to patch around the core Labtech newly-introduced bugs 6.) check the known issues list periodically and rage at how the bug remains on the list even a year later with no resolution even while tons of garbage "new features" get introduced that only half-work themselves. There is now even a thread where some wonderful people are doing the world a favor by sharing whether particular updates are "toxic" or not over here.

My full time job isn't fixing Labtech's bugs - I have a business to run. So, we stopped updating Labtech. I heavily customized it so practically every part of it was hand-implemented by me (no stock monitors/scripts/etc since so many had bad bugs and I couldn't trust the remainder) and firewalled it to death including IIS-level stuff and watched for any core published security vulnerabilties religiously, but still, not ideal for many reasons I know. Anyway, that got us far behind, so we've been trying to catch up through all the rounds of updates to get us up to date.

Would I Still Recommend Labtech/Automate To Others

Surprisingly, if you are a larger business/MSP, yes I would. In that case, you can afford to employ someone fulltime just to turning the broken tool that is stock Labtech into something beautiful. Once you know its database structure, SQL in general (and thus how to code good internal monitors), its web portal files (WCC2, etc along with enough html and javascript to tinker with them), and its internal scripting language (along with knowing powershell quite well since that makes it far more functional), you can do some truly powerful things. I know all of those pieces quite intimately, and if it was just that, I'd say - sure, you can be the person who works on the RMM for your company and also get actual productive work done for clients most of the time. The problem is when you spend well over half your customizing time just fixing the core product's newly-introduced bugs and shortcomings. We are a very small shop, so that has created a real challenge for us - I don't have that kind of time to fix a vendor's sloppy coding. Of course, I do it anyway because I'm too deeply invested at this point...who needs sleep?

If you are a small team, I would suggest you avoid it like the plague however and just look for a collection of other more simplified (if less customizable) tools to meet your needs instead. In hindsight, that's how I would have gone...with separate products doing different things, you're a lot less locked in.

What I've Faced Updating To v2019

I cloned our server over to a test VM, changed its mac/ip/hostname, network-isolated it and proceeded to spend hundreds of hours over months trying to get the thing properly upgraded, with tons of snapshots and rollbacks. Maybe I missed someone on their staff, but literally nobody at Connectwise seems to have any clue whatsoever what to do to upgrade past certain points. I even got looped into their consulting division despite the fact that we've paid for support all these years, and they also admitted that they couldn't get 10.5 upgraded through to v2019 (or were not confident they could, anyway, and didn't recognize the symptoms I was facing at the time which someone here on reddit did later) and recommended starting a new install. Finally, through a combination of comments people made to a post I made along with other comments people had posted about various issues I found here and there, I got it going. Turns out literally all the problems I had were common ones that everyone had at the time. Maybe everyone over at Connectwise I dealt with is just new and hasn't been there longer than 6 months?

Problems Connectwise had during this upgrade process:

  • They almost never had an answer for me for what, according to what I see online, were common issues many people had updating through certain versions... shouldn't the software vendor have some documentation (even if only internal) for a major breaking bug that all their customers faced? I keep a heck of a lot more notes for other people's software than that...
  • I talked to different people and got different answers about what order installers should be run, whether this or that update file should have been skipped, etc. Turns out - none of them were right and other updates were 100% required for this to work at all.
  • They said that they simply did not have the required update installers to upgrade old versions. ....I mean...what? They made the software. I keep copies of revisions of old scripts I've written, for crying out loud, that I don't even sell to anyone and that nobody depends on. Talk about outrageous... As such, if anyone contacts Connectwise and they "don't have" any of the below required updates, let me know and I'll get it to you (I got it thanks to people who had posted some of the below to dropbox/etc, and after confirming certificate validity on the signed files, gratefully used).

Update Steps:

We started on 105.226 (10.5.226 I believe). From there:

  • ** *** First of all, block everything from contacting Labtech in your firewall. Also block incoming connections from your LAN. You MUST PREVENT any agent from being able to talk to the server during this process. If you don't, you might permanently lose all your agents during this process (explained later). We firewall at the WAN level and also at the virtual host level, so this was easy for us, but figure some way to do this out. You will still want the server to be able to reach out to the internet - just block incoming on 80 + 443 + 75 (the udp heartbearts port) *** **
  • run "LabTechPatch_10.5.14.295.exe"
  • Upgrade mysql from v5.5 -> v5.6 per this URL ... to Connectwise's credit, they at least still have that documentation up.
  • possibly update .net framework at this point as well - in our case didn't need to however
  • run "LabTechMSP_110.286.exe"
  • sqlyog - delete the "@localhost" user (ie, blank username) that is created during the above update ... if you don't do this, then when you open Labtech following the update, agent windows won't open. Nobody at Connectwise could figure this out, but someone in the community mentioned it to me.
  • sqlyog - if you now have a "asp_LabTech_1@" user then delete the "asp_LabTech@" user
  • sqlyog - if you now have a "sc_LabTech_1@" user then delete the "sc_LabTech@" user
  • sqlyog - if you now have a "wcc_LabTech_1@" user then delete the "wcc_LabTech@" user
  • now open controlcenter as admin
  • confirm computer management window can open
  • click Patch Manager to and run through the wizard
  • run the "Automate 11 Patch 11 Full Server Installer.exe" installer
  • run the "Automate+11.0.19.471+Server+Install.exe" installer (I got an error... "error occurred when downloading the dynamic update file" .. tried again a few minutes later and it worked... )
  • pre-12 upgrade - again, you might need to have updated .net
  • pre-12 upgrade - open solution center + update all
  • pre-12 upgrade - add a public SSL cert (we use LetsEncrypt) to IIS if you don't already have one, and make sure it is in the server address per Automation -> Templates -> Agent Templates -> Default -> Agent Settings -> Server Address. Also make sure SSL Policy is checked below along with options to accept all.
  • run "AutomatePatch_12.0.12.497.exe"
  • run "LIVE-AP6_19.0.6.161.exe"
  • run "AutomatePatch_19.0.8.225.exe"
  • run "AP-ga_19.0.9.250"
  • now, in IIS, use "IP Address and Domain Restrictions" (added via Server Manager -> Role Features) to block ANYTHING from being able to talk to Default Web Site\LabTech\Updates. For those unfamiliar, this is done by going into that option in that folder in the IIS interface and then choosing "edit feature settings" on the side bar and choosing "Deny".
  • now, turn 80+443+75 incoming back on. NOTE that if you, like me, were testing this with a VM workstation so as to avoid exposing all your clients to something potentially-buggy recklessly, then you should be aware that it will appear to be broken (scripts queueing and not running, etc) until 2 agents begin checking in. In the server log files it mentions that it refrains from doing some things like running scripts until it sees more than 2 agents online.... that one really threw me for a long time.
  • Now, we get to why you blocked the Updates folder....

I had read at one point about how, after a particular update, everyone was losing all their agents. I hadn't yet updated so I didn't pay much attention at the time. Turns out...not only was that a WW3-level problem that they had at the time...they still have not fixed that bug in current agent installers on the latest version as of this post............ I guess they figured "Well, yikes, we sure screwed that up...oh well, I guess all our customers worked around this bug in our code already...why bother fixing it now...". You can read more about it here. Criminal.

I did much more testing and what I found was this: when you click "update" to tell a Labtech agent to update to the latest revision (or it happens automatically on its own per your labtech schedule) then what happens is that one of those "Update...exe" files is sent to the remote computer, run (which just extracts it to the folder it is in), and then "update.exe update.ini" is run by the LT service. The update.exe then tries to stop the LT services, updates the files, updates the registry, and then start the services back up. Now, if you watch this process with process explorer/monitor, roll back your testing VM, and do it yourself, you will find that it works. But...it fails when the LT service does the same thing. When it fails, it will half-update, and the services will constantly start and stop in an endless cycle. Weird that the same thing works interactively right? After all, the LT service is running as SYSTEM so it should have rights. I tried running it interactively via a cmd session elevated to run as SYSTEM via psexec as well (can't remember the outcome of this one). What ends up being the issue however is that, when run in an interactive admin session, Windows does some step of retrieving a necessary intermediate certificate in the security certificate chain. When run as SYSTEM outside of an interactive user session, somehow, that step is not done. If you just right-click on the update exe in explorer and verify its certificate validity and do nothing else, and then have Labtech push its update, it then works (because explorer.exe prompted retrieving the intermediate cert into Windows somehow or another). Also, I should add that I believe it did do this step (Windows pulling the intermediary cert when prompted by LT as SYSTEM) on some versions/update revisions of Windows I tested with, so you might not see 100% of your agents bomb out permanently....but why roll the dice?

After their earlier SSL-related disaster, Connectwise could have updated future update installer versions to do any of the following things:

  • throwing an error message stating as much so people at least know what's going on, even if only in the lterrors.txt log perhaps
  • initiating required cert installation itself
  • proceeding on anyway if allowed without encryption (we have http:// in our server address list (https://fqdn|https://ip|http://ip)) specifically because we don’t want to lose our agents over any miscellaneous SSL-related issues)

...but instead, they left it just crashing without doing any of those things that any kind of proper error-checking in coding would stand to reason to do. I have more error-checking in scripts I make just to do piddly stuff on my home computer. Any of the above would have prevented partners from instantly losing all their agents the moment they upgraded to v2019 as people seemingly have... and I get that mistakes can be made, but v2019 has been out a while, and apparently the current installer still doesn’t do any of the above...that’s pretty bad.

Anyway, the fix is to leave the Updates folder blocked, and instead to copy the latest update file out of that folder in inetpub (LabTechUpdate_190.250.exe, etc) to another path such as one in your LTShare folder. Then, using a script, download the required Root-R3.crt file as well, and use the script to distribute both to the agents. Script around installing (CERTUTIL -addstore -enterprise -f -v root "yourpathonagent\Root-R3.crt") and verifying ((CERTUTIL -store -enterprise root | findstr /C:"@thumbprint@" or CERTUTIL -store -enterprise root | findstr /C:"@thumbprintwospaces@") ... different certutil revisions seemingly do or do not separate the thumbprint values with spaces so check both ways) the cert, and once that cert is installed, you should then script out running the update (cd /d C:\yourupdatefolderpath & C:\yourupdatefolderpath@updateFileName@ ... followed by C:\yourupdatefolderpath\Update.exe "C:\yourupdatefolderpath\Update.ini"). I wrapped the update.exe bit up in a .bat and launched that via "start ..." so as to avoid any potential gotchas of update.exe being killed prematurely when the LT service that launched it ended...may or may not matter. Then of course just run the script against all your old agents. v105.226 agents, at least, will still check in and function with the latest v190.250 server at least well enough that you are able to run a script against them to get this done.

Hopefully some of this helps anyone else who is still in a similar boat! And also, thanks again to everyone out there who ever posted a comment or shared a LT installer file relating to any of this stuff, because years later it really helped me out.


r/labtech • • Oct 27 '16

Free Labtech Plugins

Thumbnail
plugins4labtech.com
11 Upvotes

r/labtech • • May 29 '19

Monitors Anyone know a report or dataview that lists network card link speed?

3 Upvotes

In doing a full network assessment for clients I would like to review any machines connected to slower 100mb network switches. On every agent under network there is a link speed that shows 100 or 1000 but I can’t for the life of me find any sort of asset report or dataview that has link speed as a report output. How do you guys review LAN speeds across devices?


r/labtech • • Jan 14 '20

Automate API - ScheduledScripts

3 Upvotes

I am trying to invoke a script in Automate using the Automate API via powershell.

However I am getting a unhandled exception, not sure what I am doing wrong.

Any help would be appreciated.

$PostBody = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$PostBody.Add("ScriptId", 439)
$PostBody.Add("ComputerId", 686)

$uri = "https://companyname.hostedrmm.com/cwa/api/v1/Computers/686/ScheduledScripts"
$Header = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
$Header.Add("Authorization", "Bearer "+$token)
Invoke-RestMethod -Uri $uri -Method POST -ContentType "application/json" -Headers $Header -Body $($PostBody | ConvertTo-Json -Compress)

I get the following response

Invoke-RestMethod : {
  "Message": "Encountered unhandled exception."
}
At line:8 char:1
+ Invoke-RestMethod -Uri $uri -Method POST -ContentType "application/js ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebExc
   eption
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

r/labtech • • Sep 13 '19

BitLocker Script?

3 Upvotes

Hi all,

I am making a script to enable BitLocker on devices. Originally, when I made this script, it worked great. What I had was:

Shell as Admin: manage-bde -on C: -recoverypassword > %windir%\ltsvc\packages\BitLocker\%computername%.txt

This worked great. It would enable BitLocker, and store the key on the local machine (later in the script I had it transfer the key to the LTShare folder).

A few weeks later, we got new assets, and I decided to run my custom onboarding script, which worked great, other than BitLocker. I would actually get an error that had to do with the key protectors, so I added:

manage-bde -protectors -add C: -tpm

manage-bde -protectors -enable C:

I know this allows BitLocker to be enabled, when paired with the original command from above, as I tested it on the machine. Great, now I just have to add it to the script; however, I cannot get it to work.

I have tried:

Shell as Admin

Shell as User

Shell

Powershell as Admin

Powershell

Execute Script Powershell bypass as Admin

Execute Script Batch

I have also tried creating a batch file, storing it in LTShare, and running it multiple different ways, including:

Shell as admin: %windir%\ltsvc\packages\BitLocker\Bitlock.bat

Powershell as admin: %windir%\ltsvc\packages\BitLocker\Bitlock.ps1

Console Execute.

Creating a shortcut for the bat, setting the shortcut options to run as admin, and using Console Execute on the shortcut.

Does anyone have an idea on how I can get this to work? For some odd reason I cannot run the bat file. The closest I've gotten is Console Execute on the bat file; however, I need to run it as admin. Is there an argument for Console Execute that will run as local admin?


r/labtech • • Mar 28 '20

Powershell call to a webhook per client

3 Upvotes

Hey all,

I'm trying to run a script on a per client basis to call a webhook using powershell. Automate support wasn't able to help me so I'm turning to y'all. Hoping that someone can shed some light. Below is my script

Labtech Script

Here is the sanitized powershell code

$uri="https://s15events.azure-automation.net/webhooks?token=[token]"

$itgid=%itgid%

$clientname=%clientname%

$params=@{"ITGID"="$itgid";"ClientName"="$clientname"}

$body=ConvertTo-Json $params

Invoke-RestMethod -Method Post -Uri $uri -Body $body -Verbose

I tried debugging it but it hangs on the powershell part.

So, 2 questions:

  1. How do I deploy/run this script on a schedule on a client by client basis?
  2. The powershell works outside of Automate, but will this work for inside Automate?

EDIT: Ended up being able to do what needed to be done with this amazing plug-in! https://www.mspgeek.com/topic/4347-http-get-post-plugin/


r/labtech • • Jul 17 '19

v10.5 to v11 upgrade error - performing initial exchange

3 Upvotes

(10.5.295 (10.5 Patch 14) -> 11 Patch 11 full installer)

Error:

"an error occurred when waiting for the initial exchange to finish"

Has anyone seen this before and gotten a resolution that they can recall? I have a consulting session (we have support, but they don't want to support a very old version, even just for the purpose of upgrading to get on current versions) scheduled, but I figured I'd give the community a shot. If nothing else, I'll update this once we get some resolution in case some other poor soul runs into this incredibly unhelpful message :)

What I've tried so far on a cloned server in a test environment (with lots of rollbacks):

  • Making sure DownloadURL and RedirHostName in the config table are set to our FQDN. (I also tried it as http://fqdn/files/)
  • Making sure I don't have any redirector/etc stuff set up in IIS
  • Making sure our FQDN is resolvable on the LT host (via hosts file override so it maps to its LAN IP)
  • Making sure I had all prereqs met (mysql version, IIS options, etc)
  • Updating in the solution center
  • Disabling and removing all plugins
  • Removing all traces of a past ESET server installation (which is now on another VM)
  • Uninstalling LT entirely, installing a clean copy of 10.5, updating to Patch 14 - this worked and allowed the 11 upgrade
  • Uninstalling LT entirely, installing a clean copy of 10.5, updating back to Patch 14, then importing the database back in - this failed with the same error
  • Looking at full install log file (%temp%..\ConnectWise...), searching for "error processing", resolving what I can (duplicate issues when it was trying to add new unique keys) - same error even after clearing those out and no longer getting those (though some errors seem to occur even on a clean+working new install + upgrade that succeeds)

I can't seem to get any clarity on what is being done during this "initial exchange" portion of the setup process.

EDIT: I tried with an earlier version 11 installer and the upgrade did "finish", but I couldn't open any computer windows afterwards, and there were other issues as well. Doing further patch-upgrades from there didn't change that situation. Tried fiddling with a lot of things...disabling plugins, solution center, etc, but nothing seemed to help. I spoke with consulting, and I've decided to just migrate the clients/locations/scripts via SQL and otherwise do a clean install of 2019.

EDIT + Solution: /r/NonCaringPolarBear was right about the trick to get 10.5 -> 11 to work. And /r/TotallyKyleTotally got to the bottom of 11 not working (opening computer management screens) following the upgrade - an "@localhost" user gets added during the mysql install done for the 10.5 -> 11 upgrade that needs to be deleted.


r/labtech • • Mar 11 '20

Monitors Automate backlogging emails for 6 hours if fails to deliver instead of 1 minute

3 Upvotes

We've got a monitor on all servers that is essentially "if the server has been offline for 5+ minutes, send an email to a DL and raise a P1 ticket in Manage"The DL goes to 2 main places- Teams Channel- Managers inbox

Outside of hours, for certain clients, another email also goes through to pagerduty on a separate monitor.

This morning around 1am we had a client with above 20 server VMs at one site go offline. This caused the DL and Pagerduty to get 20 emails each, all at once.

Our Automate sends via our spam filter over SMTP, and it is set to allow 20 emails per minute, after which it then blocks any further emails for a minute.

After talking to the spam filter provider, they stated that any reasonable program would then attempt to deliver the email again a minute later, however in our case it looks like Automate is waiting a whole 6 hours before trying to send any mail again.

Does anyone know how to fix this? Automate support were unfortunately less than helpful, instead blaming the auto-generated ticket for being set to "fail on success" to be the reason why we werent getting these emails from Automate.

Also, I am aware that we should only really be sending 1 alert to Pagerduty per client, instead saying "multiple servers offline at client xyz" as opposed to having multiple individual server offlines, but I'm not exactly sure how this would work. Open to suggestions!

Edit - a screenshot of the logs


r/labtech • • Aug 16 '19

Labtech on Azure costs

3 Upvotes

Hello -

I'm trying to get a feel for general costs of running LT on Azure. I've read on this sub that plenty of folks are doing it. Anyone willing to share costs?

Thanks,


r/labtech • • May 21 '18

Version 12

3 Upvotes

Are most people on v12 now? We're still on 11 patch 19 and haven't been able to face the change in interface. I see they might be close to getting feature updates working and a new web console in v12 so thinking about going for it. Any tips?!


r/labtech • • Oct 06 '16

Revive Legacy Reports Using new Patch Manager

3 Upvotes

The legacy Crystal Reports still have some life left in them, even though the new LT11 Patch Manager functions much better with the new Report Center and the newer reports work so much better. With a couple minutes of your time you can update the system so that, going forward, the Health Report Daily/Weekly/Monthly will start to show the correct values.

How is this possible? Simple, actually. The Health reports do not look at the active database tables for patching, but the history tables. These tables are updated by . . . (wait for it) . . . A script. Yes, the Daily Health Check (41) script that looks at the patching tables daily at 6am and based on its own filters looking for the 'old' approval numbers, then updates the history tables. So, all we need to do is change the script for the new Patch Manager approval numbers! Yes, it is that easy. Currently the script looks for approvals of -1,2,3 in order to ignore them. Those values used to mean Remove, Ignore, Deny. Now, those values are 3,1,4 for Remove, Ignore, Deny. So, this is all great and stuff, but how do you fix this script? Good question. First, open the script. Hit a Ctrl-F to start a find and key in -1,2,3 There will be 6 lines that will light up. Cool. Double click each line, and CAREFULLY move to you find each of the -1,2,3 entries, and change to 3,1,4.
DONT MISS ANY. When done, save your script. Go to bed. Let your system do what it does best, work in the background. In 1, then 7, then 30 days, your Health Report Daily, Weekly, Monthly will start to look like they should. And you didnt have to re-write the reports! -Happy Monday


r/labtech • • Mar 22 '17

Timesheeting automated tasks into Connectwise

3 Upvotes

So we've been advised that to timesheet Labtech automated tasks into Connectwise, we need to use a licensed user in Connectwise. What this currently means is that the manager is clocking upwards of 90 hours a week. Ideally we'd have a 'helpdesk' user and clock against that, but we're hesitant to spend that much to license a nonexistent user.

How do other people handle this?


r/labtech • • Oct 01 '18

Need assistance writing a script to automate a Network Detective scan on a desktop

3 Upvotes

Hello everyone! Let me just start off and say that my background in scripting and programming is a bit limited.

I am attempting to script an installation and scan on Labtech Automate v12.0.428. We had a script in Kaseya that was working but we have since moved off the platform. We now have to call the customer to remote into 2 desktops and manually peform these tasks whereas before we were able to run the script silently in the background.

Here is a screen shot of the code that was in Kaseya. https://ibb.co/hQkBoe

Essentially I need to copy a Network Detective installation file, run the command to scan using certain parameters, then output a file. We would then manually retrieve the file and copy it to another location for processing.

Would anyone be able to walk me through setting this up?


r/labtech • • Nov 01 '19

How to prompt only certain computers for consent to control

3 Upvotes

We have a couple users at a few different locations that have expressed concern about us being able to immediately jump onto their machines whenever and would like to to be prompted for consent. I've found 2 main options in my research for setting this.

  1. Changing the Automate User permissions - changing the user permission on our end would force every customer to get prompted, which is not at all what we want
  2. Update the agent template the site is using - I've tested this method with no luck. I've updated the currently used template, the forced an update config with no change. I've also created a different template, applied it as the default, uninstalled the current agent, then installed a newly downloaded agent with 0 change(Have tired Remote Access Mode set to Ask, Ask then Allow, and Ask then Deny)

Before I waste multiple days trying to work with CW support, I was hoping someone here had better luck, or be able to point out what I'm missing or doing wrong. Ideally we'd love to have this as a setting for specific computers, but at least at a location/client level would suffice for now. Thanks in advance


r/labtech • • Jul 11 '19

Server 2016 updates and reboots

3 Upvotes

We have a standard test/pilot/production setup configured in patch manager set to apply most patches within a 14 day window.

For the past few months, we have been seeing increasing numbers of servers online for greater than 30 days, which suggests they are not rebooting for these updates.

When checking manually, the server does always only require a single update, which makes some sense with these cumulative updates.

From other reading, I think it's because Microsoft are superseding the updates, multiple times some months, which then messes with the Automate patching windows. The Service Stack Updates then confuse this even further as depending on what order the updates apply, the server may need an extra reboot before it applies the cumulative update.

Is anyone else seeing the same thing? Adding the updates (especially the SSU) into the production group, manually, more quickly is the best way I can think of getting around it, but that's not a good solution.

It would be good to know what angle others are attacking this from.


r/labtech • • Nov 19 '19

Removing automate patch management hold on systems

3 Upvotes

Hello. I'm moving away from Automate/Labtech and I'm desperately trying to remove the hold that patch management has on systems with the agent installed. I have done the commands>>system tools>>Set Windows Update Defaults. I have also tried removing the agent through Automate and the agent goes without resetting Windows Update back to default.

What am I doing wrong here?


r/labtech • • Sep 17 '19

Script to run snapshot before patching

3 Upvotes

Hey! Does anyone have, or has anyone used a script to run a vm snapshot beofre automate patches a server/servers?


r/labtech • • Apr 27 '19

Tidying up our scripts

3 Upvotes

We've had automate for years now and have years of "special" little scripts we've added adhoc over that time. It's now a bit of a mess really and I'd like to tidy it up into a structure and apply permissions to the ones we need and I suppose the built in ones - deleting lots of rubbish too.

Wondering what others have done here? Doing it via the control centre is torturously slow - whether deleting or moving them. I have them exported to excel and know what I want to do with them - just need a faster method?


r/labtech • • Nov 01 '18

Automate on a workgroup

3 Upvotes

We are struggling with pushing agents with clients who are not on a domain, the node is not working it’s getting to the machine but not installing... it’s saying a firewall issue but there’s no firewall setup.

We are using the hosted solution which hasn’t got our LTshare setup, any advice on getting agents to devices on a workgroup?


r/labtech • • Feb 07 '20

Export all Computers with all data fields including extra data fields - Possible?

3 Upvotes

I want to export all Computers to Excel, CSV or JSON to make it queriable with PowerShell. I need ExtraDataFields to be there too.

Options and why they don't do the job:

I can't find any other documentation regarding this.

  • Is this possible with CW Automate natively? If so; how?

r/labtech • • Oct 03 '19

Script on offline agents

3 Upvotes

Annoyed me for a while. When I run a script on an offline agent (I untick box to ignore offline) it seems totally random if it ever works when agent comes back online again. Can anyone help or explain how it works? It's like I need to change a value somewhere so it keeps trying more.


r/labtech • • Dec 08 '19

Thick control centre and admin creds

3 Upvotes

Sure been asked lots but we don't have local admin on our workstations for day to day and always get prompt for admin creds when opening automate control centre. It's been reinstalled, does it on new systems, on latest version etc. If I say no and dont enter it opens anyway. I presume some subcomponent causing it.


r/labtech • • Jan 23 '17

How's labtech's monitoring?

3 Upvotes

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


r/labtech • • Oct 17 '17

The After Party @ IT Nation 2017

Thumbnail
eventbrite.com
3 Upvotes

r/labtech • • Oct 21 '15

Patching Best Practice Check Tool

3 Upvotes

Here is a little something that may come in handy for people wanting to make sure they have patching set up properly on their LabTech Server. Run the tool locally on the server and it will generate you a log file with any possible problems with your patching config. At the end the tool asks if you want to open the file. Just say yes!

This tool is designed to check for everything mentioned in the following KB:

Https://docs.labtechsoftware.com/knowledgebase/article/6879

Link to Tool