Comparing MeshCentral 2 to ScreenConnect
-
@manxam said in Comparing MeshCentral 2 to ScreenConnect:
@Ylian : are there any plans at this time to allow one-time "support sessions" instead of "access sessions". Used for IT support of computers that a) don't have an access session already configured b) users (rightfully) don't have administrator access? (e.g. ScreenConnect)
That's been there, we've been using it for a while. Using the same "agent", but without installation.
-
@scottalanmiller : Oh, good. I asked you personally about it in the other thread a couple of weeks ago and you had stated "no" iirc.
Do you still need 2 files for this? Executable and manifest or can they be combined into the exe?
Thanks!
-
@manxam said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller : Oh, good. I asked you personally about it in the other thread a couple of weeks ago and you had stated "no" iirc.
Do you still need 2 files for this? Executable and manifest or can they be combined into the exe?
Thanks!
You only need one file in either case, it is just the exe.
-
@scottalanmiller : Awesome. Their instructions and the youtube videos show two files needed for client installation.
-
@manxam said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller : Awesome. Their instructions and the youtube videos show two files needed for client installation.
That's really weird, as their actual installation tools only have one. You just clink "download agent" and there is only one file.
-
No instructions needed, it's one exe and you just run it where you want it to be installed or where you want support.
-
It's quite possible that I had come across the old mesh v1 documentation when I first looked at it weeks ago.
This clearly shows the "install/uninstall" or "Connect" options for the installer.Thanks.
-
@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.
