On my side, the service needed to be Local System to be able to launch properly, which prevent GUI and graphical context to be run inside the service. Since I needed the GUI context for some unit test (OpenGL unit test was problematic), I had to change the service user for a local user. That prevented the jenkins service from booting at startup.
Sorry I didn't investigate why, since we moved the master from Windows to Linux to avoid those problems. Starting the slave with a simple batch script that connect to the master solved the problems: LaunchSlave.bat "c:\Program Files\Java\jdk1.8.0_121\bin\javaws.exe" "http://MyHost/Jenkins/computer/Windows%%2010%%20Node/slave-agent.jnlp"; Put it into the Start Menu Startup folder for a local user and you are done. You can make the Windows slave machine auto login into that user. I may suggest to put your master into a VM with Linux, that really solve those problems if you need GUI context, if you don't need it, make sure you use the default Local System as Jenkins service user, it should work. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1e7337f4-93bd-4d96-a27e-001cfe3ae30c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
