@scottalanmiller said in MeshCentral "locking remote user out of desktop":

@Dashrender said in MeshCentral "locking remote user out of desktop":

@DustinB3403 said in MeshCentral "locking remote user out of desktop":

@Dashrender said in MeshCentral "locking remote user out of desktop":

@DustinB3403 said in MeshCentral "locking remote user out of desktop":

@scottalanmiller who still uses screensavers. . . . . .

Versus just a blank screen? Isn't the effect the same - a locked system?

No, a screensaver actively uses resources to operate. A blank screen is off.

Plus Cmmd+L locks the screen, no need for a screensaver to do that for you.

the screensaver also has a 'blank' mode which has an associated timer...

If the user set it at 1 min, I'm sure it's about security with them, not some stupid pipe drawing program.... so I'm back to my original comment.

blank screen/screen saver - who cares - end result is the same, a locked system.

Yeah, that was going on too!

too?

@Dashrender said in MeshCentral Web RDP Client:

@scottalanmiller said in MeshCentral Web RDP Client:

You ever try this?

I've not, I keep forgetting that it even exists, lol.

@scottalanmiller said in MeshCentral Run Commands on Multiple Computers at Once:

"Starting with MeshCentral v0.5.85, you can now select "Run Commands" in the group actions or device actions. Allows running shell commands on many devices at once."

Ecq0qLrUcAEBBek.png

Wow, this is going to really change the way we use Mesh! Awesome stuff!

EdkJFXDVoAEXM2i.png

@JaredBusch said in Notification by MeshCentral after a computer comes back online:

This is not a MC request or support forum.

I'll make a note.

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

I'm on 0.7.47, I don't see a problem w Windows machines?

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.