Comparing MeshCentral 2 to ScreenConnect

JaredBusch

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@JaredBusch You guys are demanding! Good feedback, entire checkbox label is active in v0.2.8-x I just published.

as I use it more, I'll make issues on github. but for now I jsut pop random thought here.

scottalanmiller

On 0.2.9-a now.

Ylian

By the way, I love Red Dwarf I am terrible at SMEG... I need to do more SMEG'ing for my own sanity. Pushed out more MongoDB optimizations.

scottalanmiller

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

By the way, I love Red Dwarf

Several old Red Dwarf fans here.

scottalanmiller

0.2.9-d now.

scottalanmiller

0.2.9-h... busy day!

JaredBusch

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

0.2.9-h... busy day!

I was still on 0.2.9-a, fixed that.

syko24

Just curious are you guys leaving the web portal (login screen) open to all IPs or are you restricting to your office addresses? I like being able to login to our ScreenConnect from everywhere. I am not sure if MeshCentral has a lockout mechanism yet. Granted there is the 2FA now.

CCWTech

Is this going to be open source once out of beta?

Also, is there a way to mass deploy it? I understand there isn't an MSI for a group policy deployment.

scottalanmiller

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

Is this going to be open source once out of beta?

Already open. Apache 2.0 license.

scottalanmiller

@CCWTech here is the code...

https://github.com/Ylianst/MeshCentral

CCWTech

@scottalanmiller How about deployment?

scottalanmiller

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller How about deployment?

What aspect?

CCWTech

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller How about deployment?

What aspect?

The agent - approx 1,500 PC's.

JaredBusch

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller How about deployment?

What aspect?

The agent - approx 1,500 PC's.

You can silent install the agent via whatever means you want to push the exe out with.

MeshAgent.exe -fullinstall

CCWTech

@JaredBusch said in Comparing MeshCentral 2 to ScreenConnect:

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller How about deployment?

What aspect?

The agent - approx 1,500 PC's.

You can silent install the agent via whatever means you want to push the exe out with.
MeshAgent.exe -fullinstall

What do you like to push it out with?

scottalanmiller

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@CCWTech said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller How about deployment?

What aspect?

The agent - approx 1,500 PC's.

Oh, I see.

scottalanmiller

And now 0.2.9-i

Doing the updates now.

black3dynamite

Has this happen to any of you ?
If this happens again, I'll be submitting a ticket.

-------- 2/27/2019, 8:57:46 AM ---- 0.2.9-h --------


/opt/meshcentral/node_modules/mongodb/lib/mongo_client.js:421
          throw err
          ^
MongoError: failed to connect to server [127.0.0.1:27017] on first connect [MongoError: connect ECONNREFUSED 127.0.0.1:27017]
    at Pool. (/opt/meshcentral/node_modules/mongodb-core/lib/topologies/server.js:336:35)
    at Pool.emit (events.js:182:13)
    at Connection. (/opt/meshcentral/node_modules/mongodb-core/lib/connection/pool.js:280:12)
    at Object.onceWrapper (events.js:273:13)
    at Connection.emit (events.js:182:13)
    at Socket. (/opt/meshcentral/node_modules/mongodb-core/lib/connection/connection.js:189:49)
    at Object.onceWrapper (events.js:273:13)
    at Socket.emit (events.js:182:13)
    at emitErrorNT (internal/streams/destroy.js:82:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
Emitted 'error' event at:
    at /opt/meshcentral/node_modules/mongojs/lib/database.js:31:16
    at connectCallback (/opt/meshcentral/node_modules/mongodb/lib/mongo_client.js:527:5)
    at /opt/meshcentral/node_modules/mongodb/lib/mongo_client.js:418:11
    at process._tickCallback (internal/process/next_tick.js:61:11)

scottalanmiller

@black3dynamite No, have not seen that.

But the error appears to be from MongoDB not responding, not from MeshCentral.