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/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.
-
@Scott said in Comparing MeshCentral 2 to ScreenConnect:
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.
In our case, we almost always control the environments that it is going into. So things like AV problems don't arise for us.
-
@scottalanmiller I get this, sometimes you may not be able to change the current A/V solution they are using though. This is still an issue.
-
Starting with MeshCentral v0.3.6-m, both the 32bit and 64bit MeshAgents should no longer report as a problem with any anti-virus. Both get a perfect score on virustotal.com. Update your server and you should be fine.
-
Quick note that MeshCentral v0.3.6-n just got published with remote user consent support for remote desktop, terminal and file access. The remote user prompt will work on Windows, MacOS and many Linux distributions. This is a much improved MeshAgent, so lots of fixes. Enjoy and of course, feedback appreciated.
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
Quick note that MeshCentral v0.3.6-n just got published with remote user consent support for remote desktop, terminal and file access. The remote user prompt will work on Windows, MacOS and many Linux distributions. This is a much improved MeshAgent, so lots of fixes. Enjoy and of course, feedback appreciated.
Awesome.
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
Quick note that MeshCentral v0.3.6-n just got published with remote user consent support for remote desktop, terminal and file access. The remote user prompt will work on Windows, MacOS and many Linux distributions. This is a much improved MeshAgent, so lots of fixes. Enjoy and of course, feedback appreciated.
Excellent work.
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
Starting with MeshCentral v0.3.6-m, both the 32bit and 64bit MeshAgents should no longer report as a problem with any anti-virus. Both get a perfect score on virustotal.com. Update your server and you should be fine.
Awesome work, as always.
-
@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller I get this, sometimes you may not be able to change the current A/V solution they are using though. This is still an issue.
Oh its an issue, just critical to understand where the issue is. Broken AV needs to be recognized as broken AV.
-
0.3.7-h .... we just updated to here.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
0.3.7-h .... we just updated to here.
And now 0.3.7-k. Being this far off of the time zone than the team makes updating MC easier, at least.
-
Just posted a blog on the latest MeshCentral2 improvements. Added FreeBSD support, Puppy Linux support, Account creation invitation Email, Notification control and API Tracing.
