I currently have ix-mn-w0864-001 loaned to me (Bug 1015418). If we can use that, great, if not we can use any other machine and i'll return my loan. Currently, ix-mn-w0864-001 has vs2010 SP1 installed on it along with vs2013. This SP1 version is not the same as the rest of our prod build pool so we need it to mirror the same vs2010 version as everything else but as well have vs2013 installed on it. The plan here is to use this testing machine to play around and munge the PATH while hopefully correcting this error by using the correct vs2010's CVTRES.EXE  https://bugzilla.mozilla.org/show_bug.cgi?id=1026870#c10  http://msdn.microsoft.com/en-us/library/7dz62kfh(v=vs.100).aspx
q - would you be able to help me with this or pass me off to someone who can? thanks! :)
I can re-image the machine to mirror production then install 2013. Does that work for you ? Is there anything you need off that box first? Q
(In reply to Q from comment #2) > I can re-image the machine to mirror production then install 2013. Does that > work for you ? Is there anything you need off that box first? > > Q I don't need anything from this machine. jhopkins was using it before myself and AFAIK he did not mention anything about it to anyone before he left releng. So yes, re-image away when time permits :) I disabled the slave but kept it locked to me so others don't use it.
This is now in a virgin state with 2010 would you like to copy /loot at anything before I set the gpo to install 2013 ? Q
(In reply to Q from comment #4) > This is now in a virgin state with 2010 would you like to copy /loot at > anything before I set the gpo to install 2013 ? > > Q Thanks for checking Q. I would imagine if I need to dive into 2010 state, I should be able to poke at another clean image with only vs2010 on it. So let's just install 2013 at your earliest convenience. :)
Just got a chance to look in on this machine and it looks like the 2013 gpo took and you are all set.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.