GTMike
asked on
Replication errors after AD 2003->2008 Schema upgrade
Hi EEr's
Have recently taken over a new client who have a small network with a couple of servers:
Previous IT guru attempted (and successfully?) upgraded their AD schema to 2008 (in preparation for their move to Exchange 2010 & new 2008 Servers), however one of their DCs failed the upgrade. Server was due to be decommissioned but was overlooked during the upgrade, has some serious OS issues that prevent communication to the network.
Should I manually remove it from the AD environment with NTDSutil (following steps identified here:http://www.petri.co.il/delete_failed_dcs_from_ad.htm) or am I better off trying to repair the OS and decommission via DCPromo?
Previous IT guy had attempted repairs, but AD replication errors & DNS resolution issues (due to non-replication of AD) that are piling up encouraged him to find greener pastures.
All FSMO roles, DHCP & DNS services have been transferred off the old server some time ago, and DCDiag doesn't report any issues with their primary DC (Secondary GC Servers are reporting replication warnings!).
Any advice?!
Regards
Mike
Have recently taken over a new client who have a small network with a couple of servers:
Previous IT guru attempted (and successfully?) upgraded their AD schema to 2008 (in preparation for their move to Exchange 2010 & new 2008 Servers), however one of their DCs failed the upgrade. Server was due to be decommissioned but was overlooked during the upgrade, has some serious OS issues that prevent communication to the network.
Should I manually remove it from the AD environment with NTDSutil (following steps identified here:http://www.petri.co.il/delete_failed_dcs_from_ad.htm) or am I better off trying to repair the OS and decommission via DCPromo?
Previous IT guy had attempted repairs, but AD replication errors & DNS resolution issues (due to non-replication of AD) that are piling up encouraged him to find greener pastures.
All FSMO roles, DHCP & DNS services have been transferred off the old server some time ago, and DCDiag doesn't report any issues with their primary DC (Secondary GC Servers are reporting replication warnings!).
Any advice?!
Regards
Mike
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When you say "successfully?" you can verify that http://technet.microsoft.com/en-us/library/dd464018(WS.10).aspx#BKMK_VerifyForestPrep
See if your schema is at 44 for 2008 or 47 for 2008 R2.
I'd also go with the removal and metadata cleanup.
Thanks
Mike
See if your schema is at 44 for 2008 or 47 for 2008 R2.
I'd also go with the removal and metadata cleanup.
Thanks
Mike
"dcpromo /forceremoval" will just uninstall AD from this old DC and place it in a workgroup. It will not replicate the "demotion" to its old replication partners. Thus you need to run the MD Cleanup.
You can compare the schema version on this DC and see if the schema extension has been replicated to the old DC. But I'd not hesitate. Force it out :)
You can compare the schema version on this DC and see if the schema extension has been replicated to the old DC. But I'd not hesitate. Force it out :)
ASKER
Great advice for confirmation of a fix, thank you!
ASKER
Am considering trying to repair it (Was an old Win2000 that was upgraded to Win2003 by the look of it), but wondering if it'll even communicate properly once online given that its AD infrastructure missed the Schema upgrade?
Given that the old server won't even communicate with the domain in its present configuration (DCDiag fails to connect with a RPC error when run from the existing DC), should I just save time and do the MD cleanup? DCPromo /forceremoval probably won't run given then RPC errors I'm seeing on the old server!
Regards
Mike