• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 814
  • Last Modified:

FSMO fails

I have my first DC (dcl-dc01) failing. I also changed my network topology. The original network topology had dcl-dc01 as a hub to 7 other sites, who were going to the internet. All site DC's are global catalogs.  I have now made another site the hub to those other sites connected via point-to-point T1 lines. I want my new site DC (gaith-dc01) to hold the fsmo roles permanently. I have attempted to transfer those roles to gaith-dc01. They have all failed, with different errors:

1. the domain controller could not be set. the server is not operational. When trying to connect to gaith-dc01 from dcl-dc01.


2. the requested fsmo operation failed. the current fsmo holder could not be contacted.. This occurs after I successfully connected to gaith-dc01 from dcl-dc01 and cllick CHANGE on the operation master window.

From all I have read, it appears that; 1. Although dcl-dc01 hasn't  crashed or failed completely something is wrong. Somehow this dc only got a 4gb partition when initially configured and I am getting low hd space errors in the event viewer; 2. That the dc I transfer these roles to should be in the same site subnet; 3. Since the transfer won't work I MUST seize t he roles if I want them at another site.

If the answer to 2, is correct. How can I get the FSMO roles to gaith-dc01, or in your opinion do I really need to???? Also, if all roles are seized some need to be transfered back to the original dc, or am reading that wrong.

Thanks for your help ahead of time. I Google alot and your site always comes up with answers. I decided to try you out with a month subscription. Hope you can help.


Bill Bird
  • 2
1 Solution
BrianIT ManagerCommented:
Hi bbirdrt,

Well I think you made a wise decision to try out EE.  It is a great service.

Sounds to me like you need to seize those roles off of that server and then decommission that server.  Once you seize a role you should never bring the older server back online.  You can and should just reinstall it (perhaps even use a different name) and let it be a new server or DC.

Here is a link to my site where I have collected several other links about FSMO servers and moving their roles.  From what it sounds like you will want to look at the last link.  Remember you don't want to transfer, you want to seize.  You might also want to look at the 2nd link to make sure your FSMO roles are located correctly.


BrianIT ManagerCommented:
Agreed.  ;-)

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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now