after demotion you still need to delete the server object manually in sites and 
services (this is normal) (everything else like computer account, frs stuff and 
ntds settings is removed by dcpromo)
 
1) you can promote servers to DCs while they are member of a domain or not. it 
does not matter. the only difference is during DCPROMO. if the server is 
already a member then that step is skipped
 
2) if the NTDS setting is still there the demotion was not successful. perform 
a metadata cleanup first before promoting the other server to a DC 
(http://blogs.dirteam.com/blogs/jorge/archive/2005/12/03/213.aspx)
 
Met vriendelijke groeten / Kind regards,
Ing. Jorge de Almeida Pinto
Senior Infrastructure Consultant
MVP Windows Server - Directory Services
 
LogicaCMG Nederland B.V. (BU RTINC Eindhoven)
(   Tel     : +31-(0)40-29.57.777
(   Mobile : +31-(0)6-26.26.62.80
*   E-mail : <see sender address>

________________________________

From: [EMAIL PROTECTED] on behalf of Al Lilianstrom
Sent: Thu 2006-08-17 14:36
To: [email protected]
Subject: [ActiveDir] w2k3 dcpromo failure



We're in the process of replacing our w2k DCs with w2k3 machines.
Forestprep and domainprep went fine as well as putting the first new
w2k3 DC up.

Yesterday we demoted one of the old w2k machines and removed it from the
domain. Configured a w2k3 server with the same name and IP and ran
dcpromo when it was a workgroup member. About 6 minutes into the process
  this event showed up in the directory service log

----

Event Type:     Error
Event Source:   NTDS General
Event Category: Internal Processing
Event ID:       1168
Date:           8/16/2006
Time:           2:06:35 PM
User:           NT AUTHORITY\ANONYMOUS LOGON
Computer:       BIRD
Description: Internal error: An Active Directory error has occurred.

Additional Data
Error value (decimal): -1073741823
Error value (hex): c0000001
Internal ID: 3000e54

and then this

Event Type:     Information
Event Source:   NTDS Setup
Event Category: Setup
Event ID:       1442
Date:           8/16/2006
Time:           2:06:57 PM
User:           N/A
Computer:       BIRD
Description:
During the cleanup operation of a failed Active Directory installation,
the NTDS Settings object for the local server could not be deleted from
the remote domain controller.

Server:
CN=BIRD,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=wn,DC=fnal,DC=gov

Remote domain controller: lbird.wn.fnal.gov

User Action
Delete this object manually using Active Directory Sites and Services.

Additional Data
Error value: The RPC server is unavailable. 1722

----

The server ended up being non responsive and required a reboot.

I've been doing some research and I can' find answers to a a couple of
questions:

1) Would starting the dcpromo process with the server not in the domain
have caused this? I've always added the machine to the domain before
promotion. The admin who attempted the promotion said he has done it
this way before.

2) When deleting the object from AD (as specified above) the option that
actually deletes the object states that the DC is permanently offline
and can no longer be demoted... Does chosing this option prevent me from
adding the DC with the same name (Like seizing FSMO roles) ?

        al

--

Al Lilianstrom
CD/CSS/CSI
[EMAIL PROTECTED]
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx




This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you.

<<winmail.dat>>

Reply via email to