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.
@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.
@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.
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 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.
@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.
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.
@StuartJordan said in Comparing MeshCentral 2 to ScreenConnect:
Kaspersky
I asked to be whitelisted by Kaspersky a few months back and they approved. I will need to check that again.
We have our own WebRTC stack in the MeshAgent which is quite unique. However, Firefox v64 just broke it (Looking into it), Chrome works. With WebRTC traffic goes directly from the browser to the agent bypassing the server. Should be faster, scale better and lower hosting costs.
Yes, I am traveling for the next 5 days, will be back with updates soon. Got plenty to work on.
Ylian
@syko24 Yes, lockout and two-factor and both good ideas! Bit busy now, but that we certainly on the list.
@syko24 Right. The _ just causes MeshCentral to ignore that setting. I put a sample "config.json" in place to get people started, but really, MeshCentral will work just fine without any config.json file. MeshCentral will use all default values until indicated otherwise. The sample config.json basically does nothing until you start removing the _ chars.
@StuartJordan Just fixed that problem. Published v0.2.5-m a few minutes ago.
@scottalanmiller With Windows IoT the kernel is a bit different, but it's possible we could support it. The main issue we got in the past was that we had to strip out a lot of agent features to make it work. Really no way we could with WinCE, it's too insane to get the development tools and do that work for that one.
@FATeknollogee (Auto-update broken) There was a few versions a month back where auto-update was broken. Otherwise, MeshCentral has to be running in a way that allows it to write it's own files. This said, it auto-update should generally work - If it does not consistently and it should, file a issue on GitHub.
@JaredBusch Thanks. Yes, you can now change groups. By the way, maybe this will help your installer: You can create a text file with the same name as the agent with ".tag" at the end (or instead of .exe on Windows) and put some serial number or short unique id in it. When the device shows up, click on it and your will see "Agent Tag" with the content of the tag file. This is useful if you want to put your own device mapping ID and may help you sort devices.
Published v0.2.9-y with a fix for this.
v0.2.9-z is out. That should solve the fires. Desktop/Terminal/Files working again.
@scottalanmiller Many thanks for reporting this on GitHub. Did a bunch of fixes to minification and NeDB code as a result. Very must appreciated.
Nice! Today I added a "Log scale" option because some data was really off. I also made it so some data points start expiring as times goes on. One hidden feature, you can click on the series names at the top to toggle them.
Ha yes, I have to do some more work on the timeline. However, normally I would see "Connectivity: MeshAgent" if the agent was online (just below "Active User"). Since it's not present, I imagine the agent is not currently connected?