Replication is another common AD trobleshooting scenario.
AD replication issues usually turn out to be caused by one of the following:
a) Faulty, substandard or misconfigured network equipment or WAN links
b) USN rollback issues caused by using unsupported restore methods (disk imaging of DC's, P2V utilities, snapshots, etc.)
c) DNS issues
d) Lingering objects
Further reading is available at "Troubleshooting AD Replication"
How to detect and recover from a USN rollback in Windows Server 2003
How to detect and recover from a USN rollback in Windows 2000 Server
Domain controllers do not demote gracefully when you use the Active Directory Installation Wizard to force demotion in Windows Server 2003 and in Windows 2000 Server
How to remove data in Active Directory after an unsuccessful domain controller demotion
Remember metadata cleanup in Windows 2008 or Windows 2012 active directory is taken care of automatically. This is how it works. Suppose after you demote the DC using DCPROMO and its ends up in failure, or say the H\W of an old DC gave up and now you wish to replace it with a new one follow the setps given below:
1) Get into the AD users and computers snap in.
2) Select the OU where that DC resides.
3) Right click on it and delete it.
4) Rest of the metadata cleanup activity will be carried out by AD itself. So you see how easy it has become in Windows 2008 and Windows 2012.
AD replication issues usually turn out to be caused by one of the following:
a) Faulty, substandard or misconfigured network equipment or WAN links
b) USN rollback issues caused by using unsupported restore methods (disk imaging of DC's, P2V utilities, snapshots, etc.)
c) DNS issues
d) Lingering objects
Further reading is available at "Troubleshooting AD Replication"
How to detect and recover from a USN rollback in Windows Server 2003
How to detect and recover from a USN rollback in Windows 2000 Server
Domain controllers do not demote gracefully when you use the Active Directory Installation Wizard to force demotion in Windows Server 2003 and in Windows 2000 Server
How to remove data in Active Directory after an unsuccessful domain controller demotion
Remember metadata cleanup in Windows 2008 or Windows 2012 active directory is taken care of automatically. This is how it works. Suppose after you demote the DC using DCPROMO and its ends up in failure, or say the H\W of an old DC gave up and now you wish to replace it with a new one follow the setps given below:
1) Get into the AD users and computers snap in.
2) Select the OU where that DC resides.
3) Right click on it and delete it.
4) Rest of the metadata cleanup activity will be carried out by AD itself. So you see how easy it has become in Windows 2008 and Windows 2012.
0 comments:
Post a Comment