No, as usual I was exactly right. And here's the thread to prove it.
Here's Mike claiming he's the administrator of his network:
I administer a Windows 2000 and WinXP network and I see BSOD every day.
Yet here he is shortly later, when questioned why he doesn't fix it LMAO:
I only wish I had enough rights on this crappy network to fix it. Unfortunately I don't.
ROFL! His denials of course didn't end there, now he's lying about it, what a loser.
Way to take things out of context, but that's a given coming from you.
Let's start here first:
"I administer a Windows 2000 and WinXP network and I see BSOD every day."
And I still do, although we've been mandated to migrate each and every user to Winblows XP. And now we are moving more and move towards Solaris and thank God for that. Now onto your next stupid comment:
"I only wish I had enough rights on this crappy network to fix it. Unfortunately I don't."
I don't have enough rights on our UNCLASS network. That's not saying I don't have the right "password" you dipshit.
But it's not a surprise since you've never worked in an environment remotely like the one I work within (3 different networks at 3 completely different CLASSIFICATION LEVELS), that you wouldn't have a clue.
Look at it this way clown, two of our networks work just fine (if the Air Scouts can keep the power on), one doesn't. You'd never guess which one my group doesn't have complete control over (hint it's the one that YOU claim to have a major role in building).
GE, you may want to know that well set-up networks give very few of the administrators full rights to everything. As a matter of principle, smart security people keep the number of those with full-boat privileges to an absolute minimum. Other admins will have rights to deal with what they normally deal with.