Supporting server (such as Windows Server 2008 r2) the "use multimon:i:1" would apply. If you were connecting to a true multimontior Add the "span monitors:i:1" line to the end of the saved file with a text based editor and it will solve this issue. In MSTSC /SPAN it will connect spanned and when you save it it will not open to a span. When you save the RDP file, it does not add the "span monitors:i:1" command line which /span triggers. In Windows RDP7, the use multimon:i:1 flag is altered by using the "use all monitors" checkbox in the saved file. Hopefully whatever the fix is can be done from here, because I really don't feel like driving 300 miles again anytime soon! :)īrian this may be too late for you (lol) but experiencing the same thing I have found out why. We have probably a dozen or so users with the same setup and they've never experienced this issue. She's out today and tomorrow, and I'd like to have this working normally for her
I recreated her Windows profile a few minutes ago and that hasn't fixed it either. In the meantime I've tried deleting and reinstalling RDP 7 and it had no effect. As a temporaryįix, I created a batch file to do just that so she can work with both screens. I found that if I call the client using mstsc /span it will work. I made a trip to the office yesterday, and upgraded her to RDP 7 hoping it might resolve the issue. We edited the shortcut they use to automatically span to both We provide the employees with a shortcut to connect to our terminal server. I've got a remote user that has dual monitors (they're both set to 1024x768, configured identically) .
0 kommentar(er)
