Comparing MeshCentral 2 to ScreenConnect

CloudKnight

@scottalanmiller I haven't yet no, does the link only appear once you have entered SMTP settings?

scottalanmiller

@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller I haven't yet no, does the link only appear once you have entered SMTP settings?

Correct

black3dynamite

Ok, on the same fedora minimal install, I install nodemailer and created an email.js file with following code:

var nodemailer = require('nodemailer');

var transporter = nodemailer.createTransport({
    host: '10.254.0.96',
    port: 25,
    secure: false, //true --> will use ssl
});

var mailOptions = {
    from: '[email protected]',
    to: '[email protected], [email protected]',
    subject: 'Hello',
    text: 'Hello world',
    html: '<b>Hello world </b>'
};

transporter.sendMail(mailOptions, function(error, info) {
    if (error) {
        console.log(error);
    } else {
        console.log('Message sent: ' + info.response);
    }
    transporter.close();
});

And then I ran node email.js and was able to send and received emails.

But when I add the host, port, from, and tls information I don't see the invite link or can verify emails.

"smtp": {
        "host": "10.254.0.96",
        "port": 25,
        "from": "[email protected]",
        "tls": false
    }

Besides that everything else is awesome.

syko24

@black3dynamite said in Comparing MeshCentral 2 to ScreenConnect:

Ok, on the same fedora minimal install, I install nodemailer and created an email.js file with following code:
var nodemailer = require('nodemailer');

var transporter = nodemailer.createTransport({
    host: '10.254.0.96',
    port: 25,
    secure: false, //true --> will use ssl
});

var mailOptions = {
    from: '[email protected]',
    to: '[email protected], [email protected]',
    subject: 'Hello',
    text: 'Hello world',
    html: '<b>Hello world </b>'
};

transporter.sendMail(mailOptions, function(error, info) {
    if (error) {
        console.log(error);
    } else {
        console.log('Message sent: ' + info.response);
    }
    transporter.close();
});
And then I ran node email.js and was able to send and received emails.

But when I add the host, port, from, and tls information I don't see the invite link or can verify emails.
"smtp": {
        "host": "10.254.0.96",
        "port": 25,
        "from": "[email protected]",
        "tls": false
    }
Besides that everything else is awesome.

@black3dynamite - I noticed that sometimes when you make changes to the json file and restart the services, you need to close your browser completely and even clear your history at times for the page to show updates properly.

scottalanmiller

0.2.5-l is out.

CloudKnight

Update caused me error.

dafyre

Update worked for me.

CloudKnight

Last update worked fine for me, I will just reinstall new version.

bnrstnr

Do you know if this works with Windows CE/Embedded Compact? I can't get ScreenConnect working there, and it's come up a couple times for us.

Ylian

@StuartJordan Just fixed that problem. Published v0.2.5-m a few minutes ago.

scottalanmiller

@bnrstnr said in Comparing MeshCentral 2 to ScreenConnect:

Do you know if this works with Windows CE/Embedded Compact? I can't get ScreenConnect working there, and it's come up a couple times for us.

Not likely. CE is ancient.

scottalanmiller

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@StuartJordan Just fixed that problem. Published v0.2.5-m a few minutes ago.

Updating now.

Ylian

@bnrstnr No WinCE support in MeshCentral. People still use that? I have not used WinCE since my last Nav system in my old car and my HP PocketPC a long time ago.

scottalanmiller

And we are on 0.2.5-m now.

Romo

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

And we are on 0.2.5-m now.

Wondered why I was kicked out :smiling_face_with_open_mouth_cold_sweat:

Ylian

@syko24 For SMTP setup. When the server is started, it will perform a check of the SMTP server to make sure it's working. When running the server manually you should see the line "SMTP mail server... working as expected". If not, you should see an error. Can you try and report back what you see? - Thanks.

scottalanmiller

@Romo said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

And we are on 0.2.5-m now.

Wondered why I was kicked out :smiling_face_with_open_mouth_cold_sweat:

Oops

dafyre

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@StuartJordan Just fixed that problem. Published v0.2.5-m a few minutes ago.

Updated to 0.2.5-m here as well.

bnrstnr

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@bnrstnr No WinCE support in MeshCentral. People still use that? I have not used WinCE since my last Nav system in my old car and my HP PocketPC a long time ago.

Unfortunately, yes, it's very common in manufacturing settings. We use machine operator interface terminals that have it installed on them. It would be awesome to have something like MeshCentral to support them.

scottalanmiller

@bnrstnr said in Comparing MeshCentral 2 to ScreenConnect:

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@bnrstnr No WinCE support in MeshCentral. People still use that? I have not used WinCE since my last Nav system in my old car and my HP PocketPC a long time ago.

Unfortunately, yes, it's very common in manufacturing settings. We use machine operator interface terminals that have it installed on them. It would be awesome to have something like MeshCentral to support them.

Windows CE is a different platform than Windows. Different kernel and OS. Requires different applications. You CAN make things that run on both, but almost no one does. There's no reasonable chance that any modern software will be made to work on CE, it's a dead OS that wasn't very useful or good when it was still around. It's only five years since the last one, but that was more of a maintenance update than really providing something meant to still be deployed.