Solved

Seizing FSMO roles

Posted on 2012-04-12
4
514 Views
Last Modified: 2012-04-30
Hi, I am working with a company that had a migration done about 5 months ago and im logging errors: nETLOGON 5719.  I believe its related to the server fsmo roles that they did NOT transfer over when they did the migration. A command: netdom query fsmo gives my all roles pointing to old server.  This is a one server (server 2008 std ) environment with about 12 clients no  exchange (pop), setup as a dc, but with no roles.  Even thought everything runs fine on the network.  Should I seize the master roles using the Ntdsutil.exe as described here?

http://technet.microsoft.com/en-us/library/cc816779(v=ws.10).aspx


Thanks,
0
Comment
Question by:communitypc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 17

Expert Comment

by:Anuroopsundd
ID: 37838885
Yes, as the FSMO roles server does not exist.. you do seize them...
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 37838889
Yes - that's exactly what you should do if the old sever with the FSMO roles is not going to come back into play.
0
 
LVL 57

Expert Comment

by:Mike Kline
ID: 37838912
In addition please try and get a second DC up when you can.  You are playing with fire there, if that one DC goes down hard then you will definitely have an outage.  Have a second DC and users shouldn't notice.

Thanks

Mike
0
 
LVL 6

Accepted Solution

by:
sconstable earned 500 total points
ID: 37838956
You shoudl also check for any metadata that should be cleaned up, chances are if they never traferred the FSMO roles they didnt sucessfully dcpromo the old DCs and there is probably still metadata from old DCs the in the AD.

I would do things in the following order:

1. Seize FSMO roles
2. Check all replications
     Run : repadmin /replsummary
     The replication summary may show non-existing servers, if it does, this will indicate a need to run metadata cleanup.  Also, If you see any errors on the DCs that you know exist, you should attempt to resolve the erroors before going on.

3. Clean up metadata.
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

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

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…

707 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