MeshCentral Blog

This week a major new update to MeshCentral was published with a single big feature that caused a lot code changes all over the project. Because of this, community testing and feedback is very much appreciated. The big feature is that you can now assign user permissions for individual devices instead of an entire device group. In the past, you created a device group and assigned user rights to that device group. This did not allow individual devices to be singled out. Users have been working about this limitation by creating many different device groups with different user permissions and moving devices between groups. This was far from ideal. Anytime you change the access control system, it’s a big deal as your changing a lot of code. In addition, with this new release a user can be given access to a single device but not the group that this device belongs to. So, the web application needs to deal with how to display this device. A new “Individual Devices” header will now show up w

This week there is plenty more to talk about with many more releases, bug fixes and new features. Probably the two biggest topics of the week are the improved MeshCentral Router and improves internalization with more languages and translation tools. Improved MeshCentral Router . MeshCentral Router is a TCP/UDP port mapping tool that allows applications like RDP and SSH to be directed thru the MeshCentral server. This tool allows , for example, quick access to your remote Windows devices using RDP. This week MeshCentral Router got a lot of improvements including a new devices panel that shows all devices in real-time including connection status and allows you to start an RDP session with a single click. Also added was email two-factor authentication support and better support for non-standard ports. Added languages . This week, MeshCentral got added machine translations for Korean, Hindi and Simplified Chinese. While the quality of the translation is low, it’s a starting point for co

This week we got a stack bug fixes and improvements. This last month has been focused on a lot of bug fixing from the community, but we also added a few more feature. In details: Improved Let’s Encrypt support . Starting with v0.5.0, MeshCentral as transitioned from using GreenLock for Let’s Encrypt support to ACME-Client. As a result, if you are using Let’s Encrypt now and update to the latest MeshCentral, the server will come back to the un-signed certificate for a few minutes as it’s requesting a new TLS certificate using the new library. The new code allows NodeJS v8.0+ to support Let’s Encrypt (In the past NodeJS 10.12 was required) and there are new commands in the “My Server” / “Console” tab to check Let’s Encrypt status. The new code is also much smaller and should be much more robust than the old one. See picture below for the new commands (LE, LECHECK, LEEVENTS). Remote Mouse Cursor on Windows . When remotely controlling a computer, it’s sometimes possible for the remote u

MeshCommander is an open source Intel® Active Management Technology (Intel® AMT) management console tool. Version 0.8.1 just got released with much to talk about. MeshCommander has had many minor releases since v0.8.0 to fix various issues, but in v0.8.1 there is a new “Quick TLS” feature that allows users to setup Intel AMT with TLS and switch to a more secure connection in only two mouse clicks. Even more significantly, MeshCommander is now on GitHub making it possible for the community to track changes and contribute with feedback, bug reports and pull requests. In detail: - Quick TLS . Using Intel AMT without a secure connection may be ok in some cases (some private network and VPN situations), however for most use cases, it’s not ideal. In the past, setting up Intel AMT with TLS required various tools, a certificate authority and enough knowledge of Intel AMT.  With MeshCommander v0.8.1, you can now setup TLS with just two clicks. When connecting to Intel AMT without TLS, a re