You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have activated user consent for everything.
When I go to Connect to Desktop and an RDP session is open on the target system, MeshCentral recognizes this and asks me whether I want to connect to the console or to the RDP session.
If I select the RDP session, MeshCentral sends the user consent to the RDP session and not to the console session.
However, this does not work for files.
No query from MeshCentral appears here.
MeshCentral sends the user consent to the console session and the RDP user cannot confirm the question there.
To Reproduce
Steps to reproduce the behavior:
Activate user consent for desktop and files.
Establish a normal Windows RDP connection to a target system.
Open the target system in MeshCentral and try to transfer files to it with user consent from the RDP user.
Expected behavior
MeshCentral should currently recognize that an RDP session exists for files as for desktop and ask which session should be connected to.
The text was updated successfully, but these errors were encountered:
Describe the bug
We have activated user consent for everything.
When I go to Connect to Desktop and an RDP session is open on the target system, MeshCentral recognizes this and asks me whether I want to connect to the console or to the RDP session.
If I select the RDP session, MeshCentral sends the user consent to the RDP session and not to the console session.
However, this does not work for files.
No query from MeshCentral appears here.
MeshCentral sends the user consent to the console session and the RDP user cannot confirm the question there.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
MeshCentral should currently recognize that an RDP session exists for files as for desktop and ask which session should be connected to.
The text was updated successfully, but these errors were encountered: