No surprises
I'm always puzzled that people are surprised by the things end users do, mostly due to a lack of understanding.
For example many, many years ago when networking was still a novelty to most companies and wide area networks were incredibly slow if they existed at all local file and print servers were the norm. When I first worked in IT it wasn't abnormal for these servers just to be stuck in the corner of an office somewhere. So one thing I got used to seeing was a plug labelled something like "SERVER - DO NOT UNPLUG".
One of my first calls in a new job was from a site complaining that none of the staff in the office could access their files. I tried to access the server over the staggeringly fast WAN connection (64K IIRC) but there was no response. I could see other devices so it looked like a dead server. Since the site concerned was just the other side of the dual carriageway from the office I risked life and limb to walk over there. On arrival I located the back room that housed the server. Sure enough I could see the problem a soon as I entered that office. There were only three desks and some filing cabinets in the office. Two desks were occupied the third, against the back wall, was home to a bulky yellowing laser printer (this was in the days when smoking in offices was still the norm) and under the desk sat a chunky Novell Netware server. A chunky Novell Network without the usual LEDs on the front panel. Next to the printer was a double power socket - both sockets were occupied. One plug was labelled "PRINTER - DO NOT UNPLUG", the other plug was unlabelled and lead to a kettle on top of the adjacent filing cabinet. On top of the desk lay a power cable which led below the desk, on inspection the plug of this cable read "SERVER - DO NOT UNPLUG".
I asked the occupants of the desks if either of them had unplugged the cable to plug in the kettle. No, came the answer, but that kettle is usually in the kitchen. It was there when we came back from lunch. I plugged the server back in and went off to find out who was responsible for the kettle while the server was going through it's file system checks and long boot procedure. It wasn't hard to find the owner of the kettle. There was a door labelled kitchen so I entered. In there was a man with a central heating boiler in pieces. As soon as I entered he said "sorry you can't come in here while I'm working on the boiler" I apologised but asked if he'd moved the kettle. He answered no, that was the receptionist. So on to reception area where I found the woman who had called me in the first place. Had she, I asked, unplugged the server in order to plug in the kettle? Of course she had. When the engineer had arrived to work on the boiler he'd told her nobody would be allowed in the kitchen for an hour, so she'd taken in upon herself to move the kettle in case anybody needed a brew. And rather than just whipping the kettle out of the room she'd also taken it upon herself to find a location and a plug socket for it. When I asked why she had chosen to unplug the server rather than anything else in the building or maybe find a vacant socket he only answer was to say that she couldn't unplug the printer as somebody might need it. When I explained that the printer wouldn't work without the server she was surprised. Fair enough I thought, maybe she doesn't know the printer is connected to the server. But then I asked if people had started complaining about their files not being accessible straight after she unplugged the server I saw a lightbulb come on behind her eyes.
That was an early lesson to me in the fact that end users don't necessarily understand what IT staff understand.
When I got back to the office my boss was kicking off about the receptionist being an idiot. So I asked who's idea it was to put the server in an open office when it would have been better to tuck it away somewhere. Followed by why the power socket had been in such an accessible position. And why there was no UPS. And whether many other sites had the same setup. And probably a few other questions along those lines.
People in IT have a history of overestimating end users' understanding of technology/