James,
Thanks for the advise - my concern is that it has been working as part of
the domain for some time now.
1. When forced removed it simply became a member server of the domain. It
was never taken right off of the domain back to being only a work group.
2. All our user shares are currently on this server that I wish to promote
to be a DC and do not want to take it off the domain all together, change
its name and then add it back to the domain with another name as all login
scripts and drive mappings to this server would need updating.
- Is there a way around this so that I can keep the same server name
and not have to change login scripts and re-create shares again?
3. I have already used KB216948 to cleanup on the remaining DC. Does this
need to be done on the failed DC as well?
Rodney
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Blair, James
Sent: Friday, 22 October 2004 12:50 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Promoting 2nd Domain Controller in AD (The
Credentials Supplied C onflict with an Existing set of credentials)
Rodney,
If you used DCPROMO /FORCEREMOVAL ex DC should be on a workgroup if not put
it on one...rename the server...
Look at Q216498: Remove Data in Active Directory After an Unsuccessful
Domain Controller Demotion. Clear up any entries pertaining to the "old"
server.
Then add server to the domain and then do a dcpromo.
James
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rodney Gardiner
Sent: Friday, 22 October 2004 11:21 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Promoting 2nd Domain Controller in AD (The Credentials
Supplied C onflict with an Existing set of credentials)
This is further to my previous problem about promoting but the Group Policy
is fixed. I am now trying to promote the server that I forced removed as
explain in my previous post and receive the error
"The Credentials Supplied Conflict with an Existing set of credentials"
I checked all drive mapping etc to see if there was a mapping to cause this
error and there were none.... Well none visible. I used "NET USE" in a
command prompt and it showed the following:-
Status = OK Local = Remote = \\VLSEXCH2000.VANGUARD.COM.AU\SYSVOL
Network = Microsoft Windows Network
I have been told that this is because this particular server believes that
it is still part of AD. I was also informed that there is a post on this
site that explains how to do a registry hack to change a setting to make the
server believe that it is just part of the domain and not part of AD.
Once
this change has been made I then has been informed to delete SYSVOL and NTDS
folders. Not sure if a restart was required after this and then try the
dcpromo and all should be fine.
I can not find this post so can anyone please help me.
Rodney
P.S. I am now able to successfully promote other Win2000 Servers to be part
of AD since the Group Policy has been fixed.
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive:
http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
List info : http://www.activedir.org/mail_list.htm
List FAQ : http://www.activedir.org/list_faq.htm
List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
