no one could make changes to the network infrastructure, but there is no evidence that the network went down, or was impacted at all.
There's more to this story than a rogue admin. He may have been misguided and overstepped his authority, but he was trying to keep his network running and away from incompetent idiots and managers (is tat redundant?). In that area he was apparently right, I have not read of any unauthorized access of data, or denial of service from his keeping the only password to himself.
Sounds like an admin / geek doing his job too well and not wanting enyone else to screw it up. A little communcication from and to management should have prevented this.
-another NetAdmin.
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
The real problem here...
... is all the ignorant "managers" who think that the network admin is just a technician who plugs things in and they work right out of the box. Once you've had to work your way out of a couple of nightmares and begun to comprehend the scope of what can go wrong and the knowledge/skills required to fix it, it's hardly surprising that we get situations like Mr. Childs. The guy was terrified that some oaf would be appointed who would break the whole infrastructure... and he'd have to do it all over again... and again... and again. Most "executives" prefer to believe that this is "easy stuff" and never want to pay for the job at hand...usually the same people whose company laptops are polluted with PPP software, illegal copyrighted material and spyware. They just don't get it!
Post new comment