JSEE18
asked on
Replication issue - temp fix possible?
I've got a secondary DC in a remote office which hasn't replicated in ages and I think is tombstoned. Other member servers are occasionally having the dreaded "The Trust relationship between this workstation and the domain failed" message on RDP login. - causing system downtime while I de-join/rejoin to get people working again. I'm assuming this has to do with the long-failed replication on the remote server. I've seen in other articles that reformatting the server is the quickest way to restore health to the domain but I am unable to get to the location for several weeks due to other commitments.
Is there a stop-gap measure or workaround to stop this awful "Trust relationship failed..." error? The dejoin/rejoin works for maybe a day.
Could I simply shut down the non-replicating server in the meantime or would this cause additional problems - the remote machines could authenticate across the VPN to the PDC...
Thanks
Is there a stop-gap measure or workaround to stop this awful "Trust relationship failed..." error? The dejoin/rejoin works for maybe a day.
Could I simply shut down the non-replicating server in the meantime or would this cause additional problems - the remote machines could authenticate across the VPN to the PDC...
Thanks
reinstall this
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Dorothy to add that if for some reason you are unable to gracefully remove Active Directory run DCPROMO /forceremoval then do a METADATA cleanup to remove it from Active Directory as per: http://www.petri.co.il/delete_failed_dcs_from_ad.htm
Hopefully it doesn't have any FSMObroles? If so that makes it more complicated.
Hopefully it doesn't have any FSMObroles? If so that makes it more complicated.
FSMObroles= FSMO roles