Answered by:

Server 2012 sysvol broken, req easy fix

Question

I have 2 server 2012 domain controllers DC01 & DC02 AD replication between them works fine accept for sysvol folder they did initially sync but for some strange reason has stopped, I have reserched online to find a solution but its seem this is a potential
"land mine" to repair, I have pretty much determined the problem is on my DC02 box as i also setup a test only DC03 box this week and AD replication including sysvol works great between it and DC01.

I just want to find the easiest solution to fix my broken DC i don't want to spend hours performing complex repair procedures from information found in online posts that may not even be related to my problem, there is so much confusing information out there
in posts on this topic, half of which are related older server OS's like server 2008, im thinking there must be an easier way that i can maybe just remove/delete/demote/recreate/repromote or similar my damaged DC02 box without upsetting AD ?

Answers

The diagnosis would take hours of examining the data. It may be simple fix or may be complex root cause analysis, without data , it would be hard to estimate time.

Please run dcdiag /v and paste the output .

Also paste any event id error information.

You wouldn't upset the domain controller , provided the DC is only the single source of communication to your clients / apps . In that case you can safely bring additional domain controller , migrate the roles , point the clients to new DNS server and
demote the dc2. but if there are any applications with hardcoded Domain controller IP address, you might need to change them.

All replies

The diagnosis would take hours of examining the data. It may be simple fix or may be complex root cause analysis, without data , it would be hard to estimate time.

Please run dcdiag /v and paste the output .

Also paste any event id error information.

You wouldn't upset the domain controller , provided the DC is only the single source of communication to your clients / apps . In that case you can safely bring additional domain controller , migrate the roles , point the clients to new DNS server and
demote the dc2. but if there are any applications with hardcoded Domain controller IP address, you might need to change them.

Basically I wish to rebuild the my damaged DC02 box I don't really wish to mess around with diagnostics and trying to repair it as i have spend much time already and even sort 3rd party opinion from an IT consultant who was not able to offer definitive answer
on how to repair it just a "try this try that" type of solution , my goal is to start fresh with this DC and rebuild it from new or at lease demote it as a DC remove all the roles and then re add the roles and then re-promote it , I am thinking of following
the simple steps outlined here http://terrytlslau.tls1.cc/2012/03/domain-controller-demotion-on-windows.html and then re promote the same box with the same name back again ?

Will demoting the box remove its entries from AD and then allow me to re-promote it back again using the same name ?

I guess could just remove DC02 from the network and just run my DC01 and "DC03 test" boxes but i dont really want to do this as DC03 was only introduced as a test box to see if i could get it to replicate with DC01 and hence revile to me if DC02 was the
source of my replication problem "my test confirmed this".

I am unsure if demoting DC02, removing its server roles then re installing these roles and re-promoting back as a DC with the name same name of "DC02" will upset AD ? I have not performed such an operation in a network before and I fear such actions may
mess up AD in someway because i will be using the same domain controller name of DC02 ?

You are right that KB I provided is applied to Windows Server 2000 and Windows Server 2003.

In some similar threads, a sysvol restore using Burflags is able to fix FRS replication problem even on the machines where Operation Systems are not Windows Server 2000 or Windows Server 2003. Please refer to the links below:

You are right that KB I provided is applied to Windows Server 2000 and Windows Server 2003.

In some similar threads, a sysvol restore using Burflags is able to fix FRS replication problem even on the machines where Operation Systems are not Windows Server 2000 or Windows Server 2003. Please refer to the links below:

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.