OmegaKzoo
asked on
Domain Controller Issue Continued
I am still working on cleaning up the problem from my question at:
https://www.experts-exchange.com/questions/28315178/Domain-Controller-Problems.html
We had a DC on a virtual machine go down. One of my co-workers stood up an old backup to take its place. This caused all sorts of problems. We believe we have gotten most of this mess cleaned up, but are still experiencing sporadic issues with DNS. Mapped drives not working until we remap them, issues getting to the print server by DNS, problems with DNS getting to Sharepoint (when we attempt to connect by IP it works, and when I manually map in host files on user laptops it works).
Another of my coworkers gracefully decomm'd the DC that was brought back up and ran the NTDSutil.exe to get rid of metadata.
The problem I am seeing, is we are still having issues with sharepoint. We have verified that none of these users are pointed to the decomm'd DC, DHCP is not giving it out as a DNS server anymore, and I do not see it anywhere in DNS anymore. When I run DCDiag.exe however, I still get a bunch of replication errors between the decomm'd server and the new PDC. I was wondering how I would go about cleaning that up, so that it doesn't try and replicate to that anymore. Also, I was wondering how else I might be able to find any other remnants of that server on my network?
https://www.experts-exchange.com/questions/28315178/Domain-Controller-Problems.html
We had a DC on a virtual machine go down. One of my co-workers stood up an old backup to take its place. This caused all sorts of problems. We believe we have gotten most of this mess cleaned up, but are still experiencing sporadic issues with DNS. Mapped drives not working until we remap them, issues getting to the print server by DNS, problems with DNS getting to Sharepoint (when we attempt to connect by IP it works, and when I manually map in host files on user laptops it works).
Another of my coworkers gracefully decomm'd the DC that was brought back up and ran the NTDSutil.exe to get rid of metadata.
The problem I am seeing, is we are still having issues with sharepoint. We have verified that none of these users are pointed to the decomm'd DC, DHCP is not giving it out as a DNS server anymore, and I do not see it anywhere in DNS anymore. When I run DCDiag.exe however, I still get a bunch of replication errors between the decomm'd server and the new PDC. I was wondering how I would go about cleaning that up, so that it doesn't try and replicate to that anymore. Also, I was wondering how else I might be able to find any other remnants of that server on my network?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for OmegaKzoo's comment #a39861814
Assisted answer: 500 points for SagiEDoc's comment #a39852495
for the following reason:
After removing the piece that was lingering in Sites and Services the issues appear to have disappeared. Thanks
Accepted answer: 0 points for OmegaKzoo's comment #a39861814
Assisted answer: 500 points for SagiEDoc's comment #a39852495
for the following reason:
After removing the piece that was lingering in Sites and Services the issues appear to have disappeared. Thanks
ASKER
Thanks for the advice.