Active Directory File Replication Issue

We have 4 domain controllers. Three are running on hyper-v virtual machines and one is physical. I want to get rid of the physical AD server, but keep getting a file replication error on it. This one server is the only one with this error and it is the only service getting an error on the machine. The event viewer id numbers for the error are 13552 and 13555. Since I want to get rid of this server any way, can I just demote it, remove AD, then shut it down or do I need to resolve the file replication issue first?

Thank you
Matt GAsked:
Who is Participating?
 
Jose Gabriel Ortega CEE Solution Guide - CEO Faru Bonon ITCommented:
Not at all matt, just proceed with the removal and that's it.

Jose.
0
 
MaheshArchitectCommented:
What's version of server?
0
 
Matt GAuthor Commented:
Windows server 2012 r2
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
MaheshArchitectCommented:
So that u must be having 2012 R2 version of hyper-v along with 2012 R2 dcs

so it's don't have any issues to have all DC's on virtual platform
in previous version of dc and hyper-v, there is issue of USN ROLLBACK
0
 
Matt GAuthor Commented:
Correct! 3 virtual 2012 r2 domain controllers and one 2012 r2 physical. The physical one was left in place knowing down the line it would be removed and just use virtual. Then the error started and wasn't sure if I needed to go through the steps to fix the error only to turn around and remove it or could it just be demoted and removed.
0
 
MaheshArchitectCommented:
Before demotion, you need to ensure that all dependencies are addressed on physical DC
0
 
Matt GAuthor Commented:
I put this physical domain controller in after I had the 3 virtual one's running. I wanted to make sure everything was good with virtual and this one was setup afterward. It isn't doing anything other than AD. The Roles, etc.. are on the virtual domain controllers.
0
 
MaheshArchitectCommented:
Then remove it gracefully
if failed remove forcefully
0
 
Matt GAuthor Commented:
Thank you for your help and feedback. Appreciate it!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.