Hello.
I have an RDS desktop pool with one Windows Server 2008 R2 RDS host, set to PCoIP only. Running 6.2.0.
This RDS host has been around before we even started doploying View, so a lot of our users are still using it through direct RDP.
However, some of these users also access that RDSH via View, e.g. from PCoIP zero clients in conference rooms.
The problem is, if a user that already has a normal (non-View-brokered) RDP session (be it active or disconnected) on this server tries to connect to it via View (expecting to resume his existing session), it won't work, because the protocols/connection types (RDP-Tcp vs. VMware-RDS) aren't compatible.
Here's a screenshot of the error the user gets, from the (latest) Horizon Client:
It's even worse when trying to connect with a zero client, as there's no option to log out the existing session.
This also works vice versa: you cannot connect via direct RDP if there's a View session open for that user.
I have already tried disabling the "Restrict each user to a single session" setting in the Windows RDSH configuration, in the hopes that RDP-Tcp and VMware-RDS sessions would be able to coexist that way.
This helped a little, I could now successfully open new direct RDP sessions even when a View session already existed for that user, not the other way around though.
Other possible workarounds could be to automatically log off sessions on disconnect, but I'd like to avoid that if at all possible. Also, this approach wouldn't help for active sessions anyway.
Is there any way to solve this, short of only letting people logon through View?
Thanks!