[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


FSMO fails

Posted on 2005-05-13
Medium Priority
Last Modified: 2008-02-01
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
Question by:bbirdrt
  • 2
LVL 20

Accepted Solution

mkbean earned 2000 total points
ID: 14001263
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.


LVL 20

Expert Comment

ID: 14226318
Agreed.  ;-)


Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Downtime reduced, data recovered by utilizing an Experts Exchange Business Account Challenge The United States Marine Corps employs more than 200,000 active-duty Marines with operations in four continents, all requiring complex networking system…
This is the first one of a series of articles I’ll be writing to address technical issues that are always referred to as network problems. The network boundaries have changed, therefore having an understanding of how each piece in the network  puzzl…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Screencast - Getting to Know the Pipeline

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question