MeshCentral - Router Improvements, Agent Tags, Rock64, Crash Dumps

This week plenty more improvements and new features. The focus has been on MeshCentral Router, a Windows native tool that allows TCP/UDP port mappings, remote desktop and now, remote file management. I also purchased a Rock64 computer and tested MeshCentral on it resulting in a Tweet that got a lot of likes from the community. On top of it all, we have a new agent crash web page for developers, new agent tag parsing and a new automated build system on Linux. In detail:

  • MeshCentral Router Improvements. MeshCentral Router got a lot of improvements in the last week. Because it’s a native Windows tool, it does not have the limitations of the browser sandbox and so, can integrate better with the local OS. Here are some of the improvements:
  • Remote File Manager. There is now a built-in file manager. You can right click on a device and open a local/remote file window that allows quick navigation of the file system on the remote computer and quick upload/download of many files at once. The file manager also supports drag & drop of files to and from the remote computer.
  • Remote Desktop Clipboard Sharing. You can now pull or push the content of your clipboard to the remote computer. Super useful if you want to quickly cut & paste something on the remote machine.
  • Improved 2FA/3FA support. When performing two-factor authentication, you can now opt to remember your device for an allowed time windows so that you don’t have to perform 2FA each time you connect from an allowed device. MeshCentral Router also has improved 3FA support for MeshCentral Servers that make use of the “LoginKey” feature.
  • Remember Certificate. If your running a MeshCentral server with a private root certificate, you can now have MeshCentral Router remember that certificate and not warn again.
  • MeshAgent tag processing. Just yesterday a new MeshCentral was published with improved agent tag processing. The MeshAgent will send the content of “meshagent.tag” to the server on each connection and we improved the parsing of this file so that, if allowed by the server, we can use values specified in this file to fill the devices name, description and server-side tags. This is in addition to filling the agent tag like we did before. This is very useful for people that want to set some of these values at agent install time from the agent side.
  • Rock64. This week I purchased a Rock64 device that is very similar to a Raspberry Pi. It only cost 20$ on eBay and add it to our workbench of devices we test MeshCentral on. When running 64bit Armbian, the device works perfectly with our 64bit ARM MeshAgent including terminal and remote desktop. This should be very interesting for the Armbian and Rock64 communities.
  • Agent Crash Dumps. A few months back, we added a new option to automate activating and uploading MeshAgent crash dumps to the server. This week, we added a new internal web page accessible by site administrators so you can see what crash dumps are currently on the server and allow the administrator to download and delete them to free space for more uploads. This is especially useful for the development team so to quickly get and process any agent crashes.
  • Automated Linux Builds. This is not a MeshCentral feature at all, but this week I used WinSCP’s scripting to fully automate pushing code to various Linux computers, running MeshAgent compile and pulling back the resulting compiled binary. This will be a huge time saver going forward and will make it a lot easier to support more Linux devices.

Many thanks to the GitHub community for their continued feedback and contributions. As usual, feedback appreciated. If you see any problems and need support on something, please create a new issue on GitHub or help other users.







Popular posts from this blog

MeshCentral2 - Next Generation Mesh Agent

MeshCentral - Web RDP Client, Multi-Language Router, Custom Consent, 7k downloads

MeshCentral2 - MeshCtrl, Windows Services, Events, Remote Typing, Time Localization