WinXP, domain logon issues at work

Copied from my original thread entitled "fuck you microsoft": http://www.tribalwar.com/forums/showthread.php?threadid=2 33975

I'm not really providing much information but I don't think it's really necessary. If you have a suggestion, any at all, feel free to post it:

I'm a bandwagoner, ono! Okay, seriously... here's my bitch:

I work at a school providing tech support. There's a lab that has about 20 Dell PCs on it. Today, I went around to those 20 PCs, went to the Windows Update site and tagged all the critical updates to download and that's it, nothing more.

Prior to this, everything was working fine. These PCs logged onto our domain and were working properly with the policies in place.

Afterwards, they're now all borked. It hangs for about 5-10 minutes at the "Applying personal settings" screen or sometimes at the "Loading personal settings" dialog.

What...the....fuck. And it's a supposed known issue: http://support.microsoft.com/defaul...kb;en-us;329457 but I can't get the patch without contacting MS. I'll look into that tomorrow... grrrrrrr

Thanks a fucking lot MS....god, if you're going to release a fucking critical update, why don't you make sure it works completely.

Sigh. I blame myself for not having tested it on one system first.

Flame on.

I have nothing.

Do you use roaming profiles?

don't think so

So you're logging in as Administrator then?

Nah, I login as "student" with a blank password, which is what it's supposed to be.

The last three patches cause known issues logging into a mixed mode domain as well as a 2000/2003 Native mode domain.

You have to apply the patches in specific order to get it to not do this. The main problem is with the last patch they released for the RPC/blaster bug.

It writes over a file that is newer than itself due to them not paying attention to versioning. This causes a problem with the security id and secpol/grouppol.

The only way to fix it is get the patch from MS that unfucks the file and resets the version info.

You have no other way to fix it, except re-image the machines and apply the patches one by one, and reboot after each one.

great.... okay, i'll give the MS thing a shot tomorrow.

thanks candy! :heart:

Candy is god. Second only, perhaps, to Ascain.

/me bows down.