Comparing MeshCentral 2 to ScreenConnect

scotth

I have 4 tasks on the front burner today all of which require the better part of a day each and then I see a new toy released that's causing an itch between my shoulder blades. Thanks Ylian. It looks quite nice.

scottalanmiller

@NashBrydges it's the best support tool I've ever used.

scottalanmiller

Just went to 0.3.0-t

FATeknollogee

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@NashBrydges it's the best support tool I've ever used.

That be a serious understatement...

CloudKnight

wow @Ylian very impressive, love the work you are putting into this project

NashBrydges

Finally installed and setup thanks to @JaredBusch instructions. One question that I didn't find as I was reading through this now very long thread...is there a way to disable the create account capability on the login page? I may be dense but couldn't find this option anywhere.

JaredBusch

@NashBrydges

NashBrydges

@JaredBusch Thank you

Ylian

FYI. Just updated MeshCentral Router for Windows with a new relay port map mode. You can now use a remote agent as a TCP relay to access other services on that network. Feedback on it appreciated.

FATeknollogee

@Ylian Not seeing the new "Relay Map"
I'm on 0.3.0-u
edit: let me re-check, BRB
edit: All good

FATeknollogee

@Ylian Relay Map is badass...just used it to 2-step RDP to a machine that does not have MC installed on it.

Ylian

The MeshCentral Router with relay mapping is indeed, very interesting. By the way, just Published MeshCentral v0.3.1-d with server data collection and charts. You probably want to update and wait a few hours to start getting pretty pictures. Data is logged every 5 minutes. Enjoy. Feedback appreciated.

scottalanmiller

@Ylian just updated, but the server died on the update.

Error: Parse error on line 171:
...s
 * @typedef {{
 *   type: u2f.Messag
---------------------^
Expecting 'ID', 'STRING', 'NUMBER', 'BOOLEAN', 'UNDEFINED', 'NULL', 'DATA', got 'INVALID'
    at Parser.parseError (/opt/meshcentral/node_modules/handlebars/dist/cjs/handlebars/compiler/parser.js:268:19)
    at Parser.parse (/opt/meshcentral/node_modules/handlebars/dist/cjs/handlebars/compiler/parser.js:337:30)
    at HandlebarsEnvironment.parse (/opt/meshcentral/node_modules/handlebars/dist/cjs/handlebars/compiler/base.js:46:43)
    at compileInput (/opt/meshcentral/node_modules/handlebars/dist/cjs/handlebars/compiler/compiler.js:515:19)
    at ret (/opt/meshcentral/node_modules/handlebars/dist/cjs/handlebars/compiler/compiler.js:524:18)
    at ExpressHandlebars._renderTemplate (/opt/meshcentral/node_modules/express-handlebars/lib/express-handlebars.js:247:12)
    at ExpressHandlebars.<anonymous> (/opt/meshcentral/node_modules/express-handlebars/lib/express-handlebars.js:173:21)

FATeknollogee

Mine updated fine, starting to see some graphed data.

scottalanmiller

@FATeknollogee said in Comparing MeshCentral 2 to ScreenConnect:

Mine updated fine, starting to see some graphed data.

I opened an issue on GitHub. No idea what's causing the issue here.

scottalanmiller

After the server runs for a bit with the parsing error, this error appears on the console...

{ Error: Command failed: /root/.nvm/versions/node/v11.4.0/bin/node /opt/meshcentral2/node_modules/meshcentral --launch
/opt/meshcentral2/node_modules/meshcentral/db.js:413
                            func({ nodes: nodeCount, meshes: meshCount, powerEvents: powerCount, users: userCount, nodeInterfaces: nodeInterfaceCount, notes: noteCount, connectEvent: nodeLastConnectCount, smbios: nodeSmbiosCount, total: totalCount });
                                                                                     ^

ReferenceError: powerCount is not defined
    at /opt/meshcentral2/node_modules/meshcentral/db.js:413:86
    at newArguments.(anonymous function) (/opt/meshcentral2/node_modules/nedb/lib/executor.js:29:17)
    at Cursor.execFn (/opt/meshcentral2/node_modules/nedb/lib/datastore.js:445:12)
    at callback (/opt/meshcentral2/node_modules/nedb/lib/cursor.js:126:19)
    at /opt/meshcentral2/node_modules/nedb/lib/cursor.js:193:12
    at /opt/meshcentral2/node_modules/nedb/lib/datastore.js:329:14
    at Object.async.eachSeries (/opt/meshcentral2/node_modules/nedb/node_modules/async/lib/async.js:130:20)
    at /opt/meshcentral2/node_modules/nedb/lib/datastore.js:323:11
    at fn (/opt/meshcentral2/node_modules/nedb/node_modules/async/lib/async.js:582:34)
    at Immediate.<anonymous> (/opt/meshcentral2/node_modules/nedb/node_modules/async/lib/async.js:498:34)
    at processImmediate (timers.js:632:19)

    at ChildProcess.exithandler (child_process.js:294:12)
    at ChildProcess.emit (events.js:194:15)
    at maybeClose (internal/child_process.js:978:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
  killed: false,
  code: 1,
  signal: null,
  cmd:
   '/root/.nvm/versions/node/v11.4.0/bin/node /opt/meshcentral2/node_modules/meshcentral --launch' }
ERROR: MeshCentral failed with critical error, check MeshErrors.txt. Restarting in 5 seconds...

Ylian

@scottalanmiller Many thanks for reporting this on GitHub. Did a bunch of fixes to minification and NeDB code as a result. Very must appreciated.

scottalanmiller

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller Many thanks for reporting this on GitHub. Did a bunch of fixes to minification and NeDB code as a result. Very must appreciated.

Thanks. On 0.3.1-h now and all is working great.

scottalanmiller

Busy day here...

Screenshot from 2019-03-26 14-12-15.png

Ylian

Nice! Today I added a "Log scale" option because some data was really off. I also made it so some data points start expiring as times goes on. One hidden feature, you can click on the series names at the top to toggle them.