schester

I just saw this from LabTech support: Hopefully that helps you @NathanMitten or someone else!

I think I was seeing .02 because once updated to .03 they wouldn't check in. I don't know if it was just timing as to how some may have skipped it and it was only the machines that actually got .03 that I had to get on, but we had two clients call today because no one could work today, but fortunately the majority of our clients were off today. We have only ever used the mbam plugin with LabTech. Do you have any other third party software that could do reboots? Maybe even get on one machine on site and use shutdown /i to try and get all problematic computers to restart? (It didn't seem to work for me, likely because mbam was blocking access to RPC or whatever shutdown needs, but it could be worth a try for you.) Maybe your AV has a reboot function? I didn't try it in this instance, but I've seen many times when LT agent isn't checking in, but we can SC to a workstation and issue a reboot from the SC even if it doesn't really connect to show you the session.

Once the fix was released, I waited a few hours before getting in to check things. And, quite honestly, our LabTech server was also being blocked by mbam, so I couldn't get in to really check anything. After about 3 hours when it seemed clear that it wasn't going to solve itself, I found a way into the LabTech server (was able to remote desktop from another device on the same subnet, but couldn't remotely), I was able to get mbam fixed on there. Once I got it fixed, I gave things a few minutes and then found most of the clients were checking in. I *assumed* if they were checking into LabTech, that mbam probably wasn't causing a problem on them. I spot checked a few and of the online agents they all had v12 or v13 of today's definitions. The agents that weren't showing online had v02 (mostly or exclusively) definitions. I ran a search for LabTech last checkin >1 hour and <1 day to give me a list of agents that weren't checking in. Some of those had gone offline for other reasons and there was only 5% or so that I needed to go through. If the agents are checking in, but not getting mbam updates, could sending a restart script to all of them help?

I actually found that the overwhelming majority of our endpoints have updated automatically. I had about 5% that weren't updated. Most of them I've been able to get into via a ScreenConnect, even though I couldn't connect via remote desktop or TeamViewer to them. I have about 1% that are not letting me in regardless, but I can see from the network side that they are online. They may need a power cycle or physical access. Unfortunately I don't know anything about the cloud console.

I've found that disabling the website blocking, then updating the database fixes the problem and the website blocking can be re-enabled. No restarts are needed, but we are running 1.80 for MSP, so it could be different for others. What I can't figure out is how to do this on all the machines that we can't talk to because of this issue. Has anyone found a viable way to tell the remote devices to update? The impacted devices don't seem to be checking in to LabTech/Automate.

Will devices automatically update to the latest version (since they have a bad update currently) or will we need to manually update?

Having the same problem here. Had to be some update installed this morning. Things were working fine about 7:30, but starting about 8:30 I started getting calls that people can't access some sites or email. I can't use TeamViewer or Remote Desktop to access servers or workstations so I'm left using Out of Band solutions. Any ideas on how to fix this remotely?

Being that August has come and gone and there doesn't seem to be any news, can anyone provide an update on this integration?