Running a Unity3dBuilder Plugin step on a Jenkins slave configured to run as a Windows service is broken.

If you try to run a Unity3dBuilder Plugin Jenkins step on a Jenkins slave configured to run as a Windows service the Unity build log output piping to the console output is broken and doesn't show up in Jenkins (i.e. the build output only shows up under C:\Windows\System32\config\systemprofile\AppData\Local\Unity\Editor). Also, when running the Jenkins slave as a Windows service, the Unity3dBuilder Plugin Jenkins step will hang forever when the batch file step completes.

Note that the Unity3dBuilder Plugin step works perfectly fine if you change the Jenkins slave to run as a non-Windows service (i.e. the console output redirection works OK and the Unity3dBuilder Plugin Jenkins step won't hang).