Welcome to http://jasonmiller.ca Sign in | Help

Jason's Blog

my take on SBS, EBS, and solutions in the small and mid-size market!
Dual Monitor Support in Remote Desktop Connections Client v6!
Declining hardware prices and increasing demands for productivity improvements have influenced business investment in multiple monitors for the desks of executives, power users, and administrative staff. LCD display units have decreased the desktop footprint compared to CRT monitors, and since the launch of Windows XP back in October of 2001, laptop manufacturers have been improving on adapter and driver support for multiple monitor on portable equipment. Today, it is rare to find a laptop that will not support extended Windows Desktop on an external display.

Another emerging trend is the growing familiarity and reliance upon remote desktop technologies. Increasingly, IT Professionals and power users count on remote desktop services to connect efficiently to remote networks to perform business related functions, from support to day-to-day job functions. It’s not uncommon for a remote worker to rely exclusively upon remote desktops to connect from a home office or remote location to their business Terminal Server or even to their work desktop via Remote Web Workplace if their network core is Small Business Server 2003.

Microsoft recently released an updated Remote Desktop Connection client (Terminal Services Client 6.0) for Windows XP and Windows Server 2003 products. Download links and related information about this product update is available at: http://support.microsoft.com/kb/925876.

One of the interesting new features in the updated Remote Desktop Connection client is support for spanning multiple monitors!

If you have multiple monitors on the system you are running the Remote Desktop Connection client from, you can stretch the virtual desktop of the host system to span your monitors. It’s important to note that only rectangular shapes are supported – dual monitors with different resolutions will not work with multiple monitor spanning.

If you know the resolution you want for the virtual desktop (great for when you wish to have a less-than-full screen window span monitors), you can now state explicitly the dimensions you desire:
          mstsc /w:2048 /h:768 /v:"server"

The above example would create a full screen spanned virtual desktop on two 1024x768 resolution displays.

Or, if preferred, the Remote Desktop Connection client can figure out the size automatically (great for full screen view):
          mstsc /span /v:"server"

The above example would create a full screen spanned virtual desktop to match the rectangle size of your dual displays.

There are some limitations of dual monitors and the updated Remote Desktop Connection client:

  • The total resolution on all monitors must be less than or equal to 4096 x 2048.
  • All monitors must be aligned side-by-side, and have to be the same resolutions. Vertical alignment is not supported.
  • The remote session sees the virtual desktop as one very large virtual desktop. It doesn’t know you are using two monitors.

In order to make the most of the dual monitor support, a very nice little tool to have installed on the Remote Desktop host system is SplitView (www.splitview.com). This inexpensive tool adds two buttons to the top right corner of system windows in the title bar area. By pressing the left arrow, the active window is directed to move to the left and use 50% of the screen width. By pressing the right arrow, the active window is sent to the rightmost 50% of the screen. As the virtual desktop is split equally, the consequence of these actions in a Remote Desktop Connection is to move the window to the left or right display on your desk.

And you don’t necessarily need to have dual monitors on the host system! The host might have only one monitor, but you can still span the single virtual desktop across your dual physical displays on the Remote Client PC system. For people who use remote desktop connections on a regular basis, you can get more out of your remote sessions and your investment in dual displays with the updated client and the /span switch! Adding the third party application to assist in managing the windows in your virtual desktop will only improve your overall experience.

Posted: Saturday, March 03, 2007 2:40 PM by Jason
Filed under:

Comments

DaCeige said:

This needs to go on dig.com.  You've just made my day!

# April 5, 2007 6:39 PM

Milos said:

Cool...

# April 11, 2007 4:22 AM

Jason said:

I just noticed on the splitview website, that there is an update for 2007 that indicates support now for 3 and 4 monitors!  If you've got multi-monitors, you should check this product out!

# July 20, 2007 8:43 AM

Richard said:

Gridmove is a Freeware tool! Little less user-friendly as Splitview but also not so expensive! Works great and easy within terminal sessions.

http://www.donationcoders.com/jgpaiva/gridmove.html

# November 16, 2007 4:12 PM

Jim Z. said:

Check VDM (Virtual Display Manager) - http://www.ishadow.com/?tabid=115.

VDM supports any number of monitors local or remote, can supplement native Citrix multi-monitor support and costs a fraction of SplitView for Terminal Server (free for Microsoft MVPs).

PS. Try running mstsc.exe full screen within the remote session when either VDM or SplitView is on and compare :)

# January 27, 2008 5:57 AM

Phil said:

Wow telecommuting just got a whole lot easier....LOL. I was thinking the other day, "Man I wish I could extend my RDC sessions to my other monitor"  What a life saver!!

# June 12, 2008 8:45 AM

mkmcgregor said:

As an extensive user of RDP for quite some time, it is a real great feautre. I only recently discovered /span, and it's night and day more useful. I use four monitors at work, having only one at home via remote desktop was a pain. The additional space provided by my two widescreens, gives me about 2.75 width of work monitors.

However, problems with application organization and finding hidden dialogs that pop up off screen can happen.

Most windows can be move back into position by accessing the task bar, right clicking on the windows item, select restore if it's currently maximized, and then select Move. Immediately hit up arrow and then move the mouse. You'll see your window outline following the mouse pointer. Click anywhere and the window is now back on your usable virtual desktop. Certain dialogs or applications may not move as an option. This means that you need another apppication that can change the current x/y for a running application.

Another problem is that once you get back to the office, the position and alignment are off. If appears to place your virtual desktop in the middle of real desktop; composed of x monitors. So, applications like Visual Studio that I normally run with view windows pinned together and undocked from the main are in an unusable position and need to be moved everytime you use RDP and then return from it. Just a waste of time and not a real problem.

Also, if any one monitor at the place from which you want to run RDP is not the same size, /span will only run in one of them. Even if two are the same and one different, only one will work regardless of the setup. You can still manually set the size and use non-fullscreen mode to create a windowed view, but then you loose screen realestate to border and titlebars and some keys behave differently for task switching and the like. Fullscreen mnode, if possible, is far better.

# August 10, 2008 6:53 AM

Alex said:

Guys, check this out - MSTSC support of multiple monitors without... "/SPAN" switch:

http://www.ishadow.com/Forums/tabid/56/forumid/7/tpage/1/view/topic/postid/690/Default.aspx#690

That also addresses issues with monitors that are not span compatible, for example monitors of different height (usually laptop coupled with a larger desktop monitor)

# September 17, 2008 4:57 AM

nelson said:

I've been looking for this answer for some time now.  

Thanks a lot!!

# November 13, 2008 3:22 PM

Mark Derail said:

Consider the following:

desktopwidth:i:2644

desktopheight:i:1088

session bpp:i:32

winposstr:s:0,1,0,0,3660,1122

Will open as expected...but in the screen properties of the remote desktop, you are in 16 bit color mode.

Now, if you increase width by even 1 extra pixel, no matter how you setup the "winposstr:", you will fall to 8 bit color mode.

So yes you can be 4096 pixels wide, you will be in 8 bit color, which is quite lousy.

# October 23, 2009 8:27 AM

Mike said:

This is a great tip... but my color depth has decreased from 16 bit color to 8 bit color...  

I tried searching for Remote Desktop parameters and the first link was this:

http://windows.microsoft.com/en-US/windows-vista/Use-command-line-parameters-with-Remote-Desktop-Connection

But... There was unfortunately no parameter for specifying color depth.  Is there a way of fixing this?  It's dot a deal breaker if I can't but it would be nice.

Thanks again!

# November 9, 2009 12:24 PM
Leave a Comment

(required) 

(required) 

(optional)

(required) 

Enter the text you see in the image:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS