I'm a little confused. Isn't remotefx a strictly (or mainly) server side solution, so that so long as we enable remotefx on the WinServer 2016 server, all we need is a "plain old" rdp client (eg normal guacamole) and it should work? That is, does remotefx not work just like vnc-like solutions and transmit the computed bitmap image back to the rdp client, so the rdp client need not have any code changes? The reason I ask this is twofold: one, there doesn't appear to be any specific requirement for the rdp client to support remotefx, though the documentation is a touch confusing on this regard. And two, thinrdp seemed to support remotefx years ago, and I have a hunch they never recoded anything. (Note: In our use case, we are only using remoteFx to use the 3d accelerated NVidia graphics card that is on the winserver 2016 vm running on the google cloud; we don't care about USB redirection etc.)
If the rdp client (eg guacamole in this case) really must change in order to "view" remoteFx enabled screens, then what about simply installing a vnc server (such as TightVNCServer or RealVNC Server or UltimateVNC Server on the Win Server 2016 VM) and then using guacamole to connect to the win machine via vnc? (I believe that vnc will still allow the WinServer machine to use the NVidia graphics card, and I believe that guacamole shouldn't have any trouble at that point, since presumably vnc is just sending bitmap images back?) Lastly, if none of the above ideas work (or work well), would there be interest in all the people on this thread and any others that have desired remoteFx support in guacamole to maybe band together and sponsor this feature (so it's done sooner rather than later)? We're a tiny company (1 founder + 5 part-time developers, but I'm sure we can help.) -- View this message in context: http://apache-guacamole-incubating-users.2363388.n4.nabble.com/RemoteFX-Session-Sharing-tp1080p1277.html Sent from the Apache Guacamole (incubating) - Users mailing list archive at Nabble.com.
