Inscrivez-vous ou connectez-vous pour rejoindre votre communauté professionnelle.
Because Infrastructure master performs its task by comparing its state against the state of a GC - and updates other DCs in the same domain based on the outcome. Effectively, the update would never took place since no differences would be detected...!!!!
Hope this clarifies your question.
Shaik
If the infrastructure master and global catalog are on the same domain controller, theinfrastructure master will not function. The infrastructure master will never find data that is out of date, so will never replicate any changes to the other domain controllers in the domain.
If all of the domain controllers in a domain are also hosting the global catalog, all of the domain controllers will have the current data and it does not matter which domain controller holds the infrastructure master role.
we have the Infrastructure role on our 2008 DC, which is a GC.
The IM is responsible for updating cross-domain object references each DC in the Domain, to do that it needs to check for changes on an available GC, then compares its information with the information that the GC has, if any changes, then updates its local information, and updates cross-domain object references each DC in the Domain.- The Problem is that If the IM is also a GC, when is going to check for changes he asks for a GC and because the IM is also a GC it "thinks" that it has all information updated and there's no need to update the DCs on its domain causing others DCs ending up with nonupdated information, remember DCs in a domain only know everything about their domain, because the domain partition is replicated between them.
Because phantom object will not be updated. This phantom object is a special kind of object it stores cross reference object when infrastructure master update from another domain.
If the infrastructure master role holder is also a global catalog server, the phantom indexes are never created or updated on that domain controller. This behavior occurs because a global catalog server contains partial replica of every object in Active Directory. Infrastructure master does not store phantom versions of the foreign objects because it already has a partial replica of the object in the local global catalog. For this process to work correctly in a multi domain environment, the infrastructure master role holder cannot be a global catalog server. Be aware that the first domain controller in the forest holds all the five FSMO roles and is also a global catalog. Therefore, we must transfer either role to another computer as soon as another domain controller is installed in the domain if you plan to have multiple domains.
it will check difference of global catalog,if they are in same dc it will not find any change
