Comparing MeshCentral 2 to ScreenConnect
-
@manxam Yes, the old Meshv1 had 2 files. With MeshCentral v2 we got the policy file added inside the Windows executable without breaking the authenticode signature. So, just the one exe now.
-
Up to 0.2.6-e now.
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@manxam Yes, the old Meshv1 had 2 files. With MeshCentral v2 we got the policy file added inside the Windows executable without breaking the authenticode signature. So, just the one exe now.
Thanks @Ylian.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Up to 0.2.6-e now.
* runs off to update....
-
0.2.6-f released to fixed Zorin.
-
0.2.6-g out now, just updated.
-
Just updated to G here.
-
And now 0.2.6-h
-
And now 0.2.6-i
-
Published Meshcentral v0.2.6-j with support for two-factor login using Google Authentication or any compatible app. Also, if an SMTP server is setup, the server will now require email verification before you can create a device group. This way, users don't start adding devices without a password recovery option. Lastly, did a bunch of improvements when the server is running with Windows domain authentication.
-
@Ylian awesome
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
Published Meshcentral v0.2.6-j with support for two-factor login using Google Authentication or any compatible app. Also, if an SMTP server is setup, the server will now require email verification before you can create a device group. This way, users don't start adding devices without a password recovery option. Lastly, did a bunch of improvements when the server is running with Windows domain authentication.
That's awesome
-
MeshCentral trick: Set a session secret in the config.json like this:
{ "settings": { "SessionTime": 60, "SessionKey": "MyReallySecretPassword" } }This way, when the server restarts/updates, you don't need to log back in each time. By default, the session secret is generated on server start so everyone needs to login again because browser cookies can't be decoded anymore.
-
@Ylian cool, good to know!
-
Updating to 0.2.6-k now.
-
@scottalanmiller 0.2.6-k fixes a nasty bug in the MeshAgent that caused data corruption when lots of data was flowing at a high rate. The big deal about that release is that you can now do RDP over the Internet using the ClickOnce application. You need Windows on both sides to do it + Use IE or a ClickOnce add-in for FireFox/Chrome. Hit the "RDP" link at the bottom of a device page to trigger it.
-
@Ylian any way to get that working with Linux on the "support" side?
-
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller 0.2.6-k fixes a nasty bug in the MeshAgent that caused data corruption when lots of data was flowing at a high rate. The big deal about that release is that you can now do RDP over the Internet using the ClickOnce application. You need Windows on both sides to do it + Use IE or a ClickOnce add-in for FireFox/Chrome. Hit the "RDP" link at the bottom of a device page to trigger it.
RDP versus what? What is used otherwise?
-
@Dashrender said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller 0.2.6-k fixes a nasty bug in the MeshAgent that caused data corruption when lots of data was flowing at a high rate. The big deal about that release is that you can now do RDP over the Internet using the ClickOnce application. You need Windows on both sides to do it + Use IE or a ClickOnce add-in for FireFox/Chrome. Hit the "RDP" link at the bottom of a device page to trigger it.
RDP versus what? What is used otherwise?
No, you are missing the point. This is unrelated to the normal remote access. This is an additional RDP proxy system. ScreenConnect offers it, too.
-
The RDP is an end to end RDP system. Used for convenience and security versus raw RDP.
