Reminds me of The Website Is Down, episode 4:
https://www.youtube.com/watch?v=v0mwT3DkG4w
“A Windows 7 deployment image was accidently sent to all Windows machines”
91–100 of 149 posts
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#92Funny how they mention iTunes as one of the "key components" that are restored first, whereas Visio, Project, Adobe application are relegated to a second round.
It's possible they're delivering academic materials through iTunes, I suppose.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#93I asked my friend attending Emory right now, and he didn't even realize anything was going on. He says that the Emory IT department has a notorious distinction on campus as being regularly terrible, mostly with an unreliable internet connection. However, it looks like they handled this accident the best they could! Perhaps this accident would not have happened at a more reliable IT department.
[deleted]
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#94Earlier quoted context omitted.
@DEVOPS_BORAT is actually very insightful in about 1/5 tweets. Snide for sure, but there are quite a few good points in there if you read carefully: "In devops we have best minds of generation are deal with flaky VPN client." "Single point of failure in private cloud is of usually Unix guy with neckbeard." These are gold. Edit: based on the above advice I once grew out a neckbeard while going through a multi-month ro…
"In devops is turtle all way down but at bottom is perl script."
I thought Perl is what is holding the turtles together?
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#95Earlier quoted context omitted.
The BOFH sabotaged his systems before departing? Didn't build a backup plan? And they hired him back?
You know what? Fuck them. Fuck higher education completely. Undervalued and underpaid is the name of the game for any important IT roles in that shit hole of an industry. Disclaimer: dev at a university.
To be fair, a lot of the people working in support roles in academia are pretty much unemployable in the real world. They show up at 10 am, take constant smoke breaks all day, and leave at 3 pm. When I was in physics (which used the main university servers for most things) we had a sysadmin who was in charge of some printers and a couple of server boxes. He had inherited those boxes from a former student who set them up, but he was functionally illiterate in managing them. At one point I needed a package installed. Not only could he not figure out how to install a package on a ubuntu server on his own, he couldn't do it with emailed instructions either. I had to go up and physically stand over him telling him what to click on and what to type. To make matters worse, he was so hard to actually catch "in the office", that I had to have the department secretary (whose office he was next to) alert me when he showed up. Not surprisingly, the functions of those servers were soon moved to desktop machines in various offices. As far as I know he's still working there though. He's a union employee and it would be a ride through deepest, hottest, hell to get rid of him.
Note: I am not saying all university support staff are like this. Some definitely are though, and they're probably the reason why good people sometimes find it hard to be properly remunerated in academia.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#96 > As soon as the accident was discovered, the SCCM server was powered off – however, by that time, the SCCM server itself had been repartitioned and reformatted.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#97You know how in movies you need at least two people to bring their special secret keys, plug them in, and turn them at once to enable a self-destruct sequence? That is a real principle in interface design - if something would be really, really bad to activate unintentionally, make it really, really hard to activate. If you design a nuclear missile facility, you don't put the "launch nukes" button right next to "check…
In my experience, the key is that the UI makes it clear exactly what you're doing. What I mean is, instead of a button that says "Start Imaging", it should be "Start Imaging of the 12,600 computers this rule applies to". Of course, that's a lot more work for the programmer, so it's never done.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#98"As soon as the accident was discovered, the SCCM server was powered off – however, by that time, the SCCM server itself had been repartitioned and reformatted."
Unicast fail.
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#99You know how in movies you need at least two people to bring their special secret keys, plug them in, and turn them at once to enable a self-destruct sequence? That is a real principle in interface design - if something would be really, really bad to activate unintentionally, make it really, really hard to activate. If you design a nuclear missile facility, you don't put the "launch nukes" button right next to "check…
In my experience, the key is that the UI makes it clear exactly what you're doing. What I mean is, instead of a button that says "Start Imaging", it should be "Start Imaging of the 12,600 computers this rule applies to". Of course, that's a lot more work for the programmer, so it's never done.
But then that leads to people automatically clicking "Yes" to the "Are you sure..." dialog. Though even I would pause at "Are you sure you want to reformat 12,500 machines including this one?" ;-)
Re: “A Windows 7 deployment image was accidently sent to all Windows machines”
#100Funny how they mention iTunes as one of the "key components" that are restored first, whereas Visio, Project, Adobe application are relegated to a second round.
Not hard to imagine. The others likely have specialty licenses and so aren't as easily distributed to everyone. In addition, Adobe software itself wasn't working earlier ;-)