The day the "organized" intern decided the server room cables looked messy
Posted by Cascade_2Nyx@reddit | talesfromtechsupport | View on Reddit | 57 comments
So we hired this new intern a couple of weeks ago. Let us call him Kyle. Kyle is a nice guy, super eager to please, and apparently possesses a level of confidence in his cable management skills that is bordering on delusional. Most of the time he just handles basic password resets and "my mouse is double clicking" tickets, which he does fine. But yesterday I made the mistake of leaving him alone near the server room while I went to grab a much needed caffeine fix.
I was gone for maybe ten minutes. I was just walking back to my desk when my phone started blowing up with Slack notifications. Then the shouting started from the sales floor because their CRM went dark. I ran to the server room and found Kyle standing there with a handful of Cat6 cables and a very proud expression on his face. He looked at me and said hey man I noticed these wires were looking a bit cluttered so I decided to unplug them and reroute them through the side panels so it looks more professional for when the CTO visits next week.
I literally felt my soul leave my body for a second. He had unplugged the main switch that handles the entire east wing of the office without labeling a single thing or checking if there was active traffic. He just saw "messy wires" and decided to fix the aesthetic. It took me and the senior admin two hours to get everything back to normal and verify that we had not fried anything or caused a massive data loop. Kyle spent the rest of the afternoon sitting at his desk looking like a kicked puppy while I explained the concept of "if it is plugged in and working do not touch it".
The best part was when he asked if I still wanted him to finish the cable ties. I told him he is banned from entering any room that contains a blinking light for the next month. I swear some people think IT is just about making things look pretty like a pinterest board instead of actually keeping the business running. At least the CTO did not walk in while Kyle was standing there holding the lifeblood of the company in his sweaty hands.
TL;DR: New intern decided the server room cables looked messy and unplugged the main switch to "reroute" them for better aesthetics. Entire office went down and it took two hours to fix his professional cable management.
Mickenfox@reddit
Keeping things organized is important.
JJJBLKRose@reddit
He was given access to the network closet as an intern without any training or explanation? Sound a bit like a training issue.
Palmovnik@reddit
Yes and no,
if I would trust someone to call them IT and have ServiceDesk job I would think they would know not to touch cables in server room.
JJJBLKRose@reddit
He's an intern. Basically a fresh new hire off the street with no prior experience. If it was someone's first IT job first thing I would do after the 'welcome to the team and here's the office tour' is point out what they should never do, especially without supervision.
GayRacoon69@reddit
You're right but so is the other person
Not messing with cables is common sense
JJJBLKRose@reddit
And assuming things are common sense and not teaching/training is how you end up here.
GayRacoon69@reddit
Like I said, you're right, this should've been taught
That doesn't remove blame from the intern. What he did was dumb. You shouldn't need to be taught every dumb thing to not do. You gotta figure some shit out yourself. It doesn't take a genius to not unplug shit in the server room
LongSufferingSquid@reddit
Interns aren't typically just hired off the street. They're usually people who are interested in a role in the particular industry they're interning in. If Kyle is that oblivious to how computers work then he's probably not cut out for working in IT.
JJJBLKRose@reddit
In the US international are typically college students who are doing it as a credit requirement. I worked on a team that got an intern who was a Computer Science major focusing on development who ended up interning as a junior sysadmin, so not their general discipline.
On top of that, some people just don't have 'common sense' and anyone who's worked for a while has likely learned that you need to teach those things anyway.
mf0723@reddit
Also, 'common sense' turns out to not be so common...
LongSufferingSquid@reddit
... So you had an intern interested in getting into the Computer Science industry interning in the Computer Science industry.
BrocktreeMC@reddit
I’ve had access to our network room and all IDF/MDF closets since I was the lowest tier HelpDesk at my organization. We stored equipment in there that I needed access to sometimes. But even I knew, without anyone having to tell me, that I shouldn’t go fucking with any of the servers or networking unless I was specifically told to.
It seems like a common sense thing, and if that’s not a skill you have, you may not be cut out for IT.
2VesperStatic@reddit
Training matters, but there is also a baseline level of self-preservation and caution most people have around equipment they do not understand. If your instinct in a room full of blinking hardware is to start unplugging things for aesthetics, the problem is not just missing instructions. That is a brutal lack of judgment.
SporesM0ldsandFungus@reddit
That's a fundamental misunderstanding of how networking works. Like 1st semester of an associates degree. Yeah, you can have specific port assignments, VLANs, disabled ports,
Intern must have only handled his Linksys router at home.
CharcoalGreyWolf@reddit
Accompanied with top-level Dunning Kruger.
sqqueen2@reddit
And you certainly knew to label everything
ShookMyHeadAndSmiled@reddit
A janitor has access to those rooms. Most of them are smart enough not to touch things they don't understand. Some of them even understand just fine and still don't touch them.
Cascade_2Nyx@reddit (OP)
Honestly, you're not wrong. Kyle still made a wildly dumb decision, but someone also should've made it crystal clear that "if it's plugged in and blinking, keep your hands off it" was not a suggestion.
GrimmHalcyon@reddit
There's also something to be said about the confidence gap - the most dangerous intern isn't the one who asks too many questions, it's the one who stopped asking because he thinks he's already got it figured out. Kyle clearly decided somewhere along the way that cable management was within his jurisdiction. The real question is what else he's quietly decided is his call to make over the next few weeks.
robsterva@reddit
Is Kyle still there, or are there more stories coming... or both?
Starrion@reddit
Also, the cables aren’t labeled in the server room?
JJJBLKRose@reddit
Common sense would dictate that you label the patch panel at least, but often people don't document anything so it's a mess. If your switches have VLANs and you don't remember which patch ports go to which VLAN you're going to have to trial and error it until everyone is happy.
bonkdonkers@reddit
Sounds a bit like a fake story tbh
djnehi@reddit
My first real job out of college the network closet was also the water heater, water softener, and furnace closet. Needless to say it wasn’t horribly secure. I did eventually manage to relocate it to a dedicated locked room.
WhoSc3w3dDaP00ch@reddit
When I still did IT, I had to explain to the general manager why "moving the servers from their climate-controlled room to the hot, humid basement (with the building boilers and furnace) was a 'bad idea.'"
It was painful...
A_Bungus_Amungus@reddit
Sounds like a fake post made by AI for engagement
CAShark-7@reddit
Back in the mid 1990's I worked for an international, growing company. Instead of scattered dumb terminals and a PC only for the executive secretaries, we were migrating to a WAN with a PC on every desk, using MS suite products. It was quite the shift for everyone, as you can imagine. The owners promoted someone who had a reputation for 'fixing' problems. He was going to come into IT, kick ass, take names, and curb all the unnecessary expenses.
Yeah. That lasted a month. He got educated fast on what it took to support a company our size, and also just how much that costs. We weren't spending the money on coffee and donuts every Friday. To his credit, he advocated for us and got us the people and equipment that were needed.
Cascade_2Nyx@reddit (OP)
There is always someone who thinks IT is overpriced right up until the moment they learn what all that "extra" spending was preventing. Nobody notices the cost of competent support when things are running smoothly, but the second somebody starts cutting corners or letting the wrong person touch critical systems, the bill shows up fast and usually with interest.
Ranger7381@reddit
Everything is going fine: “what are we paying these guys for?”
Something goes wrong: “WHAT ARE WE PAYING THESE GUYS FOR?!???”
CAShark-7@reddit
Oh! So, so true!
dalgeek@reddit
I had a network tech do this to a PBX rack. He incorrectly assumed that digital PBX phones worked like IP phones, tore down the entire rack and repatched it in sequential order instead of where they were patched before. Took out 300+ phones and it took about 18 hours to tone out all the ports and get the phones back to where they should be.
neekogo@reddit
How much longer after that incident was he employed?
dalgeek@reddit
Not long, that was one of the final straws that pushed him out the door. He had previously caused a network outage by upgrading stacked switches incorrectly and taking down 75% of the network across multiple locations.
randomwanderingsd@reddit
I used to work with a guy who was hired to do night backups. Then one day he shows up for the day shift, without warning or talking to anyone. He then did his normal backup routine, which temporarily halted production systems. This is why there is a night shift. When asked why he did that his reply was “I had a kid. My girlfriend wants me on day shift now.” He changed shift without asking. Fired immediately.
kai58@reddit
If the cables are that important they should not be that easy to unplug, especially for an intern.
Why was he even allowed in that room?
malleysc@reddit
Yeah I had that happen with a storage engineer on an office build out on move weekend. I thought I was done knowing I still had to go back and Velcro everything and started getting calls about things not working. He unplugged everything, neatly routed the cables and plugged everything back in whereever it looked the neatest .
TulipFarmer27@reddit
Now you get to assign him the task of standardized labeling all the server room cables (you do have a standard, right?) without unplugging anything.
deltaz0912@reddit
I object to the idea of unlabeled spaghetti cable runs. It suggests a generally lackadaisical attitude among the system admins. I sympathize with Kyle. He’s still a knucklehead, but I get it.
RedsVikingsFan@reddit
“I’ll take ‘April Fools Day stories that never happened’ for $200, Ken”
Cascade_2Nyx@reddit (OP)
Trust me, if I were inventing a story for fun, I would've picked something less annoying than explaining to an intern why live network cables are not decorative.
poopsididitagen@reddit
Are you going to start labeling cables now?
JoDrRe@reddit
Maybe something with a box of keyboards…
bschott007@reddit
I'd normally agree but no joking here, a junior Network guy at a previous company I worked for did this exact thing but he at least had the brains to tape and label the wires before unplugging them. Still the senior guy told him you never do this during production times, always know what wires are connected to what devices and if losing network/internet access will affect the devices/software running on said devices.
In our case, he was doing one wire at a time so it wasn't a massive issue, just annoying. Caught it while he was just messing with the ethernet jacks for the offices and cubicals and hadn't gotten to the server switches yet.
Just_Maintenance@reddit
OP is probably a bot btw. 1w old account, single other post taken down for being AI.
poopsididitagen@reddit
Plus those cables should have been labeled in the first place
namur17056@reddit
Yeah this is on you
lucky_ducker@reddit
I was an noob in year 2000 when I got a job in I.T. infrastructure (my background was in database applications design). To my horror I discovered that their core network stack was one 10/100 switch, and three downstream 10/100 hubs. And there was zero rhyme or reason as to what was plugged in where.
I got approval to replace the entire stack with gigabit switches, and told my boss that the best thing would be to just take the network down for a couple of hours while I installed the new switches, and made intelligent (and documented) connections to them.
As I was installing the last of the switches, and with the floor piled several inches deep with disconnected patch cables, my boss's boss poked his head in the server room and watched for a minute. "You DO know what you're doing, right?"
He had not yet learned, not to give me openings like that. "Well, actually, I've never really done anything like this before."
His face went white as a sheet.
"But yes, I DO know what I'm doing."
PineScentedSewerRat@reddit
HA!
AdreKiseque@reddit
This feels AI-generated
Toto_nemisis@reddit
I sent this to my coworker Kyle who is not an intern, but more of a worker to help do big projects for little pay!
We laughed, he cried.
Dom_Shady@reddit
Chef's kiss for eloquently putting it like that!
OcotilloWells@reddit
There are several subreddits that would disagree. Someone posts a moderately disorganized patch panel, and all the comments agree that it's terrible.
Don't get me wrong, some of them show closets with a thousand cables all tangled together, those should get fixed.
Commandblock6417@reddit
I've been left unsupervised near messy network cabinets with an insurmountable urge to cable manage them since I was 12 years old and even I knew better than not to touch anything that's working, let alone without labelling it first. I hope this is an april fools' joke because Kyle does NOT pass the common sense check.
Friendly_Guy3@reddit
He did clearly wrong . But it raises some questions. Why are the cables not labeled? How its documented where which connection goes?
Savafan1@reddit
Sound like you should be fired for allowing an unsupervised intern access to the server room.
bschott007@reddit
This is definately a security issue. No one but authorized network people should have door access to the server room and anyone without authorized door access should be accompanied at all times inside that room.
LyricNimbus@reddit
The confidence level required to walk into a server room, see live cables, and start rerouting things for aesthetics needs to be studied. That is not intern behavior, that is a fully loaded disaster instinct.