journal wrap error question
Posted on 2015-01-18
I am in the process of migrating a windows 2003 DC to a new Windows 2012 server. I have joined the new server to the domain, updated the domain and forest level, promoted it to a DC, and transferred the FSMO roles from the old 2003 server to the new 2012. I also did a dc diag on the old 2003 server before starting and everything was healthy. Sysvol an and AD replicated fine. there were no journal wrap errors. That was several weeks ago. Now the Win 2003 server is having major issue and is shutting down at least once a week.
I got an alert that the 2003 server was getting journal wrap errors.
My question is: Can I just demote and shut down the old DC or do I have to fix the journal wrap errors first?
and if I do, do I run the burflags (4) on the new 2012 server as I want it to be authoriative or do I have to run something on the old 2003 server? I can send over event log if needed.