![]() After removing or if the ShareFile for Outlook Plug-in does not appear on the list, click Add….If the box was already checked or if the authentication did not start automatically, select the ShareFile for Outlook and click the Remove button.If the ShareFile authentication does not start automatically, continue to the next steps. On the COM Add-Ins screen, check the box next to the ShareFile for Outlook if it is not done so already.Click Add-ins, then Go… next to Manage COM Add-ins.VMware Workstation is yet another example. It's an issue with many different applications. Oddly enoguh, I use MacOS with the official Microsoft RDP client and it doesn't suffer from a tiny mouse icon.īut this is a bigger issue than just a tiny mouse icon. I also use MacOS and Linux with high DPI displays and don't ever have to worry about this. Again, it's unsupported, but incredibly popular.Īnd it doen't matter whehter you use RDCMan or the built-in mstsc.exe, the experience is the same. Here we are years later and stuck at 2.7 with a legitimate issue that isn't being fixed. Then version 2.7 came out and brought some welcomed changes. RDCMan, while not an officially supported application, must be one of the most popular downloads from Microsoft's site and went many years without seeing an update. It's such a shame that manufacturers have moved to using beautiful high DPI displays and Microsoft's most modern operating system that's been through 3 additional feature updates since the original release doesn't have a way to make the experience consistent It is a little blurry,īut text and things like mouse pointers and cursors are easily visible. My RDP sessions zoom / scale to fill the space in my RDCMan window. After this solution, my client area is now way smaller, even under the View menu under "Client Area". By default, the client area for me is something close to 3474x1995 like yours, and my 1920x1080 RDP sessions are small and centered in the middle of this area, EVEN with the "Scale docked "Remote Desktop Settings" tab in RDP manager. To confirm that I'm talking about the same thing - I use a 4K Monitor (3840x2160), and I RDP to my Azure VM's using 1920x1080 (in the This is a little deceiving because itĪlmost reads as if this default configuration would be equivalent to unchecking the "Override." box.Īfter doing this, close and reopen RDCMan, and now your client area should scale up to fill the space in the window. Uncheck "Override high DPI scaling behavior", by default this is checked and the 'Scaling performed by' menu has "Application" selected.Right-click the RDCMan icon on your taskbar or start menu and choose Properties (I have to right-click, then right-click again before I see 'Properties'). ![]() I believe you can solve your issue by changing the DPI settings within the properties of the RDCMan shortcut /. I found this elsewhere and it worked for me: The RDP client has come a long way recently but still has a way to go until it properly supports the scenario as mentioned above. I haven't tried but believe that connecting to newer windows OSes is fine. Displays at the full resolution for the monitor hardware (1920x1080) everything is the correct size but this time the mouse pointers are the expected "normal" size. This can be fixed by auto hiding or removing the task bar from that screen.Ģ) On the normal DPI screen, full screen. ![]() One minor issue is that if that screen has a windows toolbar, "full" screen doesn't quite fit and we end Displays at the full resolution, but with correct 200% scaling so everything looks as expected. Checking it will produce the same results as with RDP.ġ) On the high DPI screen, full screen. Instead use Remote Desktop Connection Manager (RDCM) 2.7 but with "Disable display scaling on high DPI settings" UNCHECKED. ![]() Editing any kind of text is unusable because you lose the mouse pointer when hovering over those areas. (I suspect because an I-beam bitmap for the cursor set that small doesn't exist). What's worse, the vertical I-beam text cursor doesn't appear at all Displays at the full resolution for the monitor hardware (1920x1080) everything is the correct size except the mouse pointer is TINY. Displays at the full resolution, 100% scaling so everything is tiny and it's close to unusable.Ģ) On the normal DPI screen, full screen. Connecting to other machines (in this case Windows Server 2008R2 SP1):ġ) On the high DPI screen, full screen. Connection target: Windows Server 2008R2ĭPI scaling in Windows 10 is way better than it has been but with room for improvement.Two additional external NORMAL-DPI screens 1920x1080. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |