Span 2 monitors when using Remote Desktop Connection Manager
I've been using RDC Manager for a while on my Windows 7 Enterprise. I like the tool but have been unable to overcome one problem. How can I use both my monitors to run RDC Manager. I can easily do that using regular remote desktop services that come pre-installed with my Windows 7 Enterprise. I've already tried this without success :- Tools->Options->Full Screen->Use multiple monitors when necessary. If I can overcome this limitation, it will make my life much easier by me not having to minimize applications all the time. Thanks, SiddSP
October 10th, 2012 1:05pm

Give a try to command mstsc /span In previous versions of operating system there was higher limit for sum of resolution limitations, namely 4096x2048. Search for details for W 7. Regards Milos
Free Windows Admin Tool Kit Click here and download it now
October 10th, 2012 2:33pm

I have already tried that unsuccessfully. I think mstsc/span works only for inbuilt remote desktop services and not RDC Manager SP
October 10th, 2012 2:36pm

Hi, Please check if the following article is helpful. http://blogs.msdn.com/b/rds/archive/2009/07/01/using-multiple-monitors-in-remote-desktop-session.aspx http://www.techrepublic.com/blog/window-on-windows/use-multiple-monitors-with-windows-7s-remote-desktop-connection/5785 Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Niki TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Niki Han TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
October 11th, 2012 3:44am

Niki, I believe you didn't read the problem statement correctly. I said, its not working with Microsoft - RDC Manager. SP
October 11th, 2012 4:25pm

Have you read these in the above aritcle? The span mode has some restrictions: 1. The primary monitor must be leftmost. 2. The set of monitors must form a rectangle (i.e. identical vertical resolution, and lined up in exact straight line). 3. The total of the resolutions must be below 4096x2048 (ex. 1600x1200+1600x1200 = 3200x1200).
Free Windows Admin Tool Kit Click here and download it now
October 15th, 2012 2:45am

Hi, I am currently standing by for an update from you and would like to know how things are going. If you have any feedback, please let us know. Niki TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Niki Han TechNet Community Support
October 17th, 2012 1:22am

Hi, As this thread has been quiet for a while, I assume the issue has been resolved. At this time, we will mark it as "Answered". If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we'd love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Niki TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Niki Han TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
October 23rd, 2012 10:37pm

To Niki, I'll answer instead of the OP: Definitions: RDP: the protocolRDC: the architectureTS Client, aka mstsc: the client implementing the protocol that comes bundled with every Windows versionRDCMan: an alternative client that implements more options than mstsc /span is the "old" way of RDP to use multiple monitors. It basically extends the display of the remote desktop by simulating a virtual monitor containing more pixels than the physical primary monitor. The Remote Desktop server still thinks there is only one monitor, but thinks it's larger, thus rendering a rectangle that actually spans across the first and the second monitor. RDP 6 (the last version of the protocol, available since Vista / Server 2008), allows actually using multiple monitors, without any of the limitations of the /span option. This option (called /multimon) is only available when the RDC client can use the RDP 6 version (i.e. when both the server and the client implement the version 6 of the protocol, i.e. when mstsc in on version 6+ on both ends). In this mode, the server actually knows there are several monitors and renders correctly all monitors, even if their resolution is different both in height and width. In the post that you marked as answer, the solution obviously refers to all the limitations of the RDP version 5 and earlier, misunderstanding the question as "how to span across monitors with mstsc", and answering wrongly using limitations that are not there since Vista. So that's definitely not the answer. The question of the OP refers to a different client than the default one, called RDMan, written and distributed freely by Microsoft . The title of the question actually contained the full name of the tool, and the OP replied to the thread insisting on it. In this client, you can set up different connections and tile them on the screen, and you have access to basically all the options of the standard client (mstsc). But, it seems that those options are limited to the ones present in version 5 of the protocol and client. The question of the OP was: how can I access this "new" (bear in mind that it's been available for 7 years now) option from this client. I was looking for this too but I suppose that you cannot because the tool has been developed as a side project and has not been updated in quite a long time. To the OP, I would say that they should consider a tool like Remote Desktop Plus. It doesn't allow tiling the screens like RDCMan, and it doesn't have groups and option inheritance (which is a very nice feature), but it allows storing credentials and setting options for each connection, including the multiple monitor one, and can include a taskbar icon that starts with Windows. That's still better than mstsc. To the MSDN managers as a whole, I would like to say that it's probably better to have false negatives (actual answers not marked as such) than false positives (posts marked as answers when they are not). The policy of the forums to have marked answers to every question is just killing the MSDN forums altogether; it prevents dedicating the sufficient amount of time explaining both questions and answers. I just did dedicate the sufficient amount of time explaining the question just now (and, I hope, answering it), but that was mainly because it's Friday afternoon and I wanted to prove my point. I am sooo tired of seeing MSDN questions marked as answered show up in my search engine results, then come on the forum and realize it is far from answered. I don't know why I bother any more, instead of going to my favourite Q&A website directly. This is exactly why the OP didn't bother to show up on their thread any more. Marking a post as answer when the OP explicitly discarded it is just a slap in the face. And I'm sure I can go now to that same Q&A website and find his exact question with an actual answer (even if the answer is most likely "you can't do it").
November 2nd, 2012 12:31pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics