Installing plugin makes some agent go offline about meshcentral-scripttask HOT 3 CLOSED

Hi @canove,

The win-message-pump is a module built into the MeshAgent. ScriptTask doesn't directly utilize it for anything, but if there's an association between installing ScriptTask and receiving the error I can certainly take a look.

I don't have any Win7 anymore (it went out of support by MS in January), but I can spin up a test VM to see if it has an affect. What % of your Win7 machines did you see the issue on?

Did you select the option to update the cores after installing ScriptTask?

At what point in the install / usage did the issue occur? Do you have a way to repeat the behavior? If there is a way to repeat the error message on a client system, we can change the MeshCore to show more details about the stack trace.

Also, what version of MeshCentral are you using?

from meshcentral-scripttask.

Hi @ryanblenis . I just tried it now, and it seems they all come back online after a while.

I have installed the plugin again and looked up on devices, it goes from 127 to 108 online. The offline ones are all Windows 7, but after a few moments all came back online again.

You can close this. Thanks.

from meshcentral-scripttask.

Thank you for the info! Sounds like the MeshAgent might fail/halt when a new core is sent. Could be an issue to raise with the MeshAgent side of the project, but since it's for Win7, which is no longer under support, and the agent restarts itself as the service failure directive states it should, probably not much to worry about here.

Thank you.

from meshcentral-scripttask.