Free Republic
Browse · Search
News/Activism
Topics · Post Article

To: MikeinIraq
"I administer a Windows 2000 and WinXP network and I see BSOD every day."

Umm, since you "administer" the network aren't you therefore accountable for those BSODs? Certainly you've found the cause and implemented a fix by now, you know, being the administrator and all.... Lemme guess someone just must have pushed a nasty, vile GPO, singling-out your base among all the others for those BSODs?

Ever hear of configuration management? The only BSODs I've seen in Iraq have been from local hardware failure or configuration changes by site Administrators -and those have been very rare. You might see BSODs at your base and on your network but you sure-as-H don't see them on my network -even on your base. That's why we restrict admin permissions. ; )

82 posted on 10/05/2005 1:49:16 PM PDT by Justa (Politically Correct is morally wrong.)
[ Post Reply | Private Reply | To 70 | View Replies ]


To: Justa

well let's see here...

I have found that BSODs can happen with cached profiles, crappy builds and just the fact they are Windows.

I don't control the building of the machines here. I wish I did. I end up getting stuck with every error the guys who end up building the machines give us.


83 posted on 10/05/2005 1:54:32 PM PDT by MikefromOhio (FR is funny when the HYSTERIA corps is out in force.....it's vanity day!!!!)
[ Post Reply | Private Reply | To 82 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson