Posts made by Ylian

@scottalanmiller Feedback appreciated, let me know if it works for you. I did post a new blog on this topic today.

Just published MeshCentral v0.4.6-y with User Groups feature fully enabled. Everything should be real-time so, creating a new group, adding users and adding the group to a device group should all show immediate results on all logged in user sessions. Good QA testing and feedback on this feature would be most appreciated.

@Romo That is correct, the red "Agent Tag" is a "meshagent.tag" text file that is in the same folder that the "meshagent.exe". It can contain up to 1k of data sent to the server on each agent start. It's there so if you have some sort of automatic installation of the agent, you can put a serial number of something in that file and it gets sent up to the server. It pre-dates the other blue tagging that is server side only.

All this to say, the two tagging systems are completely separate. I can add you a "atag:<agenttag>" filter if you like? Let me know what you need.

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.

Published MeshCentral v0.4.6-s, making progress. The user interface in mostly done, you can make user groups by you can't do anything else with the group right now.

@scottalanmiller Someone reported the removing a device caused a server crash, but I just fixed it in v0.4.6-r. Apart from that, I started working on the user interface for managing user groups, it's in the "My Users" / "Groups" sub tab but it does nothing now. I plan to build a lot of the UI and groups management first.

Changing the user access control system is going cause a bunch of trashing in the code, published MeshCentral v0.4.6-q just now with lots of changes in preparation for user groups. If you spot anything wrong, please let me know.

@scottalanmiller Makes sense, I will start working on it. This is not going to be easy as it requires a change to how access control is done and there is more user interface work to be done to manage user groups, etc. This said, as you explained, it's an important feature. I will like to have users test the feature when I have early versions. I will post again with progress.

In the case of MeshCentral v0.4.6-d, it was there for a few hours and I had to pull it because it had a bad issue. Once you put a version online, NPM does not allow you to reuse that version number so, it gets skipped. This said, I probably accidentally double bumped up the version number a few times in the past, causing a skip

In real news, I updated the public server, https://meshcentral.com last night to the very latest version. A lot of people use that server and it's sometimes months behind as I want to keep it stable. MeshCentral.com now requires that the privacy bar show up on the remote system when you do a remote desktop session, this is only hard coded for this specific server. You can still do remote desktop without the privacy bar when setting up your own server.

@scottalanmiller Thanks for the new link. Just bookmarked it.
@black3dynamite Thanks for the distro, I will pass that to Bryan so he can test the agent with it.

@black3dynamite MeshCentral should be able to (I think) support Wayland, what distribution are you using?

@scottalanmiller Published MeshCentral v0.4.5-f that should fix a problem with the web application.
@hobbit666 When you update the server, all agents are automatically updated.

@scottalanmiller The best way to see the smaller changes between releases is to look at GitHub commit log. MeshCentral v0.4.5-c has a first pass at a Czech translation, a bit better French translation, Internalization improvements, support for "MpsAliasHost" in settings section of config.json.

I just post on Twitter major changes. The quick releases are to fix issues on GitHub or respond to specific requests.

@black3dynamite I posted about an hour after I published MeshCentral v0.4.5-b. If you are set to auto-update, your server will generally check between midnight and 1am for any updates. So, 24 hours after I publish a new version, you should have it.

@Ylian Another trick in MeshCentral v0.4.5-b is that the MeshAgent should be able to be installed within a Docker container. We will start testing that a bit more. Should be useful to manage what is going on inside server containers remotely.

FYI. Just published MeshCentral v0.4.5-b, this is a super-update because it includes the next generation MeshAgent. You can check Twitter for updates, but this version includes a new remote desktop privacy bar, wallpaper toggling, improved Windows terminal and more.

@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.

FYI. MeshCentral just hit 500k downloads on npm-stat.com in about 2 years of being available.

You don't generally have to use "aliasport" unless the external port that agents will see if different from the port MeshCentral uses. This is not common.

As for the real certificate, you will not have to reinstall the agents. Agent use a special system to authenticate the server using a second certificate within the TLS connection, it's explained in Section 8 of this guide if you want to look at the details. So you can swap the HTTPS certificate when you want as long as the DNS name and port stays the same.

Also, MeshCentral has built-in support for Let's Encrypt and will auto-renew the certificate. You can find help on this in section 11 of the User's guide.

Hope it helps,
Ylian

@smartkid808 Yes, you can change the port, however you need to do this before installing agents as existing agents will not be able to find the server anymore. The "port" setting in config.json will change the port used by MeshCentral, "aliasport" will change the port MeshCentral tells the agents to connect to. So, if you have a port map in front of MeshCentral, use "aliasport" to indicate the "real" port that will be used. Hope it makes sense.

{
  "settings": {
    "Cert": "devbox.mesh.meshcentral.com",
    "Port": 4430,
    "AliasPort": 444
  }
}