At a customer I have got a really strange and annoying problem. The customer has got a Hyper-V VM with 2012 R2 Server as a RDS server aka Terminal Server.
One user has got issues with his multi monitor setup. The connection settings seems to be OK. It is set to full screen and the checkbox for the multi monitor configuration is enabled. Theoretically this works because the user sees a correct setup with one primary display and one secondary display. The settings itself are correct.
1. Primary display: 1680*1050
2. Secondary display: 27" 1920*1080
The display settings on the client are nearly the same except that the numbers of the two monitors are different (those numbers you get when you click identify at the resolution change window). On the Windows 7 client the primary display number 2 and the 27" has got the number 1. On the Terminal Server the primary display has got the number 1 and the 27" display has got the number 2. But the corresponding resolution at the display number is correct.
Now the problem. Everything seems fine, the desktop is expended. But when the user is "touching" the top or bottom edge of the screen the display is scrolling (in full screen) - like in a 3D game scrolling over a map. The user told me that both screens are scrolling equally at the same time. I am not sure but the user told me that if he is going to the bottom the CLIENT task bar appears. Changing the task bar of the client to fixed the user told me that the task bar will always show up. - Strange that CTRL + ALT + BREAK does not work.
I tried to press CTRL + ALT + BREAK twice, changing the resolution to a fixed value and back to full screen again, changing the primary display to the new 27" monitor, adding smart sizing:i:1 to rdp file and upgrading the Intel HD
4600 laptop graphic drivers (must be downloaded from Lenovo :/). NOTHING helped :(.
But this strange behavior does not exist on the client. Opening two programs (simple notepad e.g.) on each display and maximize them and moving the mouse the screen borders won't show this problem. It only exist on the remote session.
Now the "funny" part. If I connect with Team Viewer to the client the problem disappears as long as I am connected. If I disconnect the problem shows up again.