ActiveDirectory promotion causes reboot loop

[Guest Tim_S]

I am installing a Windows 2003 std server on a dell 2950 system. Brand New

from Dell, and I am using their software to load.

 

Everything went fine with the install and the software loaded without

incident. I patched the system fully with MS patches. Everything was great

until I went to configure the server for AD as a member server on a domain

with 2003 std (R1).

 

First thing that happend is this release is R2 and the other releases on the

other two servers are R1 release that is fully patched.

The first thing it errored out was I got a message stating that the Schema

wasn't compatable between the this version R2 and the other R1 and that I

had to run the Adprep tool adprep.exe /forestprep and adprep /domainprep.

 

Ok, i stopped right there, then got the 2003 disk 1 and run the adprep tool

on the schema master PC that had R1 on it. Both Adprep commands failed...

I did some internet searching and found out that the Adprep tool on Disk 1

is bad and that I needed to run the tool from CD #2. Runing that version

on that disk then both commands ran fine on the schema master. Both

/forestprep and /domainprep ran successully.

 

Then I restarted the dcpromo wiz on the R2 system and completed the

inclusion of the new server to active directoy.... I got the screen that it

was successful. Now here is where the issue is...

 

On rebooting the server (new one) now i only get ONE option in the domain

dropdown box and that is the domain, the "local workstation" is not showing

up. ok, I thought, that is strange, then i attempted a domain login using

domain administrator credentials since it is the only option to pick... but

the screen goes something like this...

 

Enter username/password and domain, screen accepts credentials and goes

away...

immediatly i get a "Starting windows" or "loading profile" (can't remember

exactly which)... then instant flash, prompt changes to "Windows shutting

down..". it then reboots and brings me back to the login window.

 

Another stinking "Constant" reboot loop... I have disabled the auto-reboot

feature so I could at least see if it is a BSOD or driver... but it just

reboots..

 

I can log in using ONLY two options after the F8 key... Directory service

restore mode, and Safe mode.... any other options restarts the pc...

 

Addiing to an existing AD domain corrupted the local box somehow because the

local workstaton isn't showing up in the pick box to select local or domain

log-in... any clue as to where to start? I had a similar instance happen

to an XP box where the c:\windows\system32\userinit.exe key was corrupt or

missing from the registry... this registry has it...

 

thanks

[Guest Meinolf Weber]

Re: ActiveDirectory promotion causes reboot loop

 

Hello Tim_S,

 

See inline.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> I am installing a Windows 2003 std server on a dell 2950 system.

> Brand New from Dell, and I am using their software to load.

>

> Everything went fine with the install and the software loaded without

> incident. I patched the system fully with MS patches. Everything was

> great until I went to configure the server for AD as a member server

> on a domain with 2003 std (R1).

>

> First thing that happend is this release is R2 and the other releases

> on the

> other two servers are R1 release that is fully patched.

> The first thing it errored out was I got a message stating that the

> Schema

> wasn't compatable between the this version R2 and the other R1 and

> that I

> had to run the Adprep tool adprep.exe /forestprep and adprep

> /domainprep.

> Ok, i stopped right there, then got the 2003 disk 1 and run the adprep

> tool on the schema master PC that had R1 on it. Both Adprep commands

> failed... I did some internet searching and found out that the Adprep

> tool on Disk 1 is bad and that I needed to run the tool from CD #2.

 

The adprep on disk 1 is for the upgrade to schema version 30, the adprep

on disk 2 is for the upgrade to schema version 31, which you needed because

30 is used with 2003 "normal", btw 13 is windows 2000 and 44 is windows 2008.

You can find out easy with "schupgr" on a command prompt on the schema master.

> Runing that version on that disk then both commands ran fine on the

> schema master. Both /forestprep and /domainprep ran successully.

 

Becasue it was the correct version upgrade.

> Then I restarted the dcpromo wiz on the R2 system and completed the

> inclusion of the new server to active directoy.... I got the screen

> that it was successful. Now here is where the issue is...

>

> On rebooting the server (new one) now i only get ONE option in the

> domain dropdown box and that is the domain, the "local workstation" is

> not showing up. ok, I thought, that is strange, then i attempted a

> domain login using domain administrator credentials since it is the

> only option to pick... but the screen goes something like this...

 

On a domain controller you are not able to logon locally. As soon as the

server is a DC this option is not possible. Only member servers and workstations

have the option.

> Enter username/password and domain, screen accepts credentials and

> goes

> away...

> immediatly i get a "Starting windows" or "loading profile" (can't

> remember

> exactly which)... then instant flash, prompt changes to "Windows

> shutting

> down..". it then reboots and brings me back to the login window.

> Another stinking "Constant" reboot loop... I have disabled the

> auto-reboot feature so I could at least see if it is a BSOD or

> driver... but it just reboots..

>

> I can log in using ONLY two options after the F8 key... Directory

> service restore mode, and Safe mode.... any other options restarts the

> pc...

 

In safe mode check the event viewer for errors or if the server is up, open

the event viewer from the other DC and check. Did you try logon with remote

desktop, does it also reboot?

> Addiing to an existing AD domain corrupted the local box somehow

> because the local workstaton isn't showing up in the pick box to

> select local or domain log-in... any clue as to where to start? I

> had a similar instance happen to an XP box where the

> c:\windows\system32\userinit.exe key was corrupt or missing from the

> registry... this registry has it...

 

Make sure that you run an Antivirus check with up to date software, also

possible if you make it remote from a test workstation not form a production

one.

> thanks

>

[Guest Tim_S]

Re: ActiveDirectory promotion causes reboot loop

 

Thanks Weber,

 

i am adding this as a member server not a master... it should have the local

PC listed... my schema master (PDC) has it's local pc listed as an option

and so does the other member server...

 

This is a new load, i have not loaded any antivirus on it yet. The domain

is secured by Symantec AV Corp 10 and the domain is virus free so i am not

worried about that.

 

Only errors in the log are 1202 DFS replication service failed to contact

domain controller... which could be because i am only able to view the event

log in safe mode.

 

Yes remote control (RDP) reboots the system as well..

 

t

 

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

news:ff16fb6698a38caf9baef5319d0@msnews.microsoft.com...

> Hello Tim_S,

>

> See inline.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and

> confers no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>> I am installing a Windows 2003 std server on a dell 2950 system.

>> Brand New from Dell, and I am using their software to load.

>>

>> Everything went fine with the install and the software loaded without

>> incident. I patched the system fully with MS patches. Everything was

>> great until I went to configure the server for AD as a member server

>> on a domain with 2003 std (R1).

>>

>> First thing that happend is this release is R2 and the other releases

>> on the

>> other two servers are R1 release that is fully patched.

>> The first thing it errored out was I got a message stating that the

>> Schema

>> wasn't compatable between the this version R2 and the other R1 and

>> that I

>> had to run the Adprep tool adprep.exe /forestprep and adprep

>> /domainprep.

>> Ok, i stopped right there, then got the 2003 disk 1 and run the adprep

>> tool on the schema master PC that had R1 on it. Both Adprep commands

>> failed... I did some internet searching and found out that the Adprep

>> tool on Disk 1 is bad and that I needed to run the tool from CD #2.

>

> The adprep on disk 1 is for the upgrade to schema version 30, the adprep

> on disk 2 is for the upgrade to schema version 31, which you needed

> because 30 is used with 2003 "normal", btw 13 is windows 2000 and 44 is

> windows 2008. You can find out easy with "schupgr" on a command prompt on

> the schema master.

>

>> Runing that version on that disk then both commands ran fine on the

>> schema master. Both /forestprep and /domainprep ran successully.

>

> Becasue it was the correct version upgrade.

>

>> Then I restarted the dcpromo wiz on the R2 system and completed the

>> inclusion of the new server to active directoy.... I got the screen

>> that it was successful. Now here is where the issue is...

>>

>> On rebooting the server (new one) now i only get ONE option in the

>> domain dropdown box and that is the domain, the "local workstation" is

>> not showing up. ok, I thought, that is strange, then i attempted a

>> domain login using domain administrator credentials since it is the

>> only option to pick... but the screen goes something like this...

>

> On a domain controller you are not able to logon locally. As soon as the

> server is a DC this option is not possible. Only member servers and

> workstations have the option.

>

>> Enter username/password and domain, screen accepts credentials and

>> goes

>> away...

>> immediatly i get a "Starting windows" or "loading profile" (can't

>> remember

>> exactly which)... then instant flash, prompt changes to "Windows

>> shutting

>> down..". it then reboots and brings me back to the login window.

>> Another stinking "Constant" reboot loop... I have disabled the

>> auto-reboot feature so I could at least see if it is a BSOD or

>> driver... but it just reboots..

>>

>> I can log in using ONLY two options after the F8 key... Directory

>> service restore mode, and Safe mode.... any other options restarts the

>> pc...

>

> In safe mode check the event viewer for errors or if the server is up,

> open the event viewer from the other DC and check. Did you try logon with

> remote desktop, does it also reboot?

>

>> Addiing to an existing AD domain corrupted the local box somehow

>> because the local workstaton isn't showing up in the pick box to

>> select local or domain log-in... any clue as to where to start? I

>> had a similar instance happen to an XP box where the

>> c:\windows\system32\userinit.exe key was corrupt or missing from the

>> registry... this registry has it...

>

> Make sure that you run an Antivirus check with up to date software, also

> possible if you make it remote from a test workstation not form a

> production one.

>

>> thanks

>>

>

>

[Guest Meinolf Weber]

Re: ActiveDirectory promotion causes reboot loop

 

Hello Tim_S,

 

You stated:

"Then I restarted the dcpromo wiz on the R2 system and completed the inclusion

of the new server to active directoy.... I got the screen that it was successful.

Now here is where the issue is..."

 

This is the step where you made this server an additional domain controller.

 

Again see inline.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> Thanks Weber,

>

> i am adding this as a member server not a master... it should have the

> local PC listed... my schema master (PDC) has it's local pc listed as

> an option and so does the other member server...

 

Again. This is not possible on a Domain Controller. On member servers, yes.

> This is a new load, i have not loaded any antivirus on it yet. The

> domain is secured by Symantec AV Corp 10 and the domain is virus free

> so i am not worried about that.

>

> Only errors in the log are 1202 DFS replication service failed to

> contact domain controller... which could be because i am only able to

> view the event log in safe mode.

 

As i said before, you can open the event log from any other computer. Rightclick

MY COMPUTER, choose MANAGE, on Computer Management(Local) rightclick again

and choose "Connect to another computer". From here on you can also see the

EVENT VIEWER of other machines without logging on.

> Yes remote control (RDP) reboots the system as well..

>

> t

>

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

> news:ff16fb6698a38caf9baef5319d0@msnews.microsoft.com...

>

>> Hello Tim_S,

>>

>> See inline.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> I am installing a Windows 2003 std server on a dell 2950 system.

>>> Brand New from Dell, and I am using their software to load.

>>>

>>> Everything went fine with the install and the software loaded

>>> without incident. I patched the system fully with MS patches.

>>> Everything was great until I went to configure the server for AD as

>>> a member server on a domain with 2003 std (R1).

>>>

>>> First thing that happend is this release is R2 and the other

>>> releases

>>> on the

>>> other two servers are R1 release that is fully patched.

>>> The first thing it errored out was I got a message stating that the

>>> Schema

>>> wasn't compatable between the this version R2 and the other R1 and

>>> that I

>>> had to run the Adprep tool adprep.exe /forestprep and adprep

>>> /domainprep.

>>> Ok, i stopped right there, then got the 2003 disk 1 and run the

>>> adprep

>>> tool on the schema master PC that had R1 on it. Both Adprep

>>> commands

>>> failed... I did some internet searching and found out that the

>>> Adprep

>>> tool on Disk 1 is bad and that I needed to run the tool from CD #2.

>> The adprep on disk 1 is for the upgrade to schema version 30, the

>> adprep on disk 2 is for the upgrade to schema version 31, which you

>> needed because 30 is used with 2003 "normal", btw 13 is windows 2000

>> and 44 is windows 2008. You can find out easy with "schupgr" on a

>> command prompt on the schema master.

>>

>>> Runing that version on that disk then both commands ran fine on the

>>> schema master. Both /forestprep and /domainprep ran successully.

>>>

>> Becasue it was the correct version upgrade.

>>

>>> Then I restarted the dcpromo wiz on the R2 system and completed the

>>> inclusion of the new server to active directoy.... I got the screen

>>> that it was successful. Now here is where the issue is...

>>>

>>> On rebooting the server (new one) now i only get ONE option in the

>>> domain dropdown box and that is the domain, the "local workstation"

>>> is not showing up. ok, I thought, that is strange, then i attempted

>>> a domain login using domain administrator credentials since it is

>>> the only option to pick... but the screen goes something like

>>> this...

>>>

>> On a domain controller you are not able to logon locally. As soon as

>> the server is a DC this option is not possible. Only member servers

>> and workstations have the option.

>>

>>> Enter username/password and domain, screen accepts credentials and

>>> goes

>>> away...

>>> immediatly i get a "Starting windows" or "loading profile" (can't

>>> remember

>>> exactly which)... then instant flash, prompt changes to "Windows

>>> shutting

>>> down..". it then reboots and brings me back to the login window.

>>> Another stinking "Constant" reboot loop... I have disabled the

>>> auto-reboot feature so I could at least see if it is a BSOD or

>>> driver... but it just reboots..

>>> I can log in using ONLY two options after the F8 key... Directory

>>> service restore mode, and Safe mode.... any other options restarts

>>> the pc...

>>>

>> In safe mode check the event viewer for errors or if the server is

>> up, open the event viewer from the other DC and check. Did you try

>> logon with remote desktop, does it also reboot?

>>

>>> Addiing to an existing AD domain corrupted the local box somehow

>>> because the local workstaton isn't showing up in the pick box to

>>> select local or domain log-in... any clue as to where to start? I

>>> had a similar instance happen to an XP box where the

>>> c:\windows\system32\userinit.exe key was corrupt or missing from the

>>> registry... this registry has it...

>>>

>> Make sure that you run an Antivirus check with up to date software,

>> also possible if you make it remote from a test workstation not form

>> a production one.

>>

>>> thanks

>>>

[Guest Tim_S]

Re: ActiveDirectory promotion causes reboot loop (solved)

 

Re: ActiveDirectory promotion causes reboot loop (solved)

 

ok, looked through all the logs, nothing showed to be the cause

 

I found out that i can log on using another adminstrator account without the

system rebooting, I thought ok a profile is corrupt... I deleted the

profile for the administrator account, I then rebooted the system, and tried

to log on as Administrator, the system goes, logging on, then shutting down.

I log in using my backup user account with administrator priv. and the log

shows nothing as to why it was failing under the Administrator account.

 

I then experimented a little further.. what was diff between my

administrator accout and my backup account? Then it hit me like a meteor

hitting the planet... the Administrator account is running a batch file as

part of the log-in script. My secondary account was not running a batch file

as part of the login script. When I added the batch file to my secondary

account, the server restarted exhibited the same behavior. Now i have

narrowed it down to the batch file. Upon examining by scripting in this

file, in which i have it doing a number of administrative task for me, I have

it calling a windows update site, and symantec update site so as to make it

easier for me to do monthly updates. Well, I also have programmed it to do

application updates to a medical program when I log in. In the batch routine

i was checking for the existance of a text file (update.txt) and if it was

not found, to execute the install of an application. I forgot to remove the

coding after the updates were done and after i removed the install program.

Well the application was not running the install of the update and was

skipping through the batch file like it should. After the app was supposed to

update, it was supposed to execute a reboot and at the end of that code as i

had a command > shutdown -r -f -t 00 That was the command that was

executing... duh.... The batch file was skipping through not installing the

app and thus doing what i acutally told it to do restart unconditionally...

Yep my own stupidity and scripting error was the problem. The reason it

didn't happen on the other system(s) is the application is installed and the

text file is there to skip the section in the login script of installing the

update.

 

Of course there would be no log file.. and no errors... it just happend so

fast i could not see the batch file kicking in...

 

Thanks for the help...

 

Mystery solved...

Thanks Weber...

 

"Meinolf Weber" wrote:

> Hello Tim_S,

>

> You stated:

> "Then I restarted the dcpromo wiz on the R2 system and completed the inclusion

> of the new server to active directoy.... I got the screen that it was successful.

> Now here is where the issue is..."

>

> This is the step where you made this server an additional domain controller.

>

> Again see inline.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>

> > Thanks Weber,

> >

> > i am adding this as a member server not a master... it should have the

> > local PC listed... my schema master (PDC) has it's local pc listed as

> > an option and so does the other member server...

>

> Again. This is not possible on a Domain Controller. On member servers, yes.

>

> > This is a new load, i have not loaded any antivirus on it yet. The

> > domain is secured by Symantec AV Corp 10 and the domain is virus free

> > so i am not worried about that.

> >

> > Only errors in the log are 1202 DFS replication service failed to

> > contact domain controller... which could be because i am only able to

> > view the event log in safe mode.

>

> As i said before, you can open the event log from any other computer. Rightclick

> MY COMPUTER, choose MANAGE, on Computer Management(Local) rightclick again

> and choose "Connect to another computer". From here on you can also see the

> EVENT VIEWER of other machines without logging on.

>

> > Yes remote control (RDP) reboots the system as well..

> >

> > t

> >

> > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

> > news:ff16fb6698a38caf9baef5319d0@msnews.microsoft.com...

> >

> >> Hello Tim_S,

> >>

> >> See inline.

> >>

> >> Best regards

> >>

> >> Meinolf Weber

> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> confers no rights.

> >> ** Please do NOT email, only reply to Newsgroups

> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>> I am installing a Windows 2003 std server on a dell 2950 system.

> >>> Brand New from Dell, and I am using their software to load.

> >>>

> >>> Everything went fine with the install and the software loaded

> >>> without incident. I patched the system fully with MS patches.

> >>> Everything was great until I went to configure the server for AD as

> >>> a member server on a domain with 2003 std (R1).

> >>>

> >>> First thing that happend is this release is R2 and the other

> >>> releases

> >>> on the

> >>> other two servers are R1 release that is fully patched.

> >>> The first thing it errored out was I got a message stating that the

> >>> Schema

> >>> wasn't compatable between the this version R2 and the other R1 and

> >>> that I

> >>> had to run the Adprep tool adprep.exe /forestprep and adprep

> >>> /domainprep.

> >>> Ok, i stopped right there, then got the 2003 disk 1 and run the

> >>> adprep

> >>> tool on the schema master PC that had R1 on it. Both Adprep

> >>> commands

> >>> failed... I did some internet searching and found out that the

> >>> Adprep

> >>> tool on Disk 1 is bad and that I needed to run the tool from CD #2.

> >> The adprep on disk 1 is for the upgrade to schema version 30, the

> >> adprep on disk 2 is for the upgrade to schema version 31, which you

> >> needed because 30 is used with 2003 "normal", btw 13 is windows 2000

> >> and 44 is windows 2008. You can find out easy with "schupgr" on a

> >> command prompt on the schema master.

> >>

> >>> Runing that version on that disk then both commands ran fine on the

> >>> schema master. Both /forestprep and /domainprep ran successully.

> >>>

> >> Becasue it was the correct version upgrade.

> >>

> >>> Then I restarted the dcpromo wiz on the R2 system and completed the

> >>> inclusion of the new server to active directoy.... I got the screen

> >>> that it was successful. Now here is where the issue is...

> >>>

> >>> On rebooting the server (new one) now i only get ONE option in the

> >>> domain dropdown box and that is the domain, the "local workstation"

> >>> is not showing up. ok, I thought, that is strange, then i attempted

> >>> a domain login using domain administrator credentials since it is

> >>> the only option to pick... but the screen goes something like

> >>> this...

> >>>

> >> On a domain controller you are not able to logon locally. As soon as

> >> the server is a DC this option is not possible. Only member servers

> >> and workstations have the option.

> >>

> >>> Enter username/password and domain, screen accepts credentials and

> >>> goes

> >>> away...

> >>> immediatly i get a "Starting windows" or "loading profile" (can't

> >>> remember

> >>> exactly which)... then instant flash, prompt changes to "Windows

> >>> shutting

> >>> down..". it then reboots and brings me back to the login window.

> >>> Another stinking "Constant" reboot loop... I have disabled the

> >>> auto-reboot feature so I could at least see if it is a BSOD or

> >>> driver... but it just reboots..

> >>> I can log in using ONLY two options after the F8 key... Directory

> >>> service restore mode, and Safe mode.... any other options restarts

> >>> the pc...

> >>>

> >> In safe mode check the event viewer for errors or if the server is

> >> up, open the event viewer from the other DC and check. Did you try

> >> logon with remote desktop, does it also reboot?

> >>

> >>> Addiing to an existing AD domain corrupted the local box somehow

> >>> because the local workstaton isn't showing up in the pick box to

> >>> select local or domain log-in... any clue as to where to start? I

> >>> had a similar instance happen to an XP box where the

> >>> c:\windows\system32\userinit.exe key was corrupt or missing from the

> >>> registry... this registry has it...

> >>>

> >> Make sure that you run an Antivirus check with up to date software,

> >> also possible if you make it remote from a test workstation not form

> >> a production one.

> >>

> >>> thanks

> >>>

>

>

>

[Guest Meinolf Weber]

Re: ActiveDirectory promotion causes reboot loop (solved)

 

Re: ActiveDirectory promotion causes reboot loop (solved)

 

Hello Tim_S,

 

Nice to hear that you find it.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

 

> ok, looked through all the logs, nothing showed to be the cause

>

> I found out that i can log on using another adminstrator account

> without the system rebooting, I thought ok a profile is corrupt... I

> deleted the profile for the administrator account, I then rebooted the

> system, and tried to log on as Administrator, the system goes, logging

> on, then shutting down. I log in using my backup user account with

> administrator priv. and the log shows nothing as to why it was

> failing under the Administrator account.

>

> I then experimented a little further.. what was diff between my

> administrator accout and my backup account? Then it hit me like a

> meteor hitting the planet... the Administrator account is running a

> batch file as part of the log-in script. My secondary account was not

> running a batch file as part of the login script. When I added the

> batch file to my secondary account, the server restarted exhibited the

> same behavior. Now i have narrowed it down to the batch file. Upon

> examining by scripting in this file, in which i have it doing a number

> of administrative task for me, I have it calling a windows update

> site, and symantec update site so as to make it easier for me to do

> monthly updates. Well, I also have programmed it to do application

> updates to a medical program when I log in. In the batch routine i

> was checking for the existance of a text file (update.txt) and if it

> was not found, to execute the install of an application. I forgot to

> remove the coding after the updates were done and after i removed the

> install program. Well the application was not running the install of

> the update and was skipping through the batch file like it should.

> After the app was supposed to update, it was supposed to execute a

> reboot and at the end of that code as i had a command > shutdown -r -f

> -t 00 That was the command that was executing... duh.... The batch

> file was skipping through not installing the app and thus doing what i

> acutally told it to do restart unconditionally... Yep my own

> stupidity and scripting error was the problem. The reason it didn't

> happen on the other system(s) is the application is installed and the

> text file is there to skip the section in the login script of

> installing the update.

>

> Of course there would be no log file.. and no errors... it just

> happend so fast i could not see the batch file kicking in...

>

> Thanks for the help...

>

> Mystery solved...

> Thanks Weber...

> "Meinolf Weber" wrote:

>

>> Hello Tim_S,

>>

>> You stated:

>> "Then I restarted the dcpromo wiz on the R2 system and completed the

>> inclusion

>> of the new server to active directoy.... I got the screen that it was

>> successful.

>> Now here is where the issue is..."

>> This is the step where you made this server an additional domain

>> controller.

>>

>> Again see inline.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> Thanks Weber,

>>>

>>> i am adding this as a member server not a master... it should have

>>> the local PC listed... my schema master (PDC) has it's local pc

>>> listed as an option and so does the other member server...

>>>

>> Again. This is not possible on a Domain Controller. On member

>> servers, yes.

>>

>>> This is a new load, i have not loaded any antivirus on it yet. The

>>> domain is secured by Symantec AV Corp 10 and the domain is virus

>>> free so i am not worried about that.

>>>

>>> Only errors in the log are 1202 DFS replication service failed to

>>> contact domain controller... which could be because i am only able

>>> to view the event log in safe mode.

>>>

>> As i said before, you can open the event log from any other computer.

>> Rightclick MY COMPUTER, choose MANAGE, on Computer Management(Local)

>> rightclick again and choose "Connect to another computer". From here

>> on you can also see the EVENT VIEWER of other machines without

>> logging on.

>>

>>> Yes remote control (RDP) reboots the system as well..

>>>

>>> t

>>>

>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

>>> news:ff16fb6698a38caf9baef5319d0@msnews.microsoft.com...

>>>

>>>> Hello Tim_S,

>>>>

>>>> See inline.

>>>>

>>>> Best regards

>>>>

>>>> Meinolf Weber

>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

>>>> and

>>>> confers no rights.

>>>> ** Please do NOT email, only reply to Newsgroups

>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>> I am installing a Windows 2003 std server on a dell 2950 system.

>>>>> Brand New from Dell, and I am using their software to load.

>>>>>

>>>>> Everything went fine with the install and the software loaded

>>>>> without incident. I patched the system fully with MS patches.

>>>>> Everything was great until I went to configure the server for AD

>>>>> as a member server on a domain with 2003 std (R1).

>>>>>

>>>>> First thing that happend is this release is R2 and the other

>>>>> releases

>>>>> on the

>>>>> other two servers are R1 release that is fully patched.

>>>>> The first thing it errored out was I got a message stating that

>>>>> the

>>>>> Schema

>>>>> wasn't compatable between the this version R2 and the other R1 and

>>>>> that I

>>>>> had to run the Adprep tool adprep.exe /forestprep and adprep

>>>>> /domainprep.

>>>>> Ok, i stopped right there, then got the 2003 disk 1 and run the

>>>>> adprep

>>>>> tool on the schema master PC that had R1 on it. Both Adprep

>>>>> commands

>>>>> failed... I did some internet searching and found out that the

>>>>> Adprep

>>>>> tool on Disk 1 is bad and that I needed to run the tool from CD

>>>>> #2.

>>>> The adprep on disk 1 is for the upgrade to schema version 30, the

>>>> adprep on disk 2 is for the upgrade to schema version 31, which you

>>>> needed because 30 is used with 2003 "normal", btw 13 is windows

>>>> 2000 and 44 is windows 2008. You can find out easy with "schupgr"

>>>> on a command prompt on the schema master.

>>>>

>>>>> Runing that version on that disk then both commands ran fine on

>>>>> the schema master. Both /forestprep and /domainprep ran

>>>>> successully.

>>>>>

>>>> Becasue it was the correct version upgrade.

>>>>

>>>>> Then I restarted the dcpromo wiz on the R2 system and completed

>>>>> the inclusion of the new server to active directoy.... I got the

>>>>> screen that it was successful. Now here is where the issue is...

>>>>>

>>>>> On rebooting the server (new one) now i only get ONE option in the

>>>>> domain dropdown box and that is the domain, the "local

>>>>> workstation" is not showing up. ok, I thought, that is strange,

>>>>> then i attempted a domain login using domain administrator

>>>>> credentials since it is the only option to pick... but the screen

>>>>> goes something like this...

>>>>>

>>>> On a domain controller you are not able to logon locally. As soon

>>>> as the server is a DC this option is not possible. Only member

>>>> servers and workstations have the option.

>>>>

>>>>> Enter username/password and domain, screen accepts credentials and

>>>>> goes

>>>>> away...

>>>>> immediatly i get a "Starting windows" or "loading profile" (can't

>>>>> remember

>>>>> exactly which)... then instant flash, prompt changes to "Windows

>>>>> shutting

>>>>> down..". it then reboots and brings me back to the login window.

>>>>> Another stinking "Constant" reboot loop... I have disabled the

>>>>> auto-reboot feature so I could at least see if it is a BSOD or

>>>>> driver... but it just reboots..

>>>>> I can log in using ONLY two options after the F8 key... Directory

>>>>> service restore mode, and Safe mode.... any other options restarts

>>>>> the pc...

>>>> In safe mode check the event viewer for errors or if the server is

>>>> up, open the event viewer from the other DC and check. Did you try

>>>> logon with remote desktop, does it also reboot?

>>>>

>>>>> Addiing to an existing AD domain corrupted the local box somehow

>>>>> because the local workstaton isn't showing up in the pick box to

>>>>> select local or domain log-in... any clue as to where to start?

>>>>> I had a similar instance happen to an XP box where the

>>>>> c:\windows\system32\userinit.exe key was corrupt or missing from

>>>>> the registry... this registry has it...

>>>>>

>>>> Make sure that you run an Antivirus check with up to date software,

>>>> also possible if you make it remote from a test workstation not

>>>> form a production one.

>>>>

>>>>> thanks

>>>>>

[Guest Anthony [MVP]]

Re: ActiveDirectory promotion causes reboot loop

 

Tim_S

I saw you had this solved, but something else is up because:

- you have made the server a domain controller, not a member server. To be a

member server you just need to join the domain.

- on a DC there is no dropdown box for the local machine, because there is

no local security database, only the domain, so you can't log in locally on

a DC.

- if you don't need this server to be a domain controller you can just run

dcpromo again to demote it.

Anthony

http://www.airdesk.com

 

 

 

"Tim_S" <NOSPAM@whereever.net> wrote in message

news:ertgQ95KJHA.3496@TK2MSFTNGP04.phx.gbl...

> Thanks Weber,

>

> i am adding this as a member server not a master... it should have the

> local PC listed... my schema master (PDC) has it's local pc listed as an

> option and so does the other member server...

>

> This is a new load, i have not loaded any antivirus on it yet. The domain

> is secured by Symantec AV Corp 10 and the domain is virus free so i am not

> worried about that.

>

> Only errors in the log are 1202 DFS replication service failed to contact

> domain controller... which could be because i am only able to view the

> event log in safe mode.

>

> Yes remote control (RDP) reboots the system as well..

>

> t

>

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

> news:ff16fb6698a38caf9baef5319d0@msnews.microsoft.com...

>> Hello Tim_S,

>>

>> See inline.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>

>>> I am installing a Windows 2003 std server on a dell 2950 system.

>>> Brand New from Dell, and I am using their software to load.

>>>

>>> Everything went fine with the install and the software loaded without

>>> incident. I patched the system fully with MS patches. Everything was

>>> great until I went to configure the server for AD as a member server

>>> on a domain with 2003 std (R1).

>>>

>>> First thing that happend is this release is R2 and the other releases

>>> on the

>>> other two servers are R1 release that is fully patched.

>>> The first thing it errored out was I got a message stating that the

>>> Schema

>>> wasn't compatable between the this version R2 and the other R1 and

>>> that I

>>> had to run the Adprep tool adprep.exe /forestprep and adprep

>>> /domainprep.

>>> Ok, i stopped right there, then got the 2003 disk 1 and run the adprep

>>> tool on the schema master PC that had R1 on it. Both Adprep commands

>>> failed... I did some internet searching and found out that the Adprep

>>> tool on Disk 1 is bad and that I needed to run the tool from CD #2.

>>

>> The adprep on disk 1 is for the upgrade to schema version 30, the adprep

>> on disk 2 is for the upgrade to schema version 31, which you needed

>> because 30 is used with 2003 "normal", btw 13 is windows 2000 and 44 is

>> windows 2008. You can find out easy with "schupgr" on a command prompt on

>> the schema master.

>>

>>> Runing that version on that disk then both commands ran fine on the

>>> schema master. Both /forestprep and /domainprep ran successully.

>>

>> Becasue it was the correct version upgrade.

>>

>>> Then I restarted the dcpromo wiz on the R2 system and completed the

>>> inclusion of the new server to active directoy.... I got the screen

>>> that it was successful. Now here is where the issue is...

>>>

>>> On rebooting the server (new one) now i only get ONE option in the

>>> domain dropdown box and that is the domain, the "local workstation" is

>>> not showing up. ok, I thought, that is strange, then i attempted a

>>> domain login using domain administrator credentials since it is the

>>> only option to pick... but the screen goes something like this...

>>

>> On a domain controller you are not able to logon locally. As soon as the

>> server is a DC this option is not possible. Only member servers and

>> workstations have the option.

>>

>>> Enter username/password and domain, screen accepts credentials and

>>> goes

>>> away...

>>> immediatly i get a "Starting windows" or "loading profile" (can't

>>> remember

>>> exactly which)... then instant flash, prompt changes to "Windows

>>> shutting

>>> down..". it then reboots and brings me back to the login window.

>>> Another stinking "Constant" reboot loop... I have disabled the

>>> auto-reboot feature so I could at least see if it is a BSOD or

>>> driver... but it just reboots..

>>>

>>> I can log in using ONLY two options after the F8 key... Directory

>>> service restore mode, and Safe mode.... any other options restarts the

>>> pc...

>>

>> In safe mode check the event viewer for errors or if the server is up,

>> open the event viewer from the other DC and check. Did you try logon with

>> remote desktop, does it also reboot?

>>

>>> Addiing to an existing AD domain corrupted the local box somehow

>>> because the local workstaton isn't showing up in the pick box to

>>> select local or domain log-in... any clue as to where to start? I

>>> had a similar instance happen to an XP box where the

>>> c:\windows\system32\userinit.exe key was corrupt or missing from the

>>> registry... this registry has it...

>>

>> Make sure that you run an Antivirus check with up to date software, also

>> possible if you make it remote from a test workstation not form a

>> production one.

>>

>>> thanks

>>>

>>

>>

>

>