Closed chrkli closed 1 year ago
Maybe related to #4387
I tend to find that this happens after a windows update on the client machine Does that match your experience?
Thanks for the hint with windows update. Unfortunately, this has not shown up in my experience.
The last two workdays I've observed the following behaviour: Whenever a client changes the network connection from ethernet to wifi or vice versa the "desktop" and "files" get lost. On a few clients (around 15) the workstation lock also triggers the issue.
Restarting the agent service on the client also restores the "manageability" - desktop and files tab is visible and usable again. It surely is not the most effective way but at the moment I've implemented the following workaround on every client: Create a task on every client with the following triggers
Duplicate of #5008
See duplikate issue for further updates
Describe the bug
Running MeshCentral on ~150 domain-joined clients, mostly Windows 10 (different build versions, see below) as well as three or four Windows 11 Clients. The device groups are configured to show only connected devices. The agent is connected, however it is not possible to access either the functionality "Desktop" or "Files".
Additionally, the list view of all connected nodes does not show anything in the column "username" However, if the command "users" is issued in the agent console of an client "non-controllable", it will print the logged on users correctly. In the agent console, I can issue any command successfully, also osinfo can be accessed.
To Reproduce I'm monitoring several clients showing this strange behavior but up to now, I was not able to find a reproduction or at least any related client-specific config.
Expected behavior While the agent is shown inside the device groupt it shall be possible to directly connect the desktop as well as files.
Current workaround In agent console, first use action "delete core" immediately followed by "Upload default server core" The tabs for "Desktop" as well as "Files" appear almost instantly. Alternatively, trigger agent update via agent consoles "run command" feature.
Server Software:
Client Device:
Remote Device:
Additional context
Screenshots
config.json file