Quote:
Originally Posted by CRussel
Nope. Mine aren't literate enough to actually read, much less write. Besides, 90% of my 'fix' is to just reboot their [explitive] computer. The other 10% involves removing the CRAP they've installed. (Which is, BTW, NOT ALLOWED on their corporate laptop, thank you. )
|
In my last go around as a corporate IT guy, desktops all got a standard image with approved software. Users all got a power user profile that let them run software but not
install stuff. If they needed something not in the standard image, their manager could send a request, and someone like me could log onto their machine with a domain admin account and install it for them.
Fine for desktops, but company laptops were another matter. There was serious discussion about a setup that would run a mandatory A/V scan every time one got hooked up to the corporate net. We'd had one too many problems with stuff picked up outside and infecting the local net.
I once burned the midnight oil helping to re-mediate an infection that had gotten onto the corporate network. It got in via a security hole that had been patched months previously, but we hadn't been enforcing critical updates, and the machine that was the vector hadn't been patched. The policy of not enforcing critical patches when they were issued got changed.
We later got acquired and merged, and got the budget for a company wide upgrade. Everyone got WinXP and the then current version of Office. I was all in favor. My world included Win98SE, WinNT workstation, Win2K, and WinXP, and I was
delighted to get everyone on XP. (I was especially delighted to get the Win98SE box upgraded. The user needed access to my *nix boxes, but 98SE didn't support the authentication required by Samba to connect. And guess which machine had been the vector for the infection mentioned above?)
I'm patient to a fault, which was a virtue in user support, especially with less than bright remote users. The folks in the office I could just go visit and talk to face-to-face.
______
Dennis