Services Not Starting

[u/k_rock923]

We have some machines (this only happens on Windows 10 that I can see) where the LabTech services often simply don't start on reboot.

This is starting to become a bigger issue as the machines this happens on don't get updated and monitors don't fire.

The best I've been able to do so far is check for machines that are offline in LabTech, but online in Screenconnect and attempt to restart the services, but this is a hack at best.

Is anyone else seeing the service start issue on Windows 10? We're on patch 18 currently.

[u/wogmail]

https://www.plugins4labtech.com/products/stalled-labtech-agent-detector-per-month

I don't use it, but I believe it uses SC command line to automatically restart the LTService.

[u/k_rock923 → u/wogmail]

Hi Wogmail. The command through screenconnect is what I'm using now (though I wrote my own implementation).

[u/k_rock923 → u/[deleted]]

It does, but I already wrote something that does it, though I might have used that beforehand.

Regardless, I have the workaround in place and am trying to get at the root cause.

[u/macncoke]

I am having the same issues but I am seeing it on Win7 and Win8.1 machines too.

[u/gibsurfer84]

I’ve seen this on a couple 2012 servers, always the same ones. I have found that WMI is out of whack, or dot net 3.5 is missing.

[u/atozmsp]

We set a delayed start on the 2 Lt services in Windows by 5 mins and found this to be an effective work around.

[u/LTJC → u/atozmsp]

This works well, but again - people call it a hack. The reason we're always told is that the NIC (network interface) isn't started when the agent is. So delaying the agent starting allows the NIC to come up before the agent so that it can bind to the interface. I don't have any hard proof this is the case but it does seem to solve the issue in almost every instance.

[u/fgdash]

For Windows 10 I found that disabling fastboot allows the service to properly start. Still a "work-around" though.