MeshCentral - Individual Device Rights, HeapDump

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 when a user has access to a device but it’s the device group that device belongs to. Because access control to a device can be given in different ways, the sum of all access rights is what the user gets. So, you can now grant limited rights to a device group but grant full access to some of the devices in that group. The web application (desktop and mobile) will both handle this correctly. Controlling device access can be done by clicking on a device, or if you are server administrator, you can click on the “My Users” tab, click a user and edit its device rights on that screen.

In addition to the big feature, this last week MeshCentral got a lot more bug fixes and a new “HeapDump” feature allowing developers to easily and quickly dump the NodeJS heap to a file and read the file using the Chrome browser. This simplifies greatly the task of finding and fixing memory leaks in the server.

Once again, many thanks to the GitHub community for their amazing help. If you see any problems and need support on something, please create a new issue on GitHub or help other users.

Enjoy,
Ylian
Twitter: https://twitter.com/meshcentral
Reddit: https://www.reddit.com/r/MeshCentral/
GitHub: https://github.com/Ylianst/MeshCentral/issues
MeshCentral2: http://www.meshcommander.com/meshcentral2





Popular posts from this blog

MeshCentral - Windows ARM64, NodeJS v11, NPM Packages

Image
Hi all. It's been a while since I last posted and now that I am settling a bit more in my work at Microsoft, I have a bit of time to occasionally look after MeshCentral again. It's about time, there where a bunch of things that needed to get fixed. Before that, I want to say that I am doing great. I am working on Microsoft Forms which is one of the offerings of Microsoft 365. For kicks, I started a YouTube channel on Microsoft Forms here during a Microsoft hacking week. I tried to up my game since the videos I last published for MeshCentral. Also, I wanted to share pictures below. I was at a Tesla Supercharger last weekend and, by luck, got to see a Tesla Cybertruck in person. It's very big. Obviously, this is a release candidate driven by a Tesla employee. I saw it after attempting to see the solar eclipse over Oregon, but sadly, too many clouds and saw nothing. In any case, back to MeshCentral. In the last few months a few things have happened with the new releases. Wind...
Read more

Starting work at Microsoft

Image
Hi everyone. It’s been a while since the last blog post and I wanted up update everyone on what is going on. As many of you know already from a discussion on GitHub , Bryan and I have been laid-off from Intel in early November 2022. This was quite a surprise as MeshCentral, MeshCommander, MeshCMD and other tools where widely used. This said, Intel has been having poor financials and Bryan and I where part of a very large first wave of downsizing by the company that involved many people that I know and worked with for a long time. I had been working for Intel for over 25 years having started in September 1998. Over the years I worked on IPsec key negotiation, Universal Plug & Play, DLNA and Intel® AMT. I loved working on all these projects and especially loved working with the open-source community on Mesh projects. Obviously, this was not my decision and Bryan and I had look for what comes next. One option was to continue working on MeshCentral as part of another company or with...
Read more

MeshCentral - New Windows Agents - Installation Dialog, Customization and Server Lock

Image
Lots is going on with MeshCentral, just yesterday Bryan Roe released a new MeshAgent for Windows with many improvements. An improved installation dialog box, logo customization and, to continue MeshCentral’s leadership in security, a new agent code signing locking feature that will surely be used by many to improve trust and security of their MeshCentral installation. In addition to this, we have many more server improvements to cover. In detail: MeshAgent with improved installation dialog box . The new MeshAgent for Windows is much improved with months of changes and bug fixes. The most noticeable feature is by far the new installation dialog with the new logo and connection details button. The new installer is a lot friendlier and easier on end-users. MeshAgent with improved customizations . In addition to all the existing agent customizations available in prior versions, the MeshAgent has new server settings for the installation text and logo. You can now set your own 200x200 PNG c...
Read more