Hangs at applying computer settings

[Daire]

Hi,

I came into work on saturday to do a bit of a tidy up on thye network cables and such. I moved the domain controller from one side of the room to another and now it wont get past "Applying computer settings"

I can boot to safe mode.
I dont have any APC UPS software.
I do have symantec AV corp 9.0.
Its Server 2003 std sp1, exchange 2003 sp2,

I have disabled all Symantec services, all CA services, I have checked the IP settings on the network cards - Its a DNS server also and set to 127.0.0.1.

I have tried Last know good config.

I tried the Symantec uninstaller (ripper) from safe mode.

I'M STUCK - anyone got any suggestions I can try. The boss wont be happy if he comes in Monday morning and the server is still down.

Thanks

 

[pagy]

Is this your only DC?? If so it may take a while to boot as AD waits for DNS to start and DNS waits for AD to start.

Do not have the DC pointing to 127.0.0.1 as it's preferred DNS, put the actual IP of the server in there, if you only have 1 DC then put it's own IP in there and not 127.0.0.1.

How long have you left it to boot when it's at Applying computer settings??

Paul
MCSE 2003
MCSA 2003
MCITP Enterprise Administrator

If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[Lemon13]

oktober patch day, i would check eventviewer and microsoft updates, and since u moved it, make sure all components are seated correctly

good luck

 

[Daire]

Hi

The DNS was set to its IP address but i read elsewhere to set it top 127.0.0.1.

I've installed SP2 in safe mode hoping that a windows file needed to be updates but still the same.

I've only ever left it about 10 minutes to start up before shutting off and going back into safe mode to try something else. I have read that it can take 20 minutes or more to boot but the server was fine a few days ago.

Its like that now for 15 mins so will leave it another 10 and then gho back to safe mode and check the dates of windows updates.

Thanks

 

[thalligan]

Had this happen to me a couple of years back. I would recommend letting it go as long as it is looking like it is still processing. I had a system that took about 45 minutes (I had another AD controller in place so I decommissioned and rebuilt the faulty one shortly after).

The pressure to do something is a bit overwhelming I know but as long as it is processing leave it be.

Use the time to organize what you will do next. Unless this is all better in which case Yeah.

Just my two cents

 

[Rockstar101]

Part of the reason it's taking so long to boot up is because Server 2003 applies it's GPOs synchronously so you won't get the logon screen until the gpos have all fully applied.

are you logging the server back into the network with the same ID it was logged in with before...

good luck!

 

[Daire]

Hi, thanks guys,

I applied Server sp2 and nothing changed, i disabled as many services as possible in safe made, nothing changed, i wated 30 minutes at the Applying computer settings screen but still nothing.

I finally re-enabled all services and rebooted and went home.

I connected using terminal services back into the LAN to a different server and tried to connect from there to the server in question but couldnt connect.

I can ping it, i can open file shares on it, i can manage it using MMC.

When i view the services in MMC the Microsoft Exchange System Attendant service is in a state of "starting" and has been for 2 hours. The exchange store cant start until this starts.

AD seems to be back up, DNS is working, DHCP is okay, Terminal services is down and exchange is down.

I'm still trying. All suggestions welcome.

Thanks

 

[jdemmi]

Have you tried logging in with a different profile? (user name).

Since you can access it remotely try renaming/deleting the profile your uing to login.

-- Jason
"It's Just Ones and Zeros

 

[cmeagan656]

Are there any relative events in your event (application and system) logs?

As you can manage via MMC try stopping any Exchange services that are started and then setting all Exchange services to manual (NOT disabled). Then reboot. A hard boot would be preferable but if you're working remotely a reboot will do.

When the server comes back up hopefully Terminal Services will come up.

That will leave only Exchange to deal with. You can then try starting the Exchange services one by one in the proper order. If it hangs on the System Attendant then you likely have an Exchange problem. Post that issue in the MS Exchange 2003 forum

http://www.tek-tips.com/threadminder.cfm?pid=955

and see if anyone there can help.

BTW, you do know that from a security standpoint it is not recommended that your Exchange Server be installed on a Domain Controller don't you?

Cheers.

 

[Daire]

Hi
I think the problem was all my own fault.

Last month i was "tidying" up the user accounts and groups and I moved the builtin exchange groups to a different OU.

The server hasnt been rebooted since then.

Apparently the system attendant looks for these groups in the default users folder. Doh!

http://support.microsoft.com/kb/910413

Thanks for all your help guys.

DS