Comparing MeshCentral 2 to ScreenConnect
-
Just updated to 0.3.0-d !
-
updated to 0.3.0-g
-
@pmoncho said in Comparing MeshCentral 2 to ScreenConnect:
updated to 0.3.0-g
Here, too. Fast moving week!
-
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@pmoncho said in Comparing MeshCentral 2 to ScreenConnect:
updated to 0.3.0-g
0.3.0-h now.
That didn't take long, 0.3.0-i
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@pmoncho said in Comparing MeshCentral 2 to ScreenConnect:
updated to 0.3.0-g
Here, too. Fast moving week!
That it is.
So fast, sometimes Auto-update cannot keep up! :winking_face:
-
0.3.0-n
Lots of updates today!
-
Realize this thread was comparing to SC but wondering how would this compare to Apache Guacamole? I haven't yet had time to try to set this up but thought I'd ask.
-
@NashBrydges said in Comparing MeshCentral 2 to ScreenConnect:
Realize this thread was comparing to SC but wondering how would this compare to Apache Guacamole? I haven't yet had time to try to set this up but thought I'd ask.
Guacamole is more a perimeter gateway interface for accessing machines inside of the LAN.
Meshcentral has client agents that you can install on machines and can access these machines across WAN. it's very much more like an RMM product. -
@NashBrydges said in Comparing MeshCentral 2 to ScreenConnect:
Realize this thread was comparing to SC but wondering how would this compare to Apache Guacamole? I haven't yet had time to try to set this up but thought I'd ask.
Quite different overall. Guac is a "gateway" product. It sits in front of a number of RDP, NX, X, VNC connections and presents them over web. It's a proxy type service.
SC is a remote access and control system for support. It does not sit (necessarily) in the same infrastructure and is meant for giving you access to machines "anywhere."
So one is to enhance and aggregate existing protocols. The other is a replacement and different kind of architecture to those protocols.
-
0.3.0-p out now.
-
0.3.0-r we just updated.
-
Auto-Update through "Check Server Version" has become an issue as of (roughly) 0.3.0-i. Prior to that all was well.
Syslog would show (when running auto-update):
Update completed... MeshCentral HTTP redirection server running on port 80. MeshCentral v0.3.0-p, WAN mode. MeshCentral HTTPS server running on domain.net:443. SMTP mail server smtp.gmail.com working as expectedAs you can see, MC is still on v0.3.0-p
**Edit - Also, there are no errors when clicking "show server error log"
To update, I connect via SSH
cd mc sudo systemctl stop meshcentral sudo npm install npm sudo npm install meshcentral sudo systemctl start meshcentralIf I don't run
sudo npm install npmMC will not update. No clue why I need the extra step. -
Are there ever agent updates that need to be done with MeshCentral?
-
@bnrstnr said in Comparing MeshCentral 2 to ScreenConnect:
Are there ever agent updates that need to be done with MeshCentral?
Haven't seen any cases for that yet.
-
@bnrstnr When you update the MeshCentral server, it will auto-update all the agents when needed.
-
@pmoncho Arg. I need to investigate this NPM issue. I have not seen this problem on my own servers, but it may be an issue with a specific NPM version. I will take a look.
-
You guys get an premiere, I am posting this here first. I just published the all new MeshCentral Router for Windows. Allows TCP port mapping thru the MeshCentral server. Requires v0.3.0-t or later. You can RDP, PuTTY, WinSCP to remote computers. Youtube video demonstration here. Feedback & bug reports appreciated.
-
@Ylian oh way, that's some awesome stuff! Thanks!
-
Fired up a quick Win10 vm & tested MC2Router....pretty damn cool :thumbs_up: :thumbs_up_medium-dark_skin_tone:
