I wrote some testing scripts with selenium, and they were working fine as long as I started them from my account, on a Windows 7 machine. But when a colleague started it from his account, on the same machine, some of the tests had a NoSuchElementException. What can cause that difference, maybe something the graphic-settings like the display resolution?
The scripts are written in Python, they are using Selenium-Webdriver with Firefox. The PC has Windows 7 Enterprise, 64 Bit, Service Pack 1, with Python 2.7.12 installed.
It looks like I’ve found the explanation: It’s the screen resolution. My colleague and I were connecting to the PC using RDP, and his connection had a smaller screen resolution than mine.
When I was starting a connection, explicitly setting the resolution to his values, the tests produced errors, and when I then started a new connection with my original settings, the tests were running fine again. And this was reproducible. 
I think the background is that on the page are many elements, which are moving dynamically with the page size, and some elements, which are fix or have a minimum size. So it’s possible that an element is covered by another, if the screen is too small, and with it the browser-window. Also a fix element could be partly out of the viewport.
What difference can the windows-user-settings make, when running a selenium-script?