It handles the difference in resolution automagically, and just works! I get an RDP client, full screen, with alt-tab and other keys passed to the host (just like in the Microsoft RDP client, mstsc.exe), and it looks great. It mentions an RDP client I had never heard of: mRemoteNG I tried it, and BINGO. But then I found this thread on the Microsoft forums. I found no working solution on any thread here on Stack Exchange. (But I repeat, the stock remote desktop client should solve for this.) The version current at this writing is 2.7, and it did not cut it, despite a lot of tinkering. If it works at all, it would appear that only v2.2 of that tool can do what is needed. I found a solution, and have verified it both on the Surface 4 Pro and ASUS PB279Q 27" 4K/ UHD 3840x2160 monitors at full DPI, and the Dell XPS 13 (running UltraSharp™ QHD+ resolution (3200x1800)!) - I expect this approach will work for any high DPI remote.įurther, I have verified it when the host machine is "regular" DPI and high DPI (specifically ASUS PB279Q 27" 4K/ UHD 3840x2160 at native resolution).įirst, I should note that the Microsoft remote connection manager path ( mentioned here) did not work for me. The Microsoft RDP client is simply missing functionality that is required in this new, multi-DPI world. I must say, this has been very frustrating. We had a fine experience using legacy-dpi remote systems. Also, please don't tell us that only win10-win10 gives the right experience. Note: Please don't tell us to "log out and start a new session" on the host: This defeats the purpose, is not useful, and is a huge regression from the functionality we had before trying the Surface. Right now, from all our work so far, this is simply a missing feature. Note: We are looking to use the Win10 Surface as a real rdp client to Win7, 2008 and Win2003 hosts. How do I get my new Surface as usable as the old Vaio? my old Vaio laptop is great for remote desktop, and my new Win10 Surface is, currently, unusable as a remote desktop remote client. I tried using Remote Desktop Connection Manager, as proposed here, but it appears to lack the ability to give me a zoomed, full screen experience (perhaps I failed to find it, but I poked it a lot! There is a report that the current 2.7 version lacks the needed functionality, and that the older 2.2 version should work, but we did not find the 2.2 version for download). This makes no difference that we can see. We made sure the Win7 hosts are already on Win7-SP1 with kb2923545 installed. After 30 min of use, I can say clearly that the zoom feature in the win10 RDP client is NOT useful for real work. However, when I use it, I lose the ability to go full screen on the client (to use all client real estate, and to get alt-tab and other keys passed up to host). Yes, there is the Zoom feature in the rdp client. However, the problem I experience is the following: This issue is discussed and demonstrated in MS blogs here and here on SU In this case, the remote is the surface (with high resolution display), and the host is low (legacy 92 dpi) resolution display. Problem: When I use remote desktop from a Surface Pro 4, running Win 10, to a Win7 or Win2003 system, the high dpi of the Surface results in the remote desktop being too tiny to see.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |