Using Terminal Services RemoteApp™ programs on multi-monitor client computers

Using Terminal Services RemoteApp™ programs on multi-monitor client computers

  • Comments 43

One of the new feature additions to Terminal Services RemoteApp (TS RemoteApp) in Windows Server® Code Name "Longhorn" Beta 3 is multi-monitor support - the ability for a remote program to be dragged between primary and secondary monitors, to be maximized on any monitor and have it stick correctly to that monitor, etc. In other words, RemoteApp programs work just like local programs do in multi-monitor setups. Here is an FAQ of what TS RemoteApp multi-monitor support constitutes.

  1. What kind of multi-monitor configurations are supported?

    Just like the requirements for usage of the /span switch in normal remote desktop (described in an earlier blog post here), TS RemoteApp also requires the following specifications for the multi-monitor setup:
    • Equal resolution monitors
    • Total resolution of all monitors not exceeding 4096 x 2048
    • Top-left monitor being the primary

      Any other kinds of multi-monitor configurations are not supported with TS RemoteApp. Here are a few examples of multi-monitor setups that are unsupported:
    • L-shaped multi-monitor configuration
    • Unequal number of monitors on the top and bottom row (if there is a two row multi-monitor setup)
    • Center or right monitor being the primary
  2. What do I need to do in order to enable multi-monitor support in TS RemoteApp?

    As the administrator, nothing, as long as the client computers are all in the supported multi-monitor configuration. By default, in Windows Server "Longhorn" Beta 3, the RDP or MSI files that are generated by using the RemoteApp Wizard allow multi-monitor usage of RemoteApp programs because the span monitors:i:1 entry is present in the RDP file.

    As the end user, you just need to launch the remote program just like you would do normally.
  3. Can bad things happen if a TS RemoteApp multi-monitor enabled RDP file is used from a single monitor client computer?

    No. The span monitors:i:1 option is ignored when the client is not multi-monitor. Hence, there are no side effects of any kind when using these RemoteApp RDP files from single monitor clients.
  4. Will RemoteApp programs launched from a Terminal Services Web Access (TS Web Access) portal on a multi-monitor client also have this support?

    In Windows Server "Longhorn" Beta 3, RemoteApp programs launched from a TS Web Access portal do not work across multiple client monitors even in the supported configuration described in FAQ #1. This will be addressed in the next interim milestone release of Windows Server "Longhorn".
  5. How do I turn off TS RemoteApp multi-monitor support for a particular multi-monitor client computer?
    • If the administrator has already generated the RDP file(s) by using the RemoteApp Wizard and pushed them on to the client computer, she will have to manually edit the RDP file(s) on that client computer to set the span monitors field to 0, i.e. it should read span monitors:i:0.
    • If the administrator has already generated the RDP file(s) by using the RemoteApp Wizard and the user is launching the RemoteApp program through a TS Web Access portal, there is no way for her to turn this functionality off for a particular client computer.
    • If the administrator is in the process of generating the RDP or MSI file(s) by using the RemoteApp Wizard and decides that for a particular client computer she does not want to provide TS RemoteApp multi-monitor support, she can use the "Custom RDP Settings" tab in the TS RemoteApp Manager tool for this. All she needs to do is to put "span monitors:i:0" in the text field on that tab and the generated RDP or MSI file(s) will have the functionality turned off. Then, she needs to push this particular set of RDP or MSI file(s) to the target client computer.
  6. What client operating system do I need to test this feature?

    As of now (7 May 2007), this feature can be tested only with Windows Server "Longhorn" Beta 3 being the client operating system, i.e. both the client computer and the remote server must be running Windows Server "Longhorn" Beta 3.
Leave a Comment
  • Please add 7 and 2 and type the answer here:
  • Post
  • am curious to learn more about your deployment so I can help troubleshoot the issue you are experiencing.  From your description, it sounds like you have things set up correctly.  Do you have an email address that I can use to start a correspondence?

  • I have the same problem as davidmohara.  Everytime I run Remote Desktop, it resizes my taskbar, and I have to manually resize it.

  • Hi, I am seeing the same problems with the taskbar resizing - on a dual monitor Vista Urtimate 32-bit machine. I am willing to help you diagnose it more closely, if needed - you can reach me at rdp_taskbar-at-oxel.net.

    Thanks.

  • Hello,

    I'm trying to use any Windows 2008 Applications that I previously published using RemoteApp manager and I can successfully lunch the application but I can't cross my application on my second monitor. The line span monitors:i:1 is there and I can succesfully expand my full Remote Desktop session on both monitor. Any Idea ?

    I'm using Windows VP Pro SP2 with RDP 6.0 as my client computer.

    Thanks

    Denis Chicoine

  • Denis:

    The RDP 6.0 client does not support RemoteApp spanning, but the one in XP SP3 (and Vista SP1) will do so.

    Rob [MSFT]

  • Hi,

    This porbly won't get read being 2 months after last post but anyways!

    I've got session broking set up on 3 win2k8 Ts's (RC1's) and can connect using the farm name on each of them.

    I can't directly connect to the servers though using their machine name nor their IP address - everytime it just starts a session on the next available server as if its still trying to share the load.

    Is anyone elses experiencing this?

    Thx

  • I'm also experiencing the taskbar resizing from 2 lines to 1 when I RDP into my office session from home.

    As requested of others, details as follow:

    Office resolution: 1280x1024 and 1280x1024 (left monitor primary)

    Home resolution: 1280x1024 (single monitor)

    Office taskbar location: On the left primary monitor

    It's also worth noting I reduce the color quality down to 16 bit in the RDP client, and I'm using Vista 32bit (at home) to connect into XP 32bit (at office)

    This seems to be a problem afflicting more than one person - is there any fix available?

  • If i need RemoteApp only, how i can disable Remote Desktop on Server for users?

  • Hello,

    I'm using Windows VP Pro SP2 with RDP 6.0 as my client computer.

    Thanks

  • If the administrator has already generated the RDP file(s) by using the RemoteApp Wizard and pushed them on to the client computer, she will have to manually edit the RDP file(s) on that client computer to set the span monitors field to 0, i.e. it should read span monitors:i:0.

  • I have two monitors at work (19" 1440x900) and one at home (17" 1280x1024). When I RDP from home I can see only one of the monitors. How can I switch to the second monitor and back?

    Thanks

  • You don't.  The only options you have are to connect to the primary monitor or to span the Remote Desktop Connection across both remote monitors using mstsc.exe's /span switch. This option is available in the Windows RDP Client 6.x.

    Patrick Rouse

    Microsoft MVP - Terminal Server

  • Has the client OS requirements change for running remote-apps across multi-monitors?

  • I just discovered that my remote apps would only work on my main monitor because my primary monitor is

  • Is it possible to modify the compression on the server side besause I need a lossless compression of the GUI of the application on the client side ?

Page 2 of 3 (43 items) 123