Comparing MeshCentral 2 to ScreenConnect
-
If you see random drops, you may have a router/proxy/firewall with short idle connection timeouts. Add this to the "settings" section of config.json and restart your MeshCentral server.
"AgentPing": 60This will cause the server to "ping" (within the TCP/TLS control channel) the agent every 60 seconds and have the agent replay. That may fix it. If it does, try "AgentPong": 60 instead, that will cause the server to send a pong every 60 seconds and the agent will not reply, so cuts idle traffic by half. Then, you can also try longer time between ping/pong commands.
It's also possible your agent is on a wireless network and the network keeps dropping.
Let me know if that works.
Ylian -
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
If you see random drops, you may have a router/proxy/firewall with short idle connection timeouts. Add this to the "settings" section of config.json and restart your MeshCentral server.
"AgentPing": 60This will cause the server to "ping" (within the TCP/TLS control channel) the agent every 60 seconds and have the agent replay. That may fix it. If it does, try "AgentPong": 60 instead, that will cause the server to send a pong every 60 seconds and the agent will not reply, so cuts idle traffic by half. Then, you can also try longer time between ping/pong commands.
It's also possible your agent is on a wireless network and the network keeps dropping.
Let me know if that works.
YlianI have this setting in place. I'll let you know if it works the next time I use it.
-
Perfect thanks. By the way, I have been doing a bunch of updates to MeshCentral, much of it is community driven from GitHub, latest updates on Twitter: https://twitter.com/meshcentral. Just added optional User Session Idle Timeout an hour ago.
-
One thing that would be nice would be to have the remote machine automatically lock when you press disconnect. Prob best to set it per-machine.
-
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
One thing that would be nice would be to have the remote machine automatically lock when you press disconnect. Prob best to set it per-machine.
Per machine is a horrible idea for anything with a tool like this.
Per group is where this type of setting should be.As for your thought. Make an issue. I don't see one for this feature request.
https://github.com/Ylianst/MeshCentral/issues -
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
@smartkid808 said in Comparing MeshCentral 2 to ScreenConnect:
One thing that would be nice would be to have the remote machine automatically lock when you press disconnect. Prob best to set it per-machine.
Per machine is a horrible idea for anything with a tool like this.
Per group is where this type of setting should be.As for your thought. Make an issue. I don't see one for this feature request.
https://github.com/Ylianst/MeshCentral/issuesYea, group sounds better.. Will do.. tnx
-
If things like that are going to be by group, I think we need way more powerful group management. Right now, we heavily limit the use of groups because it is a pain to have any number of users and groups because you have to add and remove people from every group.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
If things like that are going to be by group, I think we need way more powerful group management. Right now, we heavily limit the use of groups because it is a pain to have any number of users and groups because you have to add and remove people from every group.
That means MC is useless. No tool like this should be lacking group controls. I group by Client because not all techs need access to all clients. Some clients have different settings than others. One client requires consent on connect, one wants only the pop up, one doesn't care, etc.
Adding users to groups is actually a problem I made an issue for a while back.
https://github.com/Ylianst/MeshCentral/issues/185Since then, two more related issues for controlling things with groups and users.
https://github.com/Ylianst/MeshCentral/issues/210
https://github.com/Ylianst/MeshCentral/issues/256 -
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
That means MC is useless. No tool like this should be lacking group controls.
It HAS group controls, it's just that the time to manage them is too long so we don't do it in a granular fashion. We only do it for security groups.
-
FYI. Just published @MeshCentral v0.3.5-x with new agent installation invitation link system. You can create a time limited link and send it to users who get agent installation instructions. In agent installation page supports many OS's and tries to detect the browser's OS to be on the right starting tab (Picture below). This had been requested earlier in this thread, feedback on this appreciated.
And yes, I do need to work on improved group management. I am certainly keeping busy.
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
FYI. Just published @MeshCentral v0.3.5-x with new agent installation invitation link system. You can create a time limited link and send it to users who get agent installation instructions. In agent installation page supports many OS's and tries to detect the browser's OS to be on the right starting tab (Picture below). This had been requested earlier in this thread, feedback on this appreciated.
And yes, I do need to work on improved group management. I am certainly keeping busy.
Success! I use the Link Invitation to help a co-worker.
-
This issue is concerning if antivirus software is removing the agents it's detecting mc as a false positive.
https://github.com/Ylianst/MeshCentral/issues/296 -
@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:
This issue is concerning if antivirus software is removing the agents it's detecting mc as a false positive.
https://github.com/Ylianst/MeshCentral/issues/296Major concern with the AV products. Find whatever that is and remove it. Stick with Defender!!
-
On 0.3.6-i now.
-
On 0.3.6-i as well.
Installed on client via the invite feature and Desktop does not work on newly installed client.
Also, with each new install, Duplicate Agent count under Agent Error Counters goes up by one.
-
@Scott said in Comparing MeshCentral 2 to ScreenConnect:
On 0.3.6-i as well.
Installed on client via the invite feature and Desktop does not work on newly installed client.
Also, with each new install, Duplicate Agent count under Agent Error Counters goes up by one.
Is the newly installed client Windows 10 1903?
-
6.1.7601
Windows 7
-
0.3.6-k; agent installed via the invite function.
Client shows agent connected; 7 Day power state for 6/12/2019 shows connected 12:00:00 to 09:14:42am (it is now 12:18pm).
Connecting to desktop sometimes proceeds and says Connected, but no image is displayed; sometimes attempting to connect to desktop states "Setup..." and no image is displayed. Same with Terminal and Files: either says Connected or Setup... yet nothing connects.
For those using this in production to service clients, is there some secret here to get this to work consistently?
-
@Scott said in Comparing MeshCentral 2 to ScreenConnect:
0.3.6-k; agent installed via the invite function.
Client shows agent connected; 7 Day power state for 6/12/2019 shows connected 12:00:00 to 09:14:42am (it is now 12:18pm).
Connecting to desktop sometimes proceeds and says Connected, but no image is displayed; sometimes attempting to connect to desktop states "Setup..." and no image is displayed. Same with Terminal and Files: either says Connected or Setup... yet nothing connects.
For those using this in production to service clients, is there some secret here to get this to work consistently?
It's been too random for me. It works fine when connecting to Linux systems.
-
I was wondering if it is me. I have heard great things about this from people using it to service clients and who are switching from other remote access solutions, but I find it too random for me to use.
When it works, it's great.
