|
Home > Archive > 70-217 > December 2003 > Force replication of entire domain?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Force replication of entire domain?
|
|
| jbachert 2003-11-24, 11:45 am |
| Question:
Lets say I have a domain with 5 sites. Each site has a domain controller.
I decide to demote a DC at one site.
How can I force replication to make sure ALL the DC's that are left know about this DC being gone?
Thanks!
John | |
| adam salam 2003-11-24, 5:43 pm |
| quote:
Originally posted by jbachert
Question:
Lets say I have a domain with 5 sites. Each site has a domain controller.
I decide to demote a DC at one site.
How can I force replication to make sure ALL the DC's that are left know about this DC being gone?
Thanks!
John
From Windows Help:
-----------------
To force replication over a connection
Open Active Directory Sites and Services.
In the console tree, click NTDS Settings for the server that you want to force replication.
>Active Directory Sites and Services
>Sites
>site that contains the connection over which you want to replicate directory information
>Servers
>server that you want to force replication
>NTDS Settings
In the details pane, right-click the connection over which you want to replicate directory information, and then click Replicate Now.
Read more:
http://www.microsoft.com/technet/tr..._force_repl.asp | |
| curiousgeorge 2003-11-26, 2:31 am |
| Actually, during the demotion process, the DC being demoted has to connect to another DC in order for demotion to complete successfully. If it cannot contact another DC during the demotion process, it will pop up an error and the DC will not be demoted.
The reason for this is so that all the information on the DC being demoted can be replicated to another DC.
So the answer to your question is- by default, another DC is automatically notified when a DC is being demoted.
It is not neccessary for ALL DC's to know about the demotion of one DC unless it is the last DC in that domain. | |
| adam salam 2003-11-26, 5:55 am |
| quote:
Originally posted by curiousgeorge
Actually, during the demotion process, the DC being demoted has to connect to another DC in order for demotion to complete successfully. If it cannot contact another DC during the demotion process, it will pop up an error and the DC will not be demoted.
The reason for this is so that all the information on the DC being demoted can be replicated to another DC.
So the answer to your question is- by default, another DC is automatically notified when a DC is being demoted.
It is not necessary for ALL DC's to know about the demotion of one DC unless it is the last DC in that domain.
Thanks for the valuable information 
I forgot that it's really the demoted DC has to contact other DC in order to be demoted, in fact I have sent one Q here before regarding this problem:
"Could not demote a domain controller"
I discovered that the DC in question couldn't contact another DC controller, and the demotion process was failed. | |
| Tech Ranger 2003-11-30, 11:52 pm |
| I think it is humiliating for a dc to be demoted. | |
| adam salam 2003-12-01, 7:39 am |
| quote:
Originally posted by Tech Ranger
I think it is humiliating for a dc to be demoted.
You are certainly correct 
None accept the "Demotion", even the mineral world  |
|
|
|
|