Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

siezing roles from a 2003 server that died

Posted on 2015-02-21
4
Medium Priority
?
140 Views
Last Modified: 2015-02-24
I have a 2003 server that died and a 2008 server both were domain controllers.  The 2003 domain controller was the primary and it died.  Is there any way I can sieze the roles for the 2008 server?
0
Comment
Question by:WellingtonIS
[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 53

Accepted Solution

by:
Will Szymkowski earned 1000 total points
ID: 40623320
You can Seize the roles to the 2008 domain controller. The below link will illustrate all of the steps. You will also need to confgiure an external time source for your 2008 domain controller as well.
Seize Roles
http://support.microsoft.com/KB/255504

Configure External time source
http://support.microsoft.com/kb/816042

Use the below commands to ensure replication is working after you seize the roles and perform metadata cleanup.
repadmin /replsum
repadmin /showrepl
repadmin /bridgeheads

dcdiag /v

Also once you have Seized the roles, cleaned up the metadata and configure the external time source, you will also need to make sure that you update your clients (DHCP) and static addresses to point online to the 2008 DC for DNS.

Also another key area you need to check is the SRV records under the _msdcs.domain.com zone for your active directory integrated zones. Go through the folders and make sure that there are no references back to your 2003 domain controller. If there are delete them.

Check Sites and Services as well.

Once you have completed all of the above and everything is cleaned up introduce another domain controller so that you have redundancy.

Will.
0
 
LVL 16

Expert Comment

by:cantoris
ID: 40623345
and after seizing roles, never bring the dead machine back onto the network
0
 
LVL 79

Assisted Solution

by:arnold
arnold earned 1000 total points
ID: 40623371
after seizing roles the same machine with the prior configuration can not be rough online. A reinstalled OS system with the same name can be readded after the ad metadata has been cleaned up.

You would need to use the command ntdsutil to seize the roles.

A second DC should be added as soon as possible.
0
 

Author Closing Comment

by:WellingtonIS
ID: 40628634
Thanks I did all of that. It did the trick.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Group policies can be applied selectively to specific devices with the help of groups. Utilising this, it is possible to phase-in group policies, over a period of time, by randomly adding non-members user or computers at a set interval, to a group f…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

670 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