For trouble-shooting purposes, it's often convenient to launch a Windows command prompt as the 'SYSTEM' user (This is the user account all Windows services run.)
- Open command prompt (keyboard: Windows key+R), and type "cmd.exe" to get a command prompt as you
at 12:34 /interactive "cmd.exe"(change 12:34 to one or two minutes ahead of the current time.)
- Wait for a few minutes
- You should see a new command prompt. That one runs as the system user.
- You can verify that by running "echo abc > x" and then run "dir /Q" to see that the newly created file is owned by administrators.
When all else fails and you still can't convince the SYSTEM user to do what you want, consider running Jenkins just as a
start-up program on admin with auto-login normal user. This is much easier to set up. e.g.
sc config %jenkins_service_name% obj= %windows_domain%\%domain_user% password= %password%
Note, there is a space after equal signs, =