Get The Scoop On What's New
Want to know what Plugins4Automate is doing for ConnectWise Automate? Come check out our blog and find out about new products and updates that we are working on!

Habitat Stalled Agents Tool

Support forums for the Habitat Automate plugin
Post Reply
User avatar
Posts: 1348
Joined: Tue Dec 29, 2015 7:57 pm

Habitat Stalled Agents Tool

Post by Cubert » Wed Dec 18, 2019 3:53 pm

Habitat has taken Stalled Agents to the next level by automating the management of the LTagent services with ScreenConnect. Habitat looks at offline agents and will attempt to restart the LT agent services on that agent if it sees that agent is up in Screenconnect. After the agent goes offline for more than 24 hours the attempts will stop.

Stalled Agent detector is just that, This tool looks into all agents to see if any agents show running excessive commands or polling the commands, to see if any agent shows offline in either Automate or Screenconnect or shows know active scripting bug issues and displays those agents in plugin. The plugin provides tools to manually clear and or repair a given agent and an automated service to look for offline agents in Automate that are active in Screenconnect and restarts the Automate Services through Screenconnect.

StalledAgents.PNG (16.1 KiB) Viewed 325 times

The Plugin uses 4 main tabs to display possible troubled agents. if you do not see any agents in a view then this is "Great"! that view shows you have no agents with issues.

Click into a view then right click an agent in view to pull up menu of actions to perform on agent.

StalledAgents-offlineagents.PNG (21.49 KiB) Viewed 324 times

Red dots = agents offline over 24 hours
Green dots = agents offline less than 24 hours.

Use AgentID for Automation Task

The automation time it takes to send and receive screenconnect request using the automation in the Automat server would cause issues and overruns as the timing repeats to fast to make easy use of the automate host for agent screenconnect repairs so we offload that to an agent that can has time to spare. This process is not a heavy or strenuous process for the agent and it resolves the timing issues created when multiple agents are offline and needing service restarts. Select an agent that is always on, can be a server or workstation that can see the Screenconnect URL. Only one agent is needed for all clients and not 1 agent per client.

Posts: 9
Joined: Tue Jun 04, 2019 6:07 pm

Re: Habitat Stalled Agents Tool

Post by MarkHodges » Sun Jan 19, 2020 6:58 pm

Do we need to manually install and configure the RMM+ screenconnect plugin to get the non RPC restart working correctly?
Might be something to include documentation on as part of the habitat as some people might not know about RMM+ at all.

I believe the whole point of the plugin was to find machines where screenconnect is running, but the automate agent is stopped (ie, LT offline Agents). Every machine I try this on gives me a variation of this error.

Starting Screen Connect connections to PCNAME, Sending wakeup call
Lets give the wake up call a few seconds to do it's job
Agent Online time in second (if a negitive number then it is the number of seconds offline) -> -2385627

Agents ScreenConnect service is Offline, we are unable to use screenconnect to access agent.

I am guessing this actually means that something with the rmm+ isn't working correctly which according to the actual rmm+ posts, looks like I am not alone. I've confirmed that the RMM+ plugin in SC is up to date and configured with the access key.

I did just update to 2020.1 but I don't think thats likely to be the problem.

User avatar
Posts: 1348
Joined: Tue Dec 29, 2015 7:57 pm

Re: Habitat Stalled Agents Tool

Post by Cubert » Mon Jan 20, 2020 3:01 pm

Yes, RMM+ must be installed separately by you and configured with passcode.

Yea we are still in full beta which means the docs are yet to be written. The possibility that things change a lot between versions at this point prevents us from completing docs. With that said, as the plugin starts to solidify we will start releasing documentation.

As for your issue.

From the error, well actually not an error but from the response of the ScreenConnect Server said that your agent is offline in the "Connect" Server as well as in the Automate Server.

The stalled agent detector can use "Connect" to restart "Automate" agent or the "Automate" agent to restart the "Connect" services on agent but if both show offline we do not have any options to do anything but try a RPC call to agent from another agent. RPC as most know will work to restart services but only if all remote services have been turned on for windows OS so that one agent can send RPC calls to other agent and permissions and such allow agent to respond. This all must be done in advance of ever needing the tool to send RPC calls.

Now if you believe that the "Connect" offline agent for -xxxxxxxx seconds is not accurate and that the agent is actually available in Connect consoles then that's a different bean. Then the question would be why does the call to Connect say agents offline for -xxxxxx seconds when it is not. That might be a RMM+ issue as we only react to the data given us and that data says agent is offline in Connect.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest