Search the Community
Showing results for tags 'agents'.
Found 3 results
Is anyone else experiencing this issue (observable in LTErrors.txt agent log file)? In a client environment with a solid and stable network I have personally observed the impact of this (RMM server thought agent was offline even though I was remoted into another agent on the same network). In communication with ConnectWise, they did confirm that this could result in potentially missed alerts and data (the original focus of our issue). We have also checked three different RMM systems (one of which is our own on-prem, another which is cloud-hosted by ConnectWise, and the third in Azure) and found the same issue to exist in those environments, including on the Automate application server. Two systems we checked had no AV whatsoever, and we did not find anything misconfigured with DNS or network ports. Additional details: Azure RMM has less than 10 agents Cloud-hosted RMM has around 25 agents Our on-prem RMM has 10k+
I have to get a few of our companies NIST 800-171 compliant and I have run into an issue. According to the guidelines, you have to employ FIPS-validated cryptography within the domain. If I turn on FIPS, Labtech agents cant contact the server. Is there anything I can do?
We're looking for a way to notify a distribution group any time a new agent is added to our Automate Server. I briefly searched in the forums, but didn't see anything. I asked Automate Support, but they said they don't have anything that will do this. Does anyone have any ideas?