-
Notifications
You must be signed in to change notification settings - Fork 390
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Launching remote app creates a duplicate user log-in #99
Comments
Try adding the following line to your RDP file:
This will force console mode, which should take over the locally logged-on user session. It is the same as running:
I have added issue #100 (feature request) to have this be an option in Create Client Connection. |
And to answer your question @j-omega, yes, what you seem to be experiencing is normal/expected behaviour for an RDP session. |
I added the line, but the RemoteApp connection still creates a duplicate session. I should also note that a regular remote desktop session connects me to the console session. I wonder if this is related to the fact that Windows 10 (not Window Server) is the RemoteApp host. |
Ok, thanks for the update @j-omega There are other RDP file options and local/group policy options that might affect this behaviour. For a list of RDP file options, check out my RDP File Editor: https://kimmknight.github.io/rdpfileeditor/ Let us know if you find a solution. |
Windows starts a separate session for RemoteApp. Otherwise, Explorer.exe from the remote PC would overlap the local explorer.exe.
(But it's better not to do that...) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I am hosting my remote apps on Windows 10 Professional 22H2.
When I connect to an app from a client PC, the app launches as expected. However, if I am already logged into the host PC, the remote app is started in a new (duplicate) user session. See the attached image below.
This is not the desired behavior. Ideally, if I am already logged into the PC, the RemoteApp connection would be made to the existing user session.
Is the behavior that I am observing the expected behavior, or is it due to a misconfiguration on my end?
The text was updated successfully, but these errors were encountered: