CoffeeBlack
asked on
AD server at remote location tombstoned
We have a ad server at a remote location which I believe became tombstoned (need to verify but its been more then 60 days so it should be), which is having trouble replicating and pc's there can not connect back in to the network now that the server is back in place.
Do I want to demote it as a AD server then readd it back in, or do I want to try to fix the tombstoning. There is one pc which is out of wack (reauthenticated to the AD server which is tombstoned, which I realize now will be a problem when I go to fix things).
It is also hosting DNS, DHCP, Printing and file serving at this location.
Do I want to demote it as a AD server then readd it back in, or do I want to try to fix the tombstoning. There is one pc which is out of wack (reauthenticated to the AD server which is tombstoned, which I realize now will be a problem when I go to fix things).
It is also hosting DNS, DHCP, Printing and file serving at this location.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Will I need to remove the server from sites and services as well from the other side, before re-promoting it?
Yes delete it out of sites and services.
Thanks
Mike
Thanks
Mike
ASKER
dcdiag /v /c /d /e /s:mysrvr >d:\data_files\it\dcdiag.t
dnslint /ad /s "myipaddress"
script ftw...
But yea it looks bad, hasn't replicated in 80 days, the server itself was down and not at all a high priority, and folks were just connecting over the vpn connection. There's a little more to the story...but doesn't really matter at this point now that we're able to bring it back up.