Live data from Hacker News

“A Windows 7 deployment image was accidently sent to all Windows machines”

it.emory.edu

141–149 of 149 posts

Re: “A Windows 7 deployment image was accidently sent to all Windows machines”

#141

Isn't this more the fault of the system architect than the guy who accidentally fired the bad deploys? It's similar to a database firehose: If you accidentally start deleting all data you should have a quick working backup ready to quickly bring the dead box up to production.

I don't know. This could very well be a case of not much more than a bad drag and drop in SCCM. Its not quite that simple, but I'm not sure this is some custom process they setup.

Any tool that allows you to easily perform the antithesis of its function without making it abundantly clear what clicking the OK button will do is fundamentally broken.

Re: “A Windows 7 deployment image was accidently sent to all Windows machines”

#142
post #137

Earlier quoted context omitted.

Professionally I deal with much of the fallout from problems such as yours, and leading techs doing this kind of work. It really sucks, but for many problems like this the choice becomes spend-four-hours-reimaging-the-machine or spend-unknown-period-of-time-trying-to-fix-new-problem. The latter would be great if it was less than four hours, but it's often not, and until that time you / the user are without a machine.…

>spend-four-hours-reimaging-the-machine or spend-unknown-period-of-time-trying-to-fix-new-problem Definitely. In our case its 8 hours minimum though for a re-image. Somehow the FDE makes pulling the old data off the machine slow. You've got my sympathies though - I'd not like to be the one doing the IT in these cases. Can't be fun troubleshooting IT with that kind of time pressure.

Thank you. It really, honestly is hard on our tech because they feel the pressure from all sides. Eight hours sounds rough for a reimage. I think ours are... maybe two or three? We've done a lot of work to get the reimage time down, and Win7 (WIMs) have made this really nice.

If this is something that smells of a bigger problem (or has been seen elsewhere) then I push for them to get the user a wholly new machine, capturing the old one for analysis. If the user is given an upgraded machine, then there is usually little resistance, even with the downtime that'll be incurred.

On the upside, if the issue can be reproduced readily, from this we can almost always get root cause and put a systemic fix in place. If it's sporadic... Well... I'm sure you understand how it goes trying to fix something that you can't yet reproduce. ;)

(I'd love to troubleshoot your slow data backup issue... That's the stuff I rather enjoy.)

Re: “A Windows 7 deployment image was accidently sent to all Windows machines”

#143
post #129

Earlier quoted context omitted.

http://en.wikipedia.org/wiki/Turtles_all_the_way_down

Count is correct, but I did have a flash to my childhood: http://en.wikipedia.org/wiki/Logo_(programming_language)

That was my first thought too but I figured they couldn't be referring to that. :)

Re: “A Windows 7 deployment image was accidently sent to all Windows machines”

#145
post #137

Earlier quoted context omitted.

>spend-four-hours-reimaging-the-machine or spend-unknown-period-of-time-trying-to-fix-new-problem Definitely. In our case its 8 hours minimum though for a re-image. Somehow the FDE makes pulling the old data off the machine slow. You've got my sympathies though - I'd not like to be the one doing the IT in these cases. Can't be fun troubleshooting IT with that kind of time pressure.

Thank you. It really, honestly is hard on our tech because they feel the pressure from all sides. Eight hours sounds rough for a reimage. I think ours are... maybe two or three? We've done a lot of work to get the reimage time down, and Win7 (WIMs) have made this really nice. If this is something that smells of a bigger problem (or has been seen elsewhere) then I push for them to get the user a wholly new machine, ca…

>I'd love to troubleshoot your slow data backup issue... That's the stuff I rather enjoy.

I'm not directly involved with the tech side so I don't know the details. I gather they pull the old data off the disk using some offline low-level tool though (like you would for harddrive damage recovery). Between that and the encryption its somehow very slow. No idea why its like that though.

>get the user a wholly new machine

I wish it was the same here. They just give loan machines :/

Re: “A Windows 7 deployment image was accidently sent to all Windows machines”

#147
post #5

Snark and sarcasm aside, I am impressed with the level of detail that the IT department is sharing; it is refreshing to see such a disaster being discussed so openly and honestly, while at the same time treating customers like adults.

Snark and sarcasm somewhat aside, it's not like they could tell the users about the remediation progress through their intranet, so they probably didn't have many options besides posting it on the Internet for all to see.

Re: “A Windows 7 deployment image was accidently sent to all Windows machines”

#148
post #146

Earlier quoted context omitted.

maybe I was joking too!

I've found that jokes tend to get downvoted on HN. Your post seems to be still in the black.

No sense of humor is bad for you. But on HN it is normal.

Re: “A Windows 7 deployment image was accidently sent to all Windows machines”

#149

Earlier quoted context omitted.

Is it that surprising? I'd bet the average devops is in the top quartile, if not the top 10%.

Is that a statistics joke?

I guess it depends on where your line for 'best minds of the generation' lies. If it's the top 25%, I wouldn't be surprised that many software devs / devops people lie in that category.
Post reply on HN