But, will the WSJ reveal how this news was broken to FR's resident Microsoft lackies and bootlicks?
Posted on 10/04/2005 5:33:08 AM PDT by Halfmanhalfamazing
Windows was broken and Microsoft has admitted it. In an unprecedented attempt to explain its Longhorn problems and how it abandoned its traditional way of working, the normally secretive software giant has given unparalleled access to The Wall Street Journal, even revealing how Vice President Jim Allchin, personally broke the bad news to Bill Gates.
(Excerpt) Read more at smartofficenews.com.au ...
and I didn't compare it to one either....
I said it could be seen as an enterprise and it is.
Myyoursoft is in for a rude awakening if they are as arrogant as Golden Dodo is
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. ; )
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.
Jeez you're such a loser. Spend all day calling others names instead of cleaning up your own crap network? If you can't even keep Windows stations online, leave *nix to someone who at least halfway knows what they're doing.
Most problems start when site admins start tinkering with a configuration or, worse yet, cook their own. No documentation compliments the mess ensuring the network remains increasingly muddled until the local 'Server God' steps in and restores his ego by bestowing unto the customer their next (limited) period of functionality. In all actuality it's his mess in the first place by not using standard configurations or documentation.
If you're getting BSODs I can assure you it is from improper configuration management. Is it happening at other sites? If it is not happening on the WAN (and it is not) then it's the LAN which = site adminstration.
I suggest reading the BSOD screen(s). The error codes usually identify the cause. If that doesn't work try slaving a BSOD-d HD and reading the Event Viewer's System and Application logs. They should have specific entries related to the BSOD.
If BSODs are occuring on different hardware platforms during bootup I would use the Group Policy Management and Group Policy Inventory tools (downloadable from MS) to check the GPOs applied to the respective OUs and computer accounts. Look to see if there's a permissions policy applied to C:\ which excludes the System account from Full Control. Neglecting Full Control for the System account is the most likely cause imo.
Messed up Local Computer Policy settings are usually from a site's Server God (or apprentice) tinkering with various GPO settings and omitting the System account in the pursuit of 'fixing' or even 'tuning' account permissions. He may even have substituted himself for the System account in various fields -because he's Server God; whereas the computer is merely a machine. Server God frequently reveals himself in the Computer Configuration\Windows Settings\Local Policies\User Rights Assignement\Act as Part of the Operating System setting. Of course he doesn't document his changes or even report them ...because he's Server God. And when the network breaks it's never his faut, it can't be, -he's Server God. It has to be something more powerful, devious and domineering than Server God, it has to be a Darth Admin sneaking into his network in the pursuit of diminishing his lustre while spreading fear and suspicion among the faithful.
Friggin Jackasses.
Btw, I'm not necessarily referring to you Mike so I hope you're not offended. We all have a lot to deal with yet with limited support. I'm referring to whomever messed up your local network and consider themselves too infallible to accept responsibility or fix it. Ergo, it's essentially a management issue and there probably isn't much of a management presence at your site. Personally, I wouldn't stand for it. Unfortnately, messed up LANs usually have deep roots and may be more than one person can fix.
It doesnt have Bill in it.
But, will the WSJ reveal how this news was broken to FR's resident Microsoft lackies and bootlicks?
Don't worry. Longhorn only has a red screen of death.
"Windows was broken and Microsoft has admitted it
Wow, This is like Disneyland admitting that crime occurs in its theme parks.
Sure it does. About 3/4 of the way through.
He doesn't look happy.
Eagle Good!!!
I only wish I had enough rights on this crappy network to fix it. Unfortunately I don't.
Such is life working for the Air Force....
not that you would know and OH BY THE WAY, the UNIX side of our network is 1000s of times more stable than our Windows side.
Sounds like the REAL administrators of your network aren't as dumb as you claim. Yep, guys like me are keeping many of the DoD nets tight.
the UNIX side of our network is 1000s of times more stable than our Windows side.
Ours is equal, but probably only because we keep all the id10ts off the unix side. But if you manage them both properly, both can be highly secure and highly available. Just don't forget your password, or you'll never get in, at least not around here.
LOL
so you are lecturing me about a network you know absolutely NOTHING about?
LOL
your arrogance is amazing. And not surprising considering who you shill for.
I know this much, you first claimed you were an admin, then admitted you don't even have permssions to fix the supposed BSOD's. The rest is pretty simple, LOL.
No I admitted I don't have enough rights to fix all the problems on the crappy network I have to live with.
I FIX BSODs all the time. But I can't change the baseline they put on these machines, I am NOT a government employee (which would be those who actually come up with the baseline load).
You would be familiar with that wouldn't you Golden Roadkill?
And yes I am an admin, at least, I think that MCP would qualify me as one
run along before I have to school you in reading comprehension....
how would you know?
I administer what I can and what I am allowed too.
Apparently YOU don't know what you are talking about either.
Not surprising.
And you ineffective shilling for Microsuck along with Golden Roadkill has made you guys the joke of FR, just FYI....
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.