DC's didn't move into my new site

[Guest]

Hello all,

I checked the site-link, the subnet definition, and the site itself, they
all look fine. There are three DC's; the first we moved in manually so we
wouldn't get any "there are no DC's in the site" type of errors, the second,
we waited, and it didn't do it, and was having some other problems so we
moved it manually, the third, we're doing a wait and see, but it's been 3
days. I've ran KCC, rebooted the server, it just won't budge. There are no
errors, and once I moved the two DC's in there, the replication architecture
KCC chose is appropriate, but it just isn't moving the DC's into the site.
What gives?

 

[Paul Williams [MVP]]

The server object that represents a DC won't automatically move into a new
site. It will get created in it's correct site, but won't move. This is
because you can choose DCs to cover specific sites. When you move a DC
between sites, you must move the server object in DSSITE.MSC yourself.

 

[Guest]

Thanks so much for your reply. That was driving me crazy.

 

[Santhosh Sivarajan]

If the Site associate is correct with the Subnet, it should automatically
move the DCs to the appropriate sites.

 

[Paul Williams [MVP]]

Only when you promote a new DC. It won't automatically move it afterwards
(if the site is created after the DC is created). There are cases whereby
you would want to manually assign a DC to a site and not use auto coverage;
this wouldn't be possible if what you say were correct.

 

[Santhosh Sivarajan]

yes. thats true.