Discussion Locked

Installing a BDC and promoting it to PDC

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I think this will be a challenge but I hope that somebody will help me:

I am administering a network with only one server - PDC (quite unstable!!!),
running NT4 BackOffice. Unfortunately I have no information about recent
upgrades (apart from Service Pack 5 & antivirus software) or patches
installed. I have to install another server that will replace the existing
PDC. There are two things that make my task difficult:

1) I haven't got enough info about the setup and configuration ofthe server
and all the BackOffice programs;

2) I have only one week to gather all the info;

3) I have never done this operation before...

My initial plan is :

1. Installing the new server as a BDC - (will the replication of user data
start automatically?)

2. Promoting the BDC to PDC (hopefully the first PDC will gracefully become
a BDC...)

I would appreciate any comments, advice, hints, tips, checklists, web links
... or anything you can think of.

Many, many thanks

ict_support@supanet.com

5 replies

by bart777

You have it.... One thing you might want to do is let the PDC replicate a few times to the new BDC before you promote the new one..

It sounds like this will be the easy part though. after you have finished the upgrade you can then do the troubleshooting you need on the old server.. If it is giving you a lot of problems you might consider juset rebuilding it from the ground up as a BDC and Back Office server.

Best of Luck,
Bart

by kent.manley

Here's a couple more things you can do:

1) make a current ERD
2) from a command prompt run 'net start' (that will tell you what services are running, so you know what to duplicate on your bdc)
3) make an ERD on your bdc when you get it up and running.
4) look in technet for methods to move dhcp/wins/dns (if you have those services running on your current pdc and need to move them to your new server).
5) check to make sure you don't have any trusts established (it should not matter when you stand up the new controller, however, you do want to know these things).
6) Look for shared directories (file server), shared printers (print server), RAS services/modems (RAS server), and IIS (web server). All these things need to be taken intoaccount as you prepare to migrate services off (if that's the plan).

Finally, make a backup of your original server before you begin any work.

Hope this helps.

Kent

This discussion is closed to new replies.