Initially had 2 servers - A and B. Server A was taken down permanently a few weeks ago. Now seeing errors in Server B logged as Event ID 2092- NTDS Replication outlining FSMO roles not seized.

How do I seize these roles as well as stop the replication?
Who is Participating?
mcsweenConnect With a Mentor Sr. Network AdministratorCommented:
Open AD Users and Computers
RC the domain and select Operations Masters
Click on Each tab and click Change to seize the role
Start, run, mmc
File, Add/Remove Snap-in
Active Directory Schema, Add, OK
RC on AD Schema and select Operations Master
Click Change Button
Open AD Domains and Trusts
RC AD Domains and Trusts and select Operations Master
Click Change
(Clean up MetaData)
Open command prompt while logged in as enterprise admin
metadata cleanup
remove selected server DEADSERVERNAME

Open in new window

TomislavjConnect With a Mentor System AdminCommented:
well, you could try these methods for start

also, what does dcdiag says?
renniscomAuthor Commented:
First of all, my apologies for replying over 48hrs later.

Before attempting to seize any roles, I double checked the FSMO role holder via GUI - all roles are held by the correct server. I believe the issue is that it continues to attempt to replicate with a now non-existent server
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.