search

Ylianst / MeshCentral

A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
https://meshcentral.com
Apache License 2.0
3.96k stars 536 forks source link

Windows desktop via Agent frozen when changing users login #3028

Open rodrigolzd opened 3 years ago

rodrigolzd commented 3 years ago

I'm only using agents to connect to the desktop, so I don't know if this happens in other methods.

When I connect to a desktop, windows 7, 10 and server 2012, if the user is not logged in already and I login, the screen gets frozen and I have to disconnect and reconnect from the desktop to see the desktop already logged in. I also noticed that if the user is logged in already and I change to another one the same thing happens.

Is this a bug, by design or a failure on my setup?

VINISHVV commented 3 years ago

+1 from my side.

rodrigolzd commented 3 years ago

I forgot to mention, all my deviced are remote, the server is hosted online. Not sure that makes a difference.

krayon007 commented 3 years ago

Normally, on Windows, whenever you switch users, whether it be by logging in, or logging out, or just switching, the API I'm using to capture the screen will get locked out with a security error. Normally this should result in the pipe getting disconnected. The agent is supposed to detect this disconnect, and try to reconnect using a different UID. I've seen a few machines where the pipe doesn't disconnect, data just stops flowing, so the agent wasn't able to detect this switch... I haven't been able to reproduce it, so if you can give me some more details about your setup, I'll try to reproduce it... What server version are you using? If you just run the agent on the command line with the following switch, it will report details on which commit the agent was built with:

MeshAgent -info

PathfinderNetworks commented 3 years ago

Same here. It's something I've just gotten used to. It happens on the majority of my devices (which are a mix of Windows 10 Pro, Server 2012, Server 2016, and Server 2019). Doesn't seem to matter if the device is domain joined or stand alone.
I'm always running the current (or at least one or two versions from the current) version of MeshCentral.

rodrigolzd commented 3 years ago

Im running the latest verions, and just like PathfinderNetworks said I also have a mix of devices, most outside of a domain as well.

MeshAgent -info - didnt work so I ran info at device the console

info Current Core: Aug 5 2021, 975393991 Agent Time: 2021-08-13 14:39:07.781-03:00. User Rights: 0xffffffff. Platform: win32. Capabilities: 15. Server URL: wss://meshaddress:443/agent.ashx. OS: Windows Server 2012 R2 Standard [9600]. Modules: amt-apfclient, amt-lme, amt-manage, amt-mei, monitor-border, smbios, sysinfo, util-agentlog, wifi-scanner-windows, wifi-scanner, win-console, win-info, win-securitycenter, win-terminal, win-virtual-terminal. Server Connection: true, State: 1.