Re: New DC not sharing sysvol after dcpromo in domain with 1 other unhealthy dc

Home Forums Microsoft Networking and Management Services Active Directory New DC not sharing sysvol after dcpromo in domain with 1 other unhealthy dc Re: New DC not sharing sysvol after dcpromo in domain with 1 other unhealthy dc


tripoli
Member
#334788

Re: New DC not sharing sysvol after dcpromo in domain with 1 other unhealthy dc

gepeto;112692 wrote:
I assume the DNS is running on the old broken DC?

Primary zone?

If you logon to it can you see the proper srv records etc?

DNS is running on the broken DC.
I can see the srv records. When the new computer was promoted, it added all it’s dns records, and the broken dc’s records matched. That’s one reason I feel comfortable that I was able to rebuild the DNS for the broken computer OK.

Primary Zone?

jasonboche;112785 wrote:
It’s a little late now but the gold rule is to ensure your domain environment is healthy before adding/removing domain controllers. This means ensuring replication is working properly. Adding a “fresh new” DC to rescue the situation because your old DC is fubar will only compound the problem.

Time for you to dig out the replication monitor utility (on the server 2003 cd, tools folder) to look under the hood and see what the problem is. I’ve got a KB article or two from Microsoft that is real good at walking one through replication issules. If you get stuck, let me know and I’ll dig up the KB article for you.

I would also check Active Directory Sites and Services and make sure the KCC has accurately set up replication partners between all DCs.

Jas

Sites and services replication partners was OK when I had two DC’s (i un-promoted the new computer untill I get this solved)

I will dig up that monitor….