title: Jenkins Integration Tests on Windows: problems with some GUI functionality
body: <p>We are running our GUI integration-tests on a Jenkins build-slave.
  The slave is running Windows Server 2012. Our application is built on Java RCP and uses SWTBot for testing.</p>
  
  <p>The problem is, that most of the time, the tests fail at a point where the user (or in this case SWTBot) presses the key combination Strg+Z. It simply does not seem to have any effect.</p>
  
  <p>Then, if we log on remotely on to the server and actually watch the build process (without interaction), the tests will always complete as success. So I guess it has something to do with actually displaying the Desktop to a session. In rare cases though, the tests are also succeeding without anyone being logged on remotely to our build slave.</p>
  
  <p>Does anyone know what could be going on?</p>