Remote Desktop Connetion displays Very Small Icons and Jump Lists on Remote Machine

Anonymous
2014-06-28T22:12:39+00:00

On my remote machine, the desktop icons, icon titles, taskbar and jump lists are puny, very difficult to read the small font size.

I've tried all of the various display/sizing options in my Surface's control panel, and also the display setting tab in Remote Desktop Connection, and have not found any comnbination that works well on the remote and Surface Pro 3. (Also, the sizing options are not so convenient anyway since a sign out is generally needed.)

 I've never had this problem and regularly use RDP on various machines. Are there others with RDP display issues?

Surface | Surface Pro | Network

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

64 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2014-07-06T14:51:38+00:00

    The surface pro 3 default text size slider setting is somewhat larger (the 3/4 setting on the slider). As a result, unless the remote machine has the same setting, a sign out on the remote is needed.

    Simply sign out on the remote machine, and the next time you sign in remotely the icons/taskbar should be sized correctly. At least that was my experience.

    The downside: you need to log out of the remote before logging in with any machine with a text size setting that is different from the last login.

    It would be nice if this sign out process was not necessary.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-06-30T20:46:00+00:00

    On my Surface RT when remoting into the same Win 8.1 Pro machine the display properties on the remote show 1366x768, naturally, adding a bit of mystery of why 1440x960 is too low of a resolution to use modern apps when connecting from Surface Pro 3 using Remote Desktop Connection Manager.

    When remoting from the Surface RT, the display appears completely normal.

    Thanks again.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-06-30T20:27:44+00:00

    Thank you, Frank. The icons, etc., display correctly using RDCM, with or without deselecting "Inherit from Parent".

    Unfortunately, when connecting with RDCM to a Win 8.1 Pro machine I cannot use the remote machine's modern apps. When I try to load a remote modern app I get a message that the screen resolution is too low: when I connect using RDCM the remote is showing resolution of 1440x960. I have the display set to connect using full screen. I have not figured out how to get a higher resolution without getting the scroll bars for the remote session.

    I'll let you know if I find anything else.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-06-30T17:43:23+00:00

    Thank you, Frank. The icons, etc., display correctly using RDCM, with or without deselecting "Inherit from Parent".

    Unfortunately, when connecting with RDCM to a Win 8.1 Pro machine I cannot use the remote machine's modern apps. When I try to load a remote modern app I get a message that the screen resolution is too low: when I connect using RDCM the remote is showing resolution of 1440x960. I have the display set to connect using full screen. I have not figured out how to get a higher resolution without getting the scroll bars for the remote session.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-06-30T15:42:16+00:00

    >> 1- Download this tool, create a file and add your remote machine.

    >> http://www.microsoft.com/en-us/download/details.aspx?id=21101

    I'm connecting from Surface 3 Pro to Windows 8.1 Pro. The Remote Desktop Connection Manager does not state that it's Win 8.1 compatible.

    Can I still use RDCM?

    Do I install it on the Remote machine?

    Where would I add the file to the remote machine?

    That screen shot is from my Surface PRO 3. You don't need to install it in the remote machine.

    Was this answer helpful?

    0 comments