Solved

PDC Crash, Need roadmap

Posted on 2004-08-03
7
286 Views
Last Modified: 2012-05-05
I have  Windows 2000 AD Network. My PDC hard drive fried over the weekend. I have a BDC, that is very old and slow. Things are running but when people try to access network resources it takes forever and a day. I need to know the best road map to get me "up to speed"...

1. Should I promote the BDC, install OS on the former PDC with new hard drive, , join domain, promote to backup and then promote to PDC?

or

2. Should I keep things the way they are and install the OS on the former PDC with new hard drive and promote to backup then promote to PDC?

Because there is no PDC, I am concerned that things will go to heck in a handbasket...
0
Comment
Question by:SJConsulting
[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
  • 3
  • 2
  • 2
7 Comments
 
LVL 11

Accepted Solution

by:
cfairley earned 500 total points
ID: 11705632
Option #1 sounds the best.  In W2K, there is really no promoting option, you just have to sieze the FSMO roles from the PDC (Emulator), reinstall the former PDC, join domain, run DCPROMO, make Global Catalog, and move desired FSMO roles back to the new PDC.  That's the nutshell version, I can assist further with the details.

Thanks
0
 

Author Comment

by:SJConsulting
ID: 11706085
I thought, until I read the post, that there were distinct controllers, must be thinking WinNT 4.
With that said, why can I not just install the OS, dcpromo the server and make it the PDC (emulator) ? can it be that cut and dry?
0
 

Author Comment

by:SJConsulting
ID: 11706400
Should I consider renaming the pdc to a new machine name (...pdc1) or can I name it what it was before it crashed (...pdc) ?
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 
LVL 9

Expert Comment

by:jdeclue
ID: 11707595
As you PDC is no longer available, you must seize all of the roles to your other Domain Controller before you do anything. Then you can just bring up another server, install AD and split up the roles again. All of the information you require is in the following KB article. CFairley is correct in telling you to deal with the FSMO roles, if you do not then you will have issues with your domain even after you install a new domain controller.

0
 
LVL 11

Expert Comment

by:cfairley
ID: 11707687
Sorry for the delay, I just came back from lunch.  To answer your first question: yes, it's that cut and dry if the DC does not hold any of the five FSMO roles.  To answer the second question, I would rename the new DC.  Here are some helpful articles.
 
http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2Fen%2Fwc031902%2Fwct031902.asp
http://www.is-it-true.org/nt/nt2000/atips/atips56.shtml
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B255504
0
 

Author Comment

by:SJConsulting
ID: 11708534
I am installing the OS now...I am going to run Ntdsutil.exe now and seize the FSMO and all other roles... When I am done installing the server, I am going to add it to the domain and promote it and then run ntdsutil and seize them back?

cfairley, would love to know more about the nutshell approach you spoke of earlier...I think I am on the right track...
0
 
LVL 9

Expert Comment

by:jdeclue
ID: 11714674
Those are the right steps. Before you install Active Directory to the new server, run DCDIAG.EXE on the current Domain Controller and make sure everything is working properly, heck I would run it after I use NTDSUTIL to make sure it is looking right. If there are any issues, you want to make sure they are fixed before the new DC is installed and replication begins to occur.

0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Recovering backup .Qic files on Windows 7 6 2,305
Locking down a taskpad 1 178
Can’t delete a file 14 196
Windows Services - Run a Program Grey Out 3 90
NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Adults who share images on social media aren’t the only ones who need to worry about their privacy. Our culture’s tendency to share every move and celebration affects the privacy of our children, too.
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

740 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