The current operations master is offline. The role cannot be transferred (Windows 2008)

Hi,

I had a time sync issue with my primary DC. Now I have shut it down and left 1 over.
I want to transfer roles but it says it cannot because it is not online ...

operations master
Note: if I try to sync from a different dc, I get "The target principle name is incorrect", the server holds all the fsmo roles ...

Please advise.
J.
janhoedtAsked:
Who is Participating?
 
GeodashCommented:
Seize the FSMO roles first

Use dcpromo /forceremoval second

Directly perform metadata cleanup by removing the server completely from the network
third (if needed) using ADSIedit - only needed if the /forceremoval is not successful.

If the DC is tombstoned and it holds an FSMO role anyway, your domain has been operating without that role for this long. By Default, in 2008, a DC is not tombstoned until 180 days...yikes!
0
 
GeodashCommented:
Try transferring from the command line - using ntdsutil.exe, see if you get the same error. Look at the bottom of this article

http://www.petri.co.il/transferring_fsmo_roles.htm
0
 
janhoedtAuthor Commented:
Would like to get it online instead of seizing.
When I try to sync ad I get "The target principle name is incorrect".
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.

 
GeodashCommented:
Do you know what Server holds the role?

Run a

netdom -query fsmo

from command and see if that server is online. Try to ping it etc.
0
 
janhoedtAuthor Commented:
I can logon to it and wirk without problems. Only sync does not work + not reachable when I want to transfer fe rid role.
0
 
GeodashCommented:
use repadmin to check the status of the server and its replication - check out this article

http://technet.microsoft.com/en-us/library/cc770963%28v=ws.10%29.aspx
0
 
janhoedtAuthor Commented:
Same output: target principle name is incorrect.
0
 
GeodashCommented:
So are all of the FSMO roles on one server? Can you reboot the server to see if it clears it up? Have you looked in the event log and post any erros that are listed there?
0
 
janhoedtAuthor Commented:
http://support.microsoft.com/kb/288167

What I get:
The machine account password for the local machine could not be reset.
Logon Failure: The target account name is incorrect.
0
 
janhoedtAuthor Commented:
Ah, it did work now.
But now different message:tombstone
0
 
GeodashCommented:
ahhhh, so the DC has been offline so long it was tombstoned. That's a different story. So its a little trickier now.

http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/65414b37-d1ed-4f20-ae80-4effd9793eab/
0
 
janhoedtAuthor Commented:
If I do a  dcpromo /forceremoval won't it cause problems since not all roles are seized?
Some roles should still be transferred and are not.
0
 
GeodashCommented:
The only way I know how do recover from a Tombstoned DC is seize the roles. Do you have another DC on the network that you can do this from? If the DC needs to be back on the network, seize it to the other DC temprarily, run a dcpromo /forceremoval and then dcpromo it again to promote it back to a DC. You may have metadata to clean up though after doing the /forceremoval
0
 
GeodashCommented:
0
 
janhoedtAuthor Commented:
Ok, I only want to know: if I do a dcpromo /forceremoval, won't I loose the possibility to recover the roles?
0
 
janhoedtAuthor Commented:
Seized all roles, dcpromo force remove and dcpromo again.
Everyth worked fine again so didn t do cleanup.
0
 
GeodashCommented:
Great...it is all working again now?
0
 
janhoedtAuthor Commented:
Yes. 2 things more:
-don t get it why my dc s time was suddenly total out of sync
-i ve set tombstone to 50 year, :-) yes indeed 50 year since in my lab I have machines I want to boot "one day" and keep membersh of domain
0
 
GeodashCommented:
The DC that you just promoted or the original one that has been online?

In a test environment, I do not see that being an issue. In production, I would not recommend 50 years.

Per MS
To increase tombstoneLifetime in big infrastructures, there is only one valid solution:

    make sure that garbage collection will not run instantly after you changed the attribute, then after changing the attribute force replication and make sure it’s replicated everywhere

You can read about it here -

https://msmvps.com/blogs/ulfbsimonweidner/archive/2010/02/10/adjusting-the-tombstone-lifetime.aspx
0
 
janhoedtAuthor Commented:
Is the tombstone per dc? I thought it was for the full domain(??)
Garbage collection ...? Replication is running default at regular times so I don't see why I should worry, even with tombstone of 50 years ...
0
 
GeodashCommented:
I agree. Like I said, I wouldn't worry about it being a test. You should not have any issues.
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.