Every single PC on domain hanging on Applying Computer Settings

[mattx]

Every single PC on domain hanging on Applying Computer Settings.

What the hell ? Anyone else having problems after an MS update ?

[6Foot2]

I have to ask the obvious question here: Any changes to AD/GPOs recently?

 

What was the MS update that you applied?

[mattx]

No changes on the servers [ MS updates - only stuff on workstations ] - nothing on AD GPO. All I have done is data migration to SAN but this is just stand alone data, nothing fancy.

[6Foot2]

What were the KB numbers of the MS updates you applied? Maybe someone has some info on one or more of the updates you sent to your workstations?

[cpjitservices]

sounds daft but check your DNS Settings, we had this problem on some of our machines and turns out for some reason DNS couldn't be picked up on those machines, we restarted the switches and everything was fine.

[budgester]

Anything in the Logs ?

 

This usually sounds like a DNS setting, i.e. trying redirect to a server, that has had it's IP address changed or something similar.

 

Log onto a machine locally.

 

The logs will normally give you a clue.

[mattx]

DNS is fine - I have removed the following:

 

KB2423089

KB2284695

KB2466074

KB2289163

KB2467659

KB2436673

KB2440591

KB2416400

KB2296199

KB2449798

KB2443105

 

No difference, I have also re-started both DCs no difference - I'm now getting really pi55ed off. Some PCs will get the logon screen but only after about 10 to 15 mins. Bleeding stupid. Thanks a bunch MS you bunch of to55ers.

Nothing in the logs on both workstations and servers which would point to anything.

[mattx]

This is daft - it has to do with the data migration - one of the shares I moved over is causing PCs to hang when booting ? The relation between the shares and PCs are nothing until they actually logon - I am now going to have to find out what share it is and why it's happening.

[gshaw]

There's not a startup script in your GPO somewhere pointing to one of those shares by any chance is there? Could be trying to contact the non-existent share and timing out?

[SYNACK]

Wireshark it, that is how I solved a problem like this, just looked for a whole bunch of Windows CIFS requests that kept failing and repeating which showed me where it was trying to get to which gave me an idea of where to look. It was a logon script in my case which caused simmilar 10 minute wait issues on logon.

[mattx]

Right, it's certainly a share - it's one I created about 6 years ago which just gathered info on PCs as they logged on [ not when they booted ] - the app was called AuditWizard....... now thinking about it some more - [ 6 years ago is quite a long time ] - I let it create the share, I just pointed to a location on the server.....Maybe if I un-install it.........

At least I've located the source. Now I have 3 APs not working on our wireless network. This is all I need before Xmas - I've booked tomorrow off as my last days leave - looks like I'll be in now. To say I'm pi55ed off is an understatement.

[Little-Miss]

at least it happened now Matt and now when you've got teachers screaming at you!

[mattx]

at least it happened now Matt and now when you've got teachers screaming at you!

 

You are of course correct - well I know what share it is and I've got it working on the iSCSI SAN - I just copied over 100gig of stuff so that will be it for now. At least PCs around the place are able to logon. I've now changed all the settings on by backups so I don't get duplicate data. To say I was sh1tt1ng bricks this morning was an understatement. Just glad I worked out what it was - at least my PD skills [ problem determination ] still work to a small degree.

Thanks to all who offered assistance btw.

I've got the APs working which decided to take an early xmas break and I am now going to lock up the server room, and bugger off home !!

[Little-Miss]

Yay! You deserve it after today.

 

I hate that "uh oh" feeling you get in the pit of your stomach....

[Bruce123]

We've got various startup and logon scripts, and usually if a share that one of the scripts tries to write/read to isn't available (e.g. in the start-up script), we'd get the the familiar 10 minute wait at start-up. But it would usually get stuck on "Running Start-up Scripts...", which helps us to identify the cause of the problem.

 

On updates causing unexpected problems, we applied loads of updates this week. Some of them was to our Windows 2003 server hosting ISA2006. Immediately following the updates being applied, the server stopped proving Internet access (HTTP proxy). But I wasn't too concerned as it still needed a reboot, but it wouldn't work even following two reboots (and it got stuck for 10 minutes on "applying computer settings..." as described, which I know can often be caused by a DNS issue).

 

Searching through the forums, we tracked down the source of the problem; the post suggested removing the DNS address of the external DNS resolver from both Internal and External network connection settings. This resolved it, but this original configuration was as recommended in an trustworthy consultant's article on isaserver.org. Now our ISA server cannot resolve external names directly with external DNS resolver, instead it has to refer to an internal DNS server which then forwards the request to the external DNS resolver via our ISA server. A bit convoluted, but there you go...

 

Thanks,

 

Bruce.

Edited December 23, 2010 by Bruce123