Yup. Most of the time, policies are in place because someone tried what you’re trying and it let them do that thing… And because Windows let that thing happen, something bad happened for everyone.
So now nobody can do that thing.
The prosumer tech bro that’s never touched enterprise equipment or dealt with operational requirements are the worst.
I couldn’t tell you how many times I’ve heard that something works fine at their home but doesn’t work while they’re at work. Sometimes that’s intentional, sometimes that’s because the network in the office is about 80,000x more complex than the Linksys you plugged in at home, set a password on once that you immediately forgot, and has been doing little more than source Nat and L2 bridging every since, with no regard to what the traffic is, just sending it out regardless, and creating a goddamned mess in the process, but because it’s only you and your spouse and maybe a kid or two, that doesn’t really matter.
Suddenly when you’re dealing with hundreds of endpoints on a LAN, you don’t want every broadcast packet being sent out over the dozens of access points you have dotted around, so no, your multicast discovery won’t work Brenda. So you can’t use Chromecast in the office, okay? I don’t care how important you think it is, it would take hours to get this to work properly and I have more pressing concerns at the moment.
I used to work a little bit of IT-support for my city and this made me have flashbacks.
Another stereotype besides the techbro is the graphic designer gal.
Regards we once drove through the city to plug her scanner in… after we prodigiously made her make sure all the wires are connected.
Not exactly the same level of issue but it’s just something I’ll never forget. And nowadays it would be a completely understandable mistake to make, as USB’s can actually power things. But not in 2006, lol.
Oh heck. I can’t recall the number of times someone, even myself, has driven significant distances just to plug things in because users are to much of window lickers to understand what a USB cable looks like half the time.
One of the funniest that I still regularly encounter is people who power cycle their monitor to reboot their computer. Not realizing that the monitor isn’t the computer itself…
I mean, the list goes on and on and on for this kind of stupid shit. The kicker is that if you even fucking try to make them slightly less goddamned stupid about this shit, they don’t want to hear it.
You’ll be taking at them and you might as well be taking to the fucking wall for all the good it will do.
I had to explain to someone today that, though you can print through someone’s PC to their USB printer, you cannot run the scanner software and connect the same way. So scanning no worky from another computer.
We have print servers, but we don’t have scan servers. Why is that?
Anyway, I don’t think they believed me.
The fun part is that the printer has Ethernet, and if they plugged that in, both systems would be able to print and scan… What a crazy idea!
But the bossman didn’t think it was going to be possible to plug in the printer to the network without wifi… Idk, I’m not there, I don’t know what color the walls in your office are, nevermind being able to coach you on how to plug in a device I’ve never seen to a network I equally haven’t seen.
Maybe people should ask their IT people if it’s a good idea to buy a printer when they have these kinds of operational requirements…
“Hey Windows won’t let me…”
No, it’s actually me who doesn’t let anyone on the network do that. For a reason.
Yup. Most of the time, policies are in place because someone tried what you’re trying and it let them do that thing… And because Windows let that thing happen, something bad happened for everyone.
So now nobody can do that thing.
The prosumer tech bro that’s never touched enterprise equipment or dealt with operational requirements are the worst.
I couldn’t tell you how many times I’ve heard that something works fine at their home but doesn’t work while they’re at work. Sometimes that’s intentional, sometimes that’s because the network in the office is about 80,000x more complex than the Linksys you plugged in at home, set a password on once that you immediately forgot, and has been doing little more than source Nat and L2 bridging every since, with no regard to what the traffic is, just sending it out regardless, and creating a goddamned mess in the process, but because it’s only you and your spouse and maybe a kid or two, that doesn’t really matter.
Suddenly when you’re dealing with hundreds of endpoints on a LAN, you don’t want every broadcast packet being sent out over the dozens of access points you have dotted around, so no, your multicast discovery won’t work Brenda. So you can’t use Chromecast in the office, okay? I don’t care how important you think it is, it would take hours to get this to work properly and I have more pressing concerns at the moment.
I used to work a little bit of IT-support for my city and this made me have flashbacks.
Another stereotype besides the techbro is the graphic designer gal.
Regards we once drove through the city to plug her scanner in… after we prodigiously made her make sure all the wires are connected.
Not exactly the same level of issue but it’s just something I’ll never forget. And nowadays it would be a completely understandable mistake to make, as USB’s can actually power things. But not in 2006, lol.
Oh heck. I can’t recall the number of times someone, even myself, has driven significant distances just to plug things in because users are to much of window lickers to understand what a USB cable looks like half the time.
One of the funniest that I still regularly encounter is people who power cycle their monitor to reboot their computer. Not realizing that the monitor isn’t the computer itself…
I mean, the list goes on and on and on for this kind of stupid shit. The kicker is that if you even fucking try to make them slightly less goddamned stupid about this shit, they don’t want to hear it.
You’ll be taking at them and you might as well be taking to the fucking wall for all the good it will do.
And you also have to manage politely telling them how silly they’ve been.
Once got a ticket for “a broken DVD-drive”. Went on over. 'Twas a CD-drive.
“Well what was the issue, why didn’t my DVD-drive work?”
“Well if you look real close, this is actually a CD drive and thus incapable of reading DVDs”
She took it well enough with humour. Some don’t…
I had to explain to someone today that, though you can print through someone’s PC to their USB printer, you cannot run the scanner software and connect the same way. So scanning no worky from another computer.
We have print servers, but we don’t have scan servers. Why is that?
Anyway, I don’t think they believed me.
The fun part is that the printer has Ethernet, and if they plugged that in, both systems would be able to print and scan… What a crazy idea!
But the bossman didn’t think it was going to be possible to plug in the printer to the network without wifi… Idk, I’m not there, I don’t know what color the walls in your office are, nevermind being able to coach you on how to plug in a device I’ve never seen to a network I equally haven’t seen.
Maybe people should ask their IT people if it’s a good idea to buy a printer when they have these kinds of operational requirements…