Re: Demote Windows Server 2000 Domain Controller
- From: Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
- Date: Mon, 8 Jun 2009 12:52:20 +0000 (UTC)
Hello CHallisy,
This doesn't make sense and is not supported!!!
This will result in USN rollback. NEVER have 2 same DCs, like VM and physical, running together.
USN rollback:
http://support.microsoft.com/kb/875495
Remove immediately the physical machine from the network, because the VMs are more uptodate. Then check with the above article if you have the USN rollback.
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
"Ace Fekay [Microsoft Certified Trainer]" wrote:
"CHallisy" <CHallisy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in messageOriginally, there were 2 servers, let's call them S1 and S2. S1 was
news:6945AA7A-7320-4D73-99A8-9979C3037BED@xxxxxxxxxxxxxxxx
I replaced a server with a new server. Consequently, I now have twoNo, this is not a catch-22. It's the way AD and DCs work.
servers
that are configured exactly the same. Now, they are both a domain
controller,
with the same name, on the same domain.
By reading here:
http://technet.microsoft.com/en-us/library/cc740017.aspx
I found out how to demote the old server from Domain Controller.
However, when I run through the dcpromo, I get this error message:
"The operation failed because:
A domain controller could not be contacted for the domain
xxxxxxx.local
that
contained an account for this computer.
Make the computer a member of a workgroup then rejoin the domain
before retrying the promotion.
"The specified domain does not exist or could not be contacted""
Unfortunately, I can not rename the computer because it is a domain
controller. Also, I can not demote it from a domain controller
because the new sever is using the same name on the domain.
Is this just a ridiculous catch 22, or is there a way around this?
And creating a same name DNS and NetBIOS domain name on the same
network, you created a duplicate only in name, but not with AD. As
Meinolf said, you will need to disjoin your current machines, and
rejoin them to the new domain. This is because when a domain/forest
is created, it creates a new SID and GUID identifiying it, regardless
of the domain name. Hhowever, because of the same name, now NetBIOS
services finding a duplicate NetBIOS name, will cause the server
service to stop, causing other issues. Therefore, creating the same
name will cause additional headaches.
Curious, what was the reason you had to go through this? Was there a
problem with the DC?
Also, can you post an unedited ipconfig /all from both DCs, please?
-- Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@xxxxxxxxxxxxxxxxxxxxxxx
For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.
"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay
the DC. The two servers were moved onto a third physical server, using
VMWare, both are running on the same machine now.
So, S1 and S2 exist, in their original form, on a new machine. The
original S1 and S2 laid unplugged and dormant.
I brought the original S1 online. Consequently, I now had 2 servers
(both S1) on the network.
Did that make sense?
.
- References:
- Re: Demote Windows Server 2000 Domain Controller
- From: CHallisy
- Re: Demote Windows Server 2000 Domain Controller
- Prev by Date: Re: Demote Windows Server 2000 Domain Controller
- Next by Date: Re: Demote Windows Server 2000 Domain Controller
- Previous by thread: Re: Demote Windows Server 2000 Domain Controller
- Index(es):
Relevant Pages
|