Best posts made by Ylian

Starting with MeshCentral v0.3.6-m, both the 32bit and 64bit MeshAgents should no longer report as a problem with any anti-virus. Both get a perfect score on virustotal.com. Update your server and you should be fine.

Published MeshCentral v0.3.8-n with PowerShell support in the Terminal. For Windows computers, right click on the terminal "Connect" button and select "PowerShell connect".

Published MeshCentral v0.3.8-t with much improved event logging. Many more operations are now in the log and the viewer is improved with user/device links and details dialog box.

@srsmith MeshCentral developer here. There is no Android application for MeshCentral, it just going to be the mobile web site. It's not a feature full as the desktop site, but should get the basics (and supports NFC/Bluetooth two-factor authentication on Android Chrome). Let me know if you try it and what you think of it.

Published MeshCentral v0.4.6-u with more progress made on the user interface. Clicking on a user will now show it's device groups and user group memberships and you can add/remove from that screen. User groups don't do anything yet, still a few more days before I try to enable them.

@Romo Perfect bug report for GitHub Just updated the terminal support for Windows in the MeshAgent and I just started seeing this yesterday. Looking into it.

@black3dynamite For SMTP setup, does your server show the "Invite" link as shown in red below? Also, can you go in the "My Server" tab, click on "Show server error log" and report back if you see anything in that log? - Thanks.

@scottalanmiller Script... or set "SelfUpdate" to true in settings section of MeshCentral's config.json. It's supposed to update sometime between midnight and 1am, but I got to check that code again. I may be updating in UTC time or something.

"settings": {
  "SelfUpdate": true
},

@scottalanmiller I think you will notice the much faster start time of the agents on smaller devices.

@scottalanmiller 0.2.6-k fixes a nasty bug in the MeshAgent that caused data corruption when lots of data was flowing at a high rate. The big deal about that release is that you can now do RDP over the Internet using the ClickOnce application. You need Windows on both sides to do it + Use IE or a ClickOnce add-in for FireFox/Chrome. Hit the "RDP" link at the bottom of a device page to trigger it.

@StuartJordan On the topic of the evil "/createLoginToken.ashx?user=(username)&pass=(password)". Good feedback. I do want to allows people to setup MeshCentral on a Raspberry Pi, etc and tinker with it on a local LAN or to help developers get started. However, since I don't want anyone using this in production, in the next release: It will only be allowed if you are using the default un-trusted HTTPS cert. This way, if you start using a Let's Encrypt TLS cert, your own cert or a TLS offloader "createLoginToken" does not work anymore. Hopefully that will keep everyone happy

@JaredBusch I just published v0.2.8-v with support for batch move of devices between groups. I also did quite a bit more work on database optimization. I will check out the rename/screen things when I get a chance. Not related, but try holding shift when you press the full screen button.

There is another problem, going to patch ASAP. The remote desktop/terminal/files does not work.

@bnrstnr When you update the MeshCentral server, it will auto-update all the agents when needed.

I just released a JavaScript IDER server and added it to MeshCommander v0.7.5 and MeshCentral v0.3.2-p. Blog about this here. This is going to be really amazing for Intel AMT users. Now that this is done, I can go back to bug fixing.

@scottalanmiller On Windows terminal currently launches within the MeshAgent process and causes a bunch of issues. Bryan who works on the agent will be looking into spawning a separate process for the terminal shell / powershell that should help. One huge bug with the current model is that "ping -t 1.2.3.4" can't be halted and will keep running even after the agent is stopped. To summarize, the Windows terminal needs more work.

Charts. I need to add a inactivity timeout for one-sided relays sessions to fix the green line.

@scottalanmiller Your right, the built-in DB (called NeDB) is really fast and will probably handle a 1000 devices without any issues and with much less RAM than MongoDB. I run MeshCentral on Raspberry Pi and AWS t3.nano instances and you really don't need MongoDB.

On another note, seems like I will need to take a look at MeshCentral installation on the latest Ubuntu versions

@scotth Note that MeshCommander is built into MeshCentral. Once you get MeshCentral running, click on a device and if it has Intel AMT, you will see a "Intel AMT" tab. The content of that tab is MeshCommander.

If you just want a Intel AMT console and connect to AMT devices on the local network or using a VPN, use MeshCommander. If you want a more completely management solution with AMT support included use MeshCentral.

Hope it helps.

If you see random drops, you may have a router/proxy/firewall with short idle connection timeouts. Add this to the "settings" section of config.json and restart your MeshCentral server.

"AgentPing": 60

This will cause the server to "ping" (within the TCP/TLS control channel) the agent every 60 seconds and have the agent replay. That may fix it. If it does, try "AgentPong": 60 instead, that will cause the server to send a pong every 60 seconds and the agent will not reply, so cuts idle traffic by half. Then, you can also try longer time between ping/pong commands.

It's also possible your agent is on a wireless network and the network keeps dropping.

Let me know if that works.
Ylian