Reminds me of something that happened about 25 years ago when an elementary school visited our data center of the insurance company where I worked. One of our operators strategically positioned himself between the kids and the mainframe, leaned back and hit it’s EPO button.
Or when your building engineering team cuts themselves a new key for the ‘main breaker’ for the facility… and tests it at 2pm on a tuesday.
Or when that same team cuts a second key (gotta have 2 keys!) and tests that key on the same ‘main breaker’ … at 2pm on the following tuesday.
not fakenews, a real story from a large building full of gov’t employees and computers and all manner of ‘critical infrastructure’ for the agency occupying said building.
In the early 2000s a friend of mine worked for a company in NYC that provided stock feeds to large banks and brokerages and similar. They’d ship a (locked) cabinet full of stuff to their customers, complete with an Ethernet cable stickin’ out the back. Customer would plug this into their network and, um, do whatever it is stock people do. There was some horrendously expensive SLA attached, and so they outsourced support to one of the managed services companies so that they could provide 24x7x2hour response all over the country.
One day, one of their largest customers, a large bank, also in NYC is down. This means that the brokerage arm is unable to do any trades, and so is, um, annoyed. Support rushes over to the customer and “fix it”. My friend doesn’t really get a good explanation of how it got fixed, but, meh, it’s working, so all good. A few weeks later, same thing - customer devices disappear from monitoring, smart-hands/support rush over and fix it, no useful RFO. This happens a few more times, and everyone is getting increasingly annoyed.
Eventually my friend arranges it so that he gets paged at the same time as the support provider. Pager goes off, friend jumps in a cab to the customer. He arrives at the same time as the smart-hands person, who, oddly, is clutching 1: an Ethernet face-plate and 2: a punch-down tool. Somewhat mystified, my friend follows the support person to where the cabinet is located. Because it’s important and special, but not actually bank owned, it cannot live in their data-center… and so it is located in the corridor, just outside the server room.
Because of where the Ethernet cable comes out the back of the cabinet, and where the wall jack is, there is basically no slack. When someone goes in or out, especially if they are wheeling a cart or carrying a box of equipment, they bang into the cabinet, which slowly rolls away – ripping the wall jack off the wall, and the cable out the back of the jack. Support’s “solution” to this has been to punch down the cable onto a new wall jack, screw it back onto the wall, wheel the cabinet back into place, and call it fixed.
My friend screwed down the cabinet feet, so it wasn’t resting on the wheels any more, replaced the 6ft Ethernet with a 15ft, and the issue never recurred 
W
