Dual Monitor and Remote Desktop

AID: 285
  • Status: Published

17400 points

  • Bytigermatt
  • TypeGeneral
  • Posted on2008-11-22 at 07:36:10
Awards
  • Community Pick
  • Experts Exchange Approved
  • Editor's Choice
Having a dual- or triple-monitor configuration does a lot to boost your productivity, but what about when you want to connect to a Terminal Services session? By default, a Terminal Services screen can either be configured to fill your screen, or to a number of pre-defined screen resolutions. It doesn't seem possible to open a session which spans across all your monitors.

1

The power of /span

The truth is, there is a /span switch which can do exactly that... open a new session to a remote Terminal Server or computer with RDP enabled, and cause the new session to fill all the monitor space on your desktop. To get going, all you need to do is go to Start, Run and enter mstsc /span. When you press OK, you will be presented with the typical connection dialog, where you connect as normal.

If you want to use the switch in a shortcut, I suggest you implement it as follows:

mstsc /span /v:<IP address to connect to>:3389
                                    
1:

Select allOpen in new window



For the /span switch to work, the MSTsc.exe help guide states that:

the monitors must all have the same height and be aligned vertically
                                    
1:

Select allOpen in new window


However, I can confirm that my 3 monitors are not the same height, and the switch still works perfectly fine for me.


2

A Custom Resolution

If the /span switch just doesn't cut it for you, and for some reason (perhaps you have a large monitor) you want a window to open at a non-standard screen resolution, then there are commands which can help you, too. The /w and /h switches allow you to set a precise number of pixels which the session should be in width and in height. You can either use the switch on-demand by entering mstsc /w:xxx /h:xxx at a command prompt (where xxx represents the number of pixels) and then connect as usual, or you can make use of the switches in a shortcut. The target of such a shortcut should read:

mstsc /v:<IP address to connect to>:3389 /w:xxx /h:xxx
                                    
1:

Select allOpen in new window



(Where xxx in the above represents the number of pixels wide and the number of pixels tall the session should be.



I hope this helps; please post a comment to let me know if it does.

-Matt

Comments

Expert Comment

by: DanRollins on 2008-11-22 at 14:24:17ID: 401

Thanks!  This is very useful.  I'd like to add:
   mstsc /?
displays a syntax summary for the Remote Desktop Connection app.  But it does not mention an option that I've found to be useful:
    /console
When used on the mstsc command line, you will be able to see the window that includes tray icons and U/I windows that are produced by System Services that allow "Interact with desktop"; that is you can see the desktop as it would appear if you were actually sitting at the remote computer.  There are few System Services that interact with the desktop, but if you need to administer one remotely, you will find the /console option to be very useful.

Expert Comment

by: KeremE on 2008-11-22 at 16:44:32ID: 403

DanRollins: /console switch is simply connects you to the Administraiton session of the computer you are logged into and it has currently been obsoleted by the new /admin switch.

Cheers,
K.

Expert Comment

by: matthewstevenkelly on 2008-11-22 at 16:45:57ID: 404

Please note that when connecting from a Windows XP Service Pack 3 or Windows Vista Machine (and the upcoming Windows 2008 operating systems) you will need to use /admin instead of /console.

Remember is this the machine you are connecting from, not connecting to.

The /admin or /console is best used when wanting to remote into the current logged in session of a Windows 2003 server. When you remote into a Windows XP or Vista machine it opens the session that is currently logged in (ie the one that has programs running etc) but with Windows 2003 it creates a new session.

Expert Comment

by: matthewstevenkelly on 2008-11-22 at 16:46:48ID: 405

/console still needs to be used from a Windows 2000 or Windows XP Service pack 2 or lower machine. /admin for anything higher.

Expert Comment

by: KeremE on 2008-11-22 at 18:33:59ID: 406

>....  (ie the one that has programs running etc) but with Windows 2003 it creates a new session.

not necessarily so. If there's no one logged on the consol it creates a new session but if a user is logged on brings the logged in session without creating a new one.

Expert Comment

by: KeremE on 2008-11-22 at 18:36:32ID: 407

While in XP it can logged on only the present session so there's no need to use /console or /admin switch for xp. If you want to logon to a user different from what is logged on the console on 2003, it wnats to logoff the current sessin and logon with the new user and displays warnings about it.

Author Comment

by: tigermatt on 2008-11-23 at 02:24:23ID: 409


If you are connecting to a Windows Server 2008 computer, the /admin switch probably won't do what you expect it to do anyway. You won't strictly be connected to the console, since the possibility of interacting with Session 0 is now reserved for services, not an interactive user. Instead, if you login as DOMAIN\Administrator remotely, and the Administrator is already logged into the console, the remote session will take over the console session. That's just the way it is now, unfortunately.

The /admin switch is there for when using the new RDP 6.1 client to connect to a Server 2003 or 2000 server, since on these operating systems /admin maps to /console.

-Matt

Expert Comment

by: mwvisa1 on 2010-01-28 at 12:08:26ID: 8590

Nice article, Matt.  Short but very sweet!  Great combination for my attention deficit, my heavy use of RDP and my love of using dual monitors.
Voted yes above.

Expert Comment

by: jason1178 on 2012-01-18 at 22:53:10ID: 34610

Good article.  We're implementing RDS now and this will be helpful.

Add your Comment

Please Sign up or Log in to comment on this article.

Join Experts Exchange Today

Gain Access to all our Tech Resources

Get personalized answers

Ask unlimited questions

Access Proven Solutions

Search 3.2 million solutions

Read In-Depth How-To Guides

1000+ articles, demos, & tips

Watch Step by Step Tutorials

Learn direct from top tech pros

And Much More!

Your complete tech resource

See Plans and Pricing

30-day free trial. Register in 60 seconds.

Loading Advertisement...

Top Windows RDP Experts

  1. kevinhsieh

    5,600

    0 points yesterday

    Profile
    Rank: Genius
  2. tsmvp

    4,650

    0 points yesterday

    Profile
    Rank: Genius
  3. totallytonto

    4,500

    0 points yesterday

    Profile
    Rank: Sage
  4. RobWill

    3,550

    0 points yesterday

    Profile
    Rank: Savant
  5. Coralon

    3,500

    0 points yesterday

    Profile
    Rank: Guru
  6. MrGraves

    3,190

    0 points yesterday

    Profile
    Rank: Guru
  7. lamaslany

    3,150

    0 points yesterday

    Profile
    Rank: Sage
  8. arnold

    2,800

    0 points yesterday

    Profile
    Rank: Genius
  9. dan_blagut

    2,800

    0 points yesterday

    Profile
    Rank: Sage
  10. ve3ofa

    2,800

    0 points yesterday

    Profile
    Rank: Genius
  11. RobSampson

    2,800

    0 points yesterday

    Profile
    Rank: Genius
  12. Tony1044

    2,800

    0 points yesterday

    Profile
    Rank: Sage
  13. matrixnz

    2,100

    0 points yesterday

    Profile
    Rank: Genius
  14. nappy_d

    2,100

    0 points yesterday

    Profile
    Rank: Genius
  15. Firebar

    2,000

    0 points yesterday

    Profile
    Rank: Genius
  16. The_Dark1

    2,000

    0 points yesterday

    Profile
  17. tenaj-207

    2,000

    0 points yesterday

    Profile
    Rank: Wizard
  18. JoeKlimis

    2,000

    0 points yesterday

    Profile
    Rank: Master
  19. charlestasse

    2,000

    0 points yesterday

    Profile
    Rank: Wizard
  20. Todar

    2,000

    0 points yesterday

    Profile
    Rank: Master
  21. reach2sandeep

    2,000

    0 points yesterday

    Profile
  22. Federicof

    2,000

    0 points yesterday

    Profile
  23. kdebugs

    2,000

    0 points yesterday

    Profile
  24. davorin

    1,350

    0 points yesterday

    Profile
    Rank: Sage
  25. bb_xpress

    1,340

    0 points yesterday

    Profile

Hall Of Fame