I wrote a automation script using Winbatch that executes another desktop application and interacts with some of the GUI controls. I compiled the Winbatch script as an executable for distribution, both as an exe for running as a regular app and an exs for running as a service. It is running in several different environments on a variety of versions of Windows from XP, Server 2003, 7 and Server 2008. Some of the clients are running the exs as a Windows service and it is working just fine, but other clients that also want to run it as a service are having a problem where the automation script starts but it doesn't appear to do anything - the other application that it is supposed to execute and interact with never starts. If running the exe not as a service on the same client it works just fine. Any ideas about what might be causing this and a possible solution?