this machine needs to be prepped for loaning. normally we request: "please move the above slave to the loaner ou and reboot it" *but* this host recently had VS2013 installed on it and we need it to be available for the loanee. I am not sure the exact process involved in putting this machine in the 'loaner ou' but it if will mean losing VS2013, we may need to look at forking that process. marcko, do you know what we should do here?

2013 will not be uninstalled if we change OUs. Should I go ahead and move it over?

(In reply to Mark Cornmesser [:markco] from comment #1) > 2013 will not be uninstalled if we change OUs. Should I go ahead and move it > over? yes please. Thought I'd double check. :)

It has been moved to the loaner OU and verified through VNC.

This loaner bug for this has been resolved. I wish to use this machine now in staging so I need it to connect to buildbot. However rather than a full reimage, I would like to keep msvc2013 installed on it. /me learned that changing OUs and prepping for a loan doesn't remove any newly added programs but I would imagine a full reimage on this slave would remove it. Is it possible to just have it back in a state where I can connect it to my staging buildbot instance again but keep vs2013? Sorry for ignorance, maybe this requires something from my end?

It has been moved over to the correct OU. In most cases were a machine is coming back from being a loaner a reimage is done to be on the safe side just in case there had been a configuration change or additional applications installed. In this case we may be safe with moving it and a reboot. However, because this is not a typical situation I don't know if there will be oddities from being moved between the two OUs. Please let me know how it works out.

Thanks Mark! Everything seems to be fine. I am currently running a build on my staging env :) Resolving on that basis.