Reformatting and resintsalling on existing domain controller and exchange server

I have 2000 server domain controller which also hosts exchange 2000. It's in horrible shape, and is creating a lot of authentication problems for users.

I want to reformat it, add some extra scsi drives with another raid array to separate exchange from the OS drives. So what I'm figuring is the following, and I'm hoping for some input on ways to do this better or more efficiently.

1. Bring in another server install ad and exchange set it up to replicate with the PDC.

2. Once everything is replicated from AD and the Exchange Public folers, move the mailboxes over to the new server, and make the new server the pdc.
     a. I then have to take down the original pdc, and change the ip address of the new server to the ip of the old one. (is that going to be a problem?) It's at this point users will actually connect to it.

3. Reformat and reinstall everything on the old PDC. (AD and Exchange).

4. Set up replication again and once AD and public folders are replicated make the old PDC the PDC again, and move exchange mailboxes over to it. Change the IP again and pray that everything works.

Is that about right? Am I missing anything noteworthy? Thanks.
Who is Participating?
You should check this one, too. Global Catalogs are required to service logon requests. You must have one, but you can have as many as you want...

How To Create or Move a Global Catalog in Windows 2000;en-us;313994
You're missing a lot of noteworthy things, but you also sound like you know what you're talking about, so it's hard to tell. There is no pdc in W2000 - there are FSMO roles, and one of them is a PDC emulator, but that's for NT4 BDCs that are still active.

The AD part is pretty straight forward. The exchange part requires some care with Public folders mostly... You're going to do it twice, too, so double the chances of a missed item.

try this:

There's more info all over the place, but like i said, you've got a clear idea already....

newimagentAuthor Commented:
Well I have a lot of experience in setting up ad and exchange in 2000 and server 2003, but all of my work is small businesses, so I don't get into multiple servers or replication very much. I've thought of a couple questions since reading your post.

Thanks for the link, a lot of well organized info in there. I am unfamiliar with one portion of that list:

Transfer the 5 FSMO roles to the new server. If you don’t know what a FSMO is and have no idea why anyone would want 5 of the suckers, we’d like to recommend this book to you for future reading: Windows 2000 Essential Reference. The RID, Infrastructure and PDC FSMO roles are changed in Active Directory Users and Computers. The Domain Naming Master is changed in Active Directory Domains and Trusts and the Schema FSMO is changed in Active Directory Schema. If Active Directory Schema is not available, you must install the Windows 2000 Administration Tools from the Windows 2000 Server compact disc and add it to an MMC console.

Could you give me an explanation of what these are and how I go about transferring them? Thanks.
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Oooh I hate that when you've typed half a message, then click the close button without thinking...

The FSMO roles control additions, changes and deletions to the domain users, computers and schema. You can only have one of each role, but more than one role can be on a machine. Roles can be transfered gracefully, or sieze if a machine has died. A Dead machine can Never be brought back up as a domain controller. This doesn't affect you, as you're going to do a graceful transfer...

Windows 2000 Active Directory FSMO Roles;EN-US;197132

Flexible Single Master Operation Transfer and Seizure Process;en-us;223787&Product=win2000
newimagentAuthor Commented:
Thanks for the links they helped a lot.

I have a question, I've now started this project and I came across something that has me a bit puzzled.

Remember exchange 2000 is installed on both domain controllers

the original domain controller I thought was ready to be made a non global catalog server so all requests could be handled by the new server I put up. When I unchecked the GC box in sites and services and when I rebooted exchange wouldn't start. from my understanding the two should really have nothing to do with each other especially since there is another GC handling requests. can anyone tell me why this is happening? If I make the server a GC again exchange works normally.
newimagentAuthor Commented:
thanks for the help you're links caught some things that I missed.
Sorry for net getting back to you re your 9 Oct - I honestly didn't see it.

Did you get by it? If so, how?

thx for the points.
newimagentAuthor Commented:
well as it turns out when you install exchange on a domain controller thats a GC exchange will only operate if it can talk to that server. So even though there was another GC exchange wouldn't talk to it. this is the biggest problem with dropping exchange on an AD box. Basically I moved all the mailboxes, set up replication of the public folders and specific system folders, uninstalled exchange from old server, then uninstalled AD. Then did all of that over again after I reformatted the machine. Everything is working great now.
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.