title: How to debug a background IDE that Jenkins starts as a SYSTEM user
body: <p>We are successfully using the Jenkins CI server on Windows 7. It mainly does compiles using CodeWarrior. Using the Win32::OLE library in Perl to automate the IDE, I recently added a new Unit Test job that compiles then also starts the debugger, runs a test thread on target hardware, then stops. It works fine when I start it from a command line under my user name, however when Jenkins starts the same task the IDE consumes all the CPU and never ends. Under the Windows Task Manager I see the IDE running as a SYSTEM user. I suspect there's a new pop-up message I haven't accounted for in my OLE automation, but can't see it because it's a background task now.</p>
  
  <p>Is there a tool or technique to help debug windows that Jenkins starts as a system user but aren't visible?</p>