Two hours to boot up

[Guest Sam]

Windows 2003 R2 domain controller is taking more than 2 hours to boot up. How

should I troubleshoot?

This was originally a W2K domain. I setup this 2003 server in same domain as

DC & DNS, then GC. Moved 5 FSMO rules (KB 324801).

Demote the old W2K server and removed it from network.

Before transferring GC & FSMO, new 2003 server was booting up fine.

[Guest Lanwench [MVP - Exchange]]

Re: Two hours to boot up

 

Sam <Sam@discussions.microsoft.com> wrote:

> Windows 2003 R2 domain controller is taking more than 2 hours to boot

> up.

 

Ouch.

> How should I troubleshoot?

> This was originally a W2K domain. I setup this 2003 server in same

> domain as DC & DNS, then GC.

 

Did you run adprep / forestprep / domainprep before promoting this server to

a DC in your W2k domain?

> Moved 5 FSMO rules (KB 324801).

> Demote the old W2K server and removed it from network

 

Did you confirm you had no replication problems or errors beforehand? Did

you test by shutting off the W2k box and seeing whether everything was

running smoothly (before demoting/removing it) ?

> Before transferring GC & FSMO, new 2003 server was booting up fine.

 

Event logs would be a good place to start. Also, mention whether this

happens while you've got a live Ethernet connection at the time.

[Guest Sam]

Re: Two hours to boot up

 

 

 

"Lanwench [MVP - Exchange]" wrote:

> Sam <Sam@discussions.microsoft.com> wrote:

> > Windows 2003 R2 domain controller is taking more than 2 hours to boot

> > up.

>

> Ouch. :(

>

> > How should I troubleshoot?

> > This was originally a W2K domain. I setup this 2003 server in same

> > domain as DC & DNS, then GC.

>

> Did you run adprep / forestprep / domainprep before promoting this server to

> a DC in your W2k domain? Yes, I ran these and for R2 as well.

>

> > Moved 5 FSMO rules (KB 324801).

> > Demote the old W2K server and removed it from network

>

> Did you confirm you had no replication problems or errors beforehand? Did

> you test by shutting off the W2k box and seeing whether everything was

> running smoothly (before demoting/removing it) ? Yes I did.

>

> > Before transferring GC & FSMO, new 2003 server was booting up fine.

>

> Event logs would be a good place to start. Also, mention whether this

> happens while you've got a live Ethernet connection at the time.

 

I am waiting for it to boot up to review event logs

>

>

>

[Guest Sam]

RE: Two hours to boot up

 

Uninstalling APC Power Chute V 6 (in safe mode) resolved the issue.

 

"Sam" wrote:

> Windows 2003 R2 domain controller is taking more than 2 hours to boot up. How

> should I troubleshoot?

> This was originally a W2K domain. I setup this 2003 server in same domain as

> DC & DNS, then GC. Moved 5 FSMO rules (KB 324801).

> Demote the old W2K server and removed it from network.

> Before transferring GC & FSMO, new 2003 server was booting up fine.

>

[Guest Lanwench [MVP - Exchange]]

Re: Two hours to boot up

 

Sam <Sam@discussions.microsoft.com> wrote:

> Uninstalling APC Power Chute V 6 (in safe mode) resolved the issue.

 

Glad you found it. My heavens, that is stale. You should be running 7.0.5 on

your servers. There was a major Java-related problem with an older version

of PowerChute and it was making servers hang.... back in 2005, I think.....

 

 

 

>

> "Sam" wrote:

>

>> Windows 2003 R2 domain controller is taking more than 2 hours to

>> boot up. How should I troubleshoot?

>> This was originally a W2K domain. I setup this 2003 server in same

>> domain as DC & DNS, then GC. Moved 5 FSMO rules (KB 324801).

>> Demote the old W2K server and removed it from network.

>> Before transferring GC & FSMO, new 2003 server was booting up fine.