Unhost and Rehost the global catalog partition
Hello all,
Hope this post finds you in good health and spirit.
Unhost and Rehost the global catalog partition
This post is regarding how to unhost and rehost the global partition for a domain controller. It can be done only if there are lingering objects exist in global partition. we can also do unhost and rehost by site and service but that do for all global catalog partitions. better if you guys do the unhost and rehost for that partition, in which lingering objects occurs instead of doing for all GC partitions.
We have detected the lingering objects in global partition on DC08 domain controller. Now we are going to remove these lingering objects by unhost and rehost the global catalog partition. As its not possible to remove the lingering objects from read only partition by lingering objects removal command and only option to unhost and rehost the partition.
Clients connecting to DC08 could not query for the GC partition DC=WindowsTechno,DC=Local hence suggested to perform outside of business hours, so that you do not hear complain form the clients.
Fully Qualified Domain Name (FQDN) is not needed in this step since you will be running this from the actual affected domain controller. Kindly run the below Command to un-host GC partition on DC08
repadmin /unhost DC08 “DC=WindowsTechno,DC=Local”
Wait for some time as its depending on the size of the partition Data will take time.Once unhosting is done kindly execute the below Command to Re-host GC partition on DC08.
repadmin /rehost DC08 “DC=WindowsTechno,DC=Local” DC05.windowstechno.local”
After these steps are all completed, the lingering objects should be gone from global catalog partition, you should have better protection in place against them (with the Strict Replication Consistency turned on) and you should no longer get Unknown User or Not Found NDRs on relatively new mailboxes.
So, that’s all in this blog. I will meet you soon with next stuff .Have a nice day !!!
Recommended contents
How to Check the Active Directory Database Integrity
Disabling and Enabling the Outbound Replication
DFS Replication Service Stopped Replication
What is Strict Replication Consistency
The replication operation failed because of a schema mismatch between the servers involved
Troubleshooting ad replication error 8418 the replication operation failed because of a schema mismatch between the servers
How to export replication information in txt file
Repadmin Replsummary
Enabling the outbound replication
Disabling and enabling replication on schema master domain controller
How to enable strict replication consistency
How to prevent lingering objects replication in active directory
AD replication process overview
How to force active directory replication
Change notification in replication process
How to check replication partner for a specific domain controller
dcdiag test replications
DFS Replication Event
Unidirectional replication
Guys please don’t forget to like and share the post. You can also share the feedback on below windows techno email id.
If you have any questions feel free to contact us on admin@windowstechno.com also follow us on facebook@windowstechno to get updates about new blog posts.