-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
No multiple concurrent logins in a VM configuration. (Goal: Azure setup) #216
Comments
Are you using the same user (which logged in locally) for testing RDP? |
No, I tried other useraccounts, I tried with rdpcheck, I tried with 'Single session per user' unchecked. All results in popping up the disconnection request like in the screenshot :( |
are you using remoteFX at your guest-machine? |
Yes I do, is that the problem? I'm able to test later on today! |
Yep, see this issue: #127 and try disable RemoteFX. |
Oops - I tested and you are completely right! Now I just wonder if the same behaviour occurred when I connected to the bare metal (non-VM) install of Windows 10... Contrary to what many believe, RemoteFX between two Windows 10 (since RDP8 I thought) is possible.
|
Alright, closing as duplicate of #127. |
I'm connecting (or trying) a Windows 10 N Enterprise VM on a Windows Server 2016 host. All are up to date and the wrapper config / installation looks fine. But as soon as I try to connect another session I get asked to disconnect my current session, as if no wrapper would be active. The screenshot shows it all:
The last time (two weeks ago) I configured the same setup but on 'real' instead of virtual hardware and then all was fine.
My goals is to run a 'rdp wrapped' Windows 10 VM on Azure. Yes I could run session directly on the server instead of on the VM but my use case does not allow me to do so. I other words I really like to have it on a virtualized Windows 10 installation.
The virtualization should have no influence as far as my reasoning goes (Since I'm connecting to the VM's RDP and not the Server)... Any clues what's going on here?
The text was updated successfully, but these errors were encountered: