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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jose Gabriel Ortega CastroCEOCommented:
Not at all matt, just proceed with the removal and that's it.

Jose.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MaheshArchitectCommented:
What's version of server?
0
Matt GAuthor Commented:
Windows server 2012 r2
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.