I'm reading between the lines here, but if you're talking about taking that
dc offline just to keep as a potential "backup" that could be brought back
up in case it was needed, I would not recommend it. Once the data on that
machine is over 60 days old, it's tombstoned, and you don't want that box
back up again.
As long as the box itself is still a member of the domain as a dc, AD (kcc
and istg) will want to create replication links for it to talk with other
dc's. Yuo can kill that to be able to configure the replication links
manually, and just exclude that dc, but I see a lot of downside here with
little upside, so aren't sure what the end result is that you're trying to
accomplish.
--
David Brandt
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
J.H said:
Hi,
Talking about 'just turned off the 1st DC situation', so we will do the
seizing operation. That means the site and metadata is still in AD
site,schema,
how do we remove the site replication of 1st DC with the other DCs
completely ?
( I was not talking about demote 1st DC, but about the situation when the
1st DC
is turned off and never bring back online).
Please help with your idea, thanks
Regards,
J.H
Richard McCall said:
When the First DC(DNS) is going to be removed you should replace the IP
address used for DNS with the Second DC. When you demote the first DC it
will remove the site and metadata
--
Richard McCall [MSFT]
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Hi there,
1st DC is about retiring !!
2nd DC is about seizing up to 5 FSMO roles
(DNS setting of 2nd DC is:
DNS1 = 1st DC's IP
DNS2 = 2nd DC's IP)
Question:
- what will be the DNS setting of 2nd DC after seize operation ?
should it be:
DNS1 = 2nd DC's IP
DNS2 = 2nd DC's IP
- How do we remove the replication in the site when 1st DC is
removed