|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We were able to work around this issue by changing the node management to use "Let Jenkins control this Windows slave as a Windows". Although, that was tricky to get working correctly with our Windows 2012 Servers. (Really appreciated all the troubleshooting tips here : https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM?showComments=true&showCommentArea=true#WindowsslavesfailtostartviaDCOM-Windows64bitinstallationrelatedissues
We ended up having to make registry settings to get it working. If you need us to provide any additional information on this issue, we are willing to help.
Thanks