Comparing MeshCentral 2 to ScreenConnect
-
I think that SC, if we work out the licensing, costs us ~$19/tech/mo. That's a sizeable tooling cost.
MC appears to work out to around ~$1/tech/mo.
Now that is just licensing and hosting costs, not support. No idea what SC and MC support costs are, but so far, MC uses a lot less than SC from what I can tell. Not that SC uses much, but I've worked on it for other companies and have seen it blossom into a world of support problems. MC might do that too, of course, but SC's issues were caused by whole categories of things that MC doesn't have. Unlike SC which requires code, licensing and other management, MC is self updating and has no licensing to maintain.
-
Where are you running your MC instance, cloud or co-lo?
-
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
Where are you running your MC instance, cloud or co-lo?
Vultr Cloud
-
$5 instance, Ubuntu 18.10. 1 vCPU, 1GB RAM, 2GB Swap. CPU is not taxed, RAM is barely touched, swap is unused.
-
:thumbs_up:
-
I assume the answer is yes, but can MC have multiple techs view the same system at the same time?
-
@syko24 said in Comparing MeshCentral 2 to ScreenConnect:
I assume the answer is yes, but can MC have multiple techs view the same system at the same time?
I'm pretty sure that we tested that, but I'll try to verify in the morning. Don't want to recall someone to their desk at this time just to test that.
-
@syko24 said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
@syko24 said in Comparing MeshCentral 2 to ScreenConnect:
Remote Printing
ScreenConnect has a remote printing feature. Not everyone finds this feature necessary. It can be a little annoying at times when you go to print and have a crazy amount of printers to choose from. However, a lot of our remote users need this feature.
Is this because you are using SC as a sort of VDI tool, rather than as a support mechanism? That's a neat feature, but not one I was even aware that we had
Correct. Some employees, accountants, work remotely by connecting to their desktop in the office. Remote printing is a must for them. For me I keep a handful of clients on ScreenConnect for quick access.
We have systems like this internally, we use NX for that, though. So no need to have MC handle it. We had already found NX to be nicer than SC for that particular need. We have MC on the NX machines now to do support of the VDI instances that use NX, though.
We have customers that use SC like you do, though.
-
I'm using both side by side right now while doing some work, and it is very noticeable how much faster and simpler it is to connect to a remote session in MC over SC. I can initiate the session in SC, then go to MC, navigate to the machine, open a session and have it up before SC gets one up. Must cut the initiation time in half. It's only seconds, but those seconds equal frustration for a tech trying to assist someone. And they add up when you do this all day long.
-
Did you install per Section 4.8 (p 19 of 25) of http://info.meshcentral.com/downloads/MeshCentral2/MeshCentral2InstallGuide.pdf
-
@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:
Did you install per Section 4.8 (p 19 of 25) of http://info.meshcentral.com/downloads/MeshCentral2/MeshCentral2InstallGuide.pdf
No, I don't believe that that guide was online at the time. Most of their links were dead when I was installing.
-
Found a pretty major short coming. So far I can't get MC agents to install on older Windows. I have SC on systems going back to XP (but can't install on 2000). But so far, MC won't install on 2000, XP, 2003, 2003 R2 at all. And on 2008 it installs but does not appear to connect.
-
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Found a pretty major short coming. So far I can't get MC agents to install on older Windows. I have SC on systems going back to XP (but can't install on 2000). But so far, MC won't install on 2000, XP, 2003, 2003 R2 at all. And on 2008 it installs but does not appear to connect.
For something this new, supporting outdated OS makes no sense.
-
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Found a pretty major short coming. So far I can't get MC agents to install on older Windows. I have SC on systems going back to XP (but can't install on 2000). But so far, MC won't install on 2000, XP, 2003, 2003 R2 at all. And on 2008 it installs but does not appear to connect.
For something this new, supporting outdated OS makes no sense.
While I understand that - unless adding that support is really taxing, not having it for a support tool seems like leaving something pretty big out of the tool.
-
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Found a pretty major short coming. So far I can't get MC agents to install on older Windows. I have SC on systems going back to XP (but can't install on 2000). But so far, MC won't install on 2000, XP, 2003, 2003 R2 at all. And on 2008 it installs but does not appear to connect.
For something this new, supporting outdated OS makes no sense.
It might not make sense specifically because it is so new. Supporting that old stuff requires using older technology that might make supporting new stuff much harder (which means it might never happen.) Supporting stuff so old that it's not viable for production use is generally extremely costly and what kind of customers do you really lose by not supporting their pasts?
Compare that to risking not getting a product out the door at all, or having it not be nearly as powerful or easy to support for the future.
Investing today in the past (technical debt) is risky, because it takes time. This product is just in beta today. So Windows XP, years out of support now, will be even further out of support when this product goes production, and will quickly get further and further into the land of ridiculous. I think it is a good gamble most likely. You have to think about the lifetime of the product. By the time it is getting traction, XP will be that much older.
-
@Dashrender said in Comparing MeshCentral 2 to ScreenConnect:
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:
Found a pretty major short coming. So far I can't get MC agents to install on older Windows. I have SC on systems going back to XP (but can't install on 2000). But so far, MC won't install on 2000, XP, 2003, 2003 R2 at all. And on 2008 it installs but does not appear to connect.
For something this new, supporting outdated OS makes no sense.
While I understand that - unless adding that support is really taxing, not having it for a support tool seems like leaving something pretty big out of the tool.
Seems like it, but I don't think it is in a business context. Not supporting LONG dead products ... do "businesses" still run out of date stuff? Sure. Do serious businesses that are going to consider new open source products or are their target audience? Not likely.
-
Except this product is not truly knew it’s been around since like 2009. It’s only version to that is currently new and in beta. So my question is does the old version support those operating systems?
-
After creating the site admin, from now on :grinning_face_with_smiling_eyes: ,anyone who create an account are normal users? Anyway of preventing creating new accounts?
-
@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:
Except this product is not truly knew it’s been around since like 2009. It’s only version to that is currently new and in beta. So my question is does the old version support those operating systems?
True. But I get the impression that MC2 is a full rebuild, on new tech. Maybe that's wrong, but it seemed like a reboot.
-
@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:
After creating the site admin, from now on :grinning_face_with_smiling_eyes: ,anyone who create an account are normal users? Anyway of preventing creating new accounts?
I was wondering that, too. They don't get any permissions, but it seems like they can still make accounts. I've not found any way to remove that.
