I tried rebooting this slave a few times, but couldn't get it to connect. I then retried re-imaging the host, but it gets stuck waiting for user credentials to connect to the network shares. Please have a look at this slave and see what can be done to resurrect it.

I think this is finished reimaging now. It was an issue with some old cruft in the imaging system (which predates our two windows admins) that's since been fixed.

despite the reimage on the 18'th and multiple forced reboots it is still not connecting to the point where it takes any jobs.

callek: so what's the failure mode? We'd need more info to go on to diagnose.

This is quite interesting: * Its connected to a buildbot master (111) ** Both slave and master twistd.log's confirm this * Its in buildbot configs properly (as far as I can tell) * VNC is up and no dialogs indicating failures * Able to ssh in * Still not actually taking jobs. I've pinged catlee on irc, and redirecting needinfo to him

I don't get why, but this has taken jobs after I locked it to buildbot-master109. instead of buildbot-master111 which it had allocated to. This was at the advice of catlee