Pi1otguy
Pattern Altitude
At work were rolling out a specialized set of new computers that are somewhat time consuming to image and configure versus our run of the mill comp. So far we've had a few minor issues that come with anything new and comp related, but never anything without a work around that made it unusable.
Until 2 days ago.
Somehow a user managed to use his admin rights go into the registry (against company policy directly to touch the registry) and mess with a few drivers to not only disable all nics, but also prevented them from displaying or being easily configurable among other problems.
How do I know the user did this you ask? He told us with glee and a tone of accomplishment commenting that it took someone with his abilities to break it when no one else had this happen yet. Commenting that he's the (unofficial) tech guy for his group after breaking what hasn't broke for anyone else in testing, the pilot roll out or the current rollout! IDK why, but this is most frustrating "user error" I've seen.
Oh, wait I know why I'm ****ed. Cause we had pick up another comp, update our asset inventory, image it, install progs, adjust settings, copy user data from the defunt comp, and restore user prefs over a low bandwidth connection in the field. Basically throwing a wrench into our other planned activities at that site.
But this time he'll have no local admin rights unlike everyone else in his dept. Turns out the companies upper level IT guys were in the room when he proudly boasted about his skills in breaking stuff.
\ rant off
Any of u tech guys have this happen?
Until 2 days ago.
Somehow a user managed to use his admin rights go into the registry (against company policy directly to touch the registry) and mess with a few drivers to not only disable all nics, but also prevented them from displaying or being easily configurable among other problems.
How do I know the user did this you ask? He told us with glee and a tone of accomplishment commenting that it took someone with his abilities to break it when no one else had this happen yet. Commenting that he's the (unofficial) tech guy for his group after breaking what hasn't broke for anyone else in testing, the pilot roll out or the current rollout! IDK why, but this is most frustrating "user error" I've seen.
Oh, wait I know why I'm ****ed. Cause we had pick up another comp, update our asset inventory, image it, install progs, adjust settings, copy user data from the defunt comp, and restore user prefs over a low bandwidth connection in the field. Basically throwing a wrench into our other planned activities at that site.
But this time he'll have no local admin rights unlike everyone else in his dept. Turns out the companies upper level IT guys were in the room when he proudly boasted about his skills in breaking stuff.
\ rant off
Any of u tech guys have this happen?