@Romo yeah, we want that. The MC Router is Windows only, so not very useful as there isn't any Windows involved

@scottalanmiller said in MeshCentral - device duplicating: We get these a lot, but mostly from either major system changes or someone accidentally running the installer more than once. OK good to know. thanks!

@manxam said in MeshCentral 2 - unknown device michael-7-x64: This is an AV sandbox performing a scan and run on this application. Happens regularly when deploying various remote management tools to devices with AV. You'll get some Microsoft VMs, Bitdefender automated machines, Kaspersky, etc... It looks as though this SPECIFIC device name is from Bitdefender's sandbox : https://www.reddit.com/r/msp/comments/c8z1kl/bitdefenders_sandbox_just_ran_my_screenconnectcw/ Nice find!

@Ylian Any thoughts on why my system is demanding having the "cert": line added? I did do a startup based on the install instructions node ./node_modules/meshcentral --cert example.servername.com Does that put the hostname somewhere other than the config.json?

The new views really make a huge difference. Going to the top bar view, removing the bottom bar, adding dark mode. I have way more screen real estate and feel like I can get to what I need more quickly.

Got it all working. Thanks for everyone's assistance!

@Ylian said in MeshCentral Feature Request: User Groups: @scottalanmiller Feedback appreciated, let me know if it works for you. I did post a new blog on this topic today. We've started testing it and so far, yes, it is working!

0.4.6-x has released... "Fixed mobile application for user groups., Remove straight dep in lieu of module push if plugins are enabled, Only if plugins are enabled, add semver module, Add semver dependency for plugin version and compatibility checks."

I've exported his PDF's and converted them to ODT files for editing, they are currently available from Github here I've sent @Ylian an email requesting he pull these files over so the community can assist with updating this documentation.

@scottalanmiller That's one hell of a run on sentence! Do you actually speak without pausing or breathing?

I solved this - problem was, after I changed port on MC2, I needed to download new MeshAgents that are setup for that port and install them to monitored PCs

Exported, cleaned up references to mongo and all better. No Mongo. Export the database (this uses the running database, so I had to have Mongo fixed) cd /opt/meshcentral node node_modules/meshcentral --dbexport" Go in the config file and remove the "mongodb" line(s) in settings nano /opt/meshcentral/meshcentral-data/config.json Restart meshcentral systemctl restart meshcentral # or /opt/meshcentral/mcstop /opt/meshcentral/mcstart Import the database cd /opt/meshcentral node node_modules/meshcentral --dbimport" Restart meshcentral systemctl restart meshcentral # or /opt/meshcentral/mcstop /opt/meshcentral/mcstart

@scottalanmiller said in MeshCentral never updates the display name: I would prefer hostname as a separate "detected" field that is always there, and the display name as one that doesn't change on us. I don't care what the default setting is, as long as it is a setting that I can choose, because I will hate having to update crap all the time.

Great question actually. I don't use hyper-v much.

0.2.9-z is working for us here. Thanks!

@scottalanmiller said in MechCentral Feature Request: Blank Background Wallpaper Option: A feature that I would really like to see on MeshCentral is the option to have background wallpaper blanked out. This reduces bandwidth needs and often goes a long way to improve responsiveness and look & feel when using remote access. Many customers and users have rotating backgrounds that just destroy remote connections. @Ylian Already submitted a request on github?

@vpr00 said in MeshCentral Performance Testing: Sometimes after i press connect, half of the image loads and it wont load any further. I have to press disconnect and connect again until it works. Have you experienced the same? It only happens with WebRTC though. Yes, we do see that from time to time.

Anyone? I went thru manuals evrything seems ok but no success. LetsEncrypt subfolder is not created even if production is false This is my config.json { "settings": { "cert": "MyDomain", "wanonly": true, "_minify": true, "letsencrypt": { "email": "MyEmail", "names": "MyDomain", "rsaKeySize": 3072, "production": true }, "webrtc": true, "allowhighqualitydesktop": true }, "domains": { "": { "title": "RDP support" } } }

@JaredBusch said in Install MeshCentral2 on Fedora 29 with MongoDB: @scottalanmiller said in Install MeshCentral2 on Fedora 29 with MongoDB: @bnrstnr said in Install MeshCentral2 on Fedora 29 with MongoDB: Is it possible to migrate from MongoDB to NeDB after we've been running for a while? Easier to just start over? Probably, but never considered doing that! I think @Ylian mentioned that is was possible or was going to be possible. in the main thread.. not 100% sure. Should be, they share a format. I've just never ingested a backup into NeDB before.

@scottalanmiller said in MeshCentral2 Issue: @dafyre said in MeshCentral2 Issue: What I saw on my Fedora 29/Gnome desktop was that it showed up, but most of the remote features did not work. that's more of what I would expect. As discussed in another thread (I think)... that's due to Wayland being used for Gnome.

@black3dynamite said in MeshCentral Agent Supported Linux Distros: I'm able to connect to the Desktop on Fedora 29 Gnome (Xorg). At the lock screen too. Same here.

Its actually Upload default server core, when the terminal has gotten stuck for me, I have cleared the core and then upload the default server core to get it to work again properly without rebooting the machine. Clearing the core gets only General, Events and Console tabs and loading the default loads all the rest. Maybe it helps in this case as well.

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