Avatar of Silly013
Silly013 asked on

Domain Upgrade (2000 - 2003)

I have a single domain runing on Windows 2000 Servers and a Exchange 2003 server.  There are two domain controllers, one holds all of the FSMO roles - and the other one is just there for redundancy.  We just purchase a couple of new servers and I'd like to switch out the two domain controllers.  I'd like the new servers to run Windows Server 2008.  Could you please give me some insight of what needs to be done so that the domain controllers can be switched out without any interruption to users, as far as them being able to access their e-mails, logon, etc.

Thanks.
Windows Server 2008Active DirectoryExchange

Avatar of undefined
Last Comment
Silly013

8/22/2022 - Mon
jakirkhan

ASKER CERTIFIED SOLUTION
Mike Kline

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
NoodlesWIU

I'm assuming the FSMO roles are on the non exchange server.  Add your 3rd sever and make it a DC using dcpromo, transfer the FSMO roles, then demote the old DC.  You are now halfway there.  You have two options at this point, either do a swing migration creating a second exchange server and migrating the mailboxes so there is no downtime then going through the process of removing the old exchange server.  but doing this you have to have a different server name for your new mail server than what you previously had.  

If you can afford a little down time you can demote the exchange server if this was a DC cut access to your mail server at night and perform an NTBACKUP of the exchange database if its not being used for anything other than a mail server.  Then take it off the network, reset the computer account in AD for the exchange server, then build the new os with the old Exchange name, and perform an exchange install in /disasterrecovery mode  

take a look at some of the Exchange 2003 ntbackup guides out there.  Personally I like to keep the same mail server name.  I've done this method for a few clients when converting their mail server into a virtual enviornment because their mail server is usually pretty gummed up with other non exchange related errors when I prefer a clean OS.
ASKER
Silly013

@jakirkhan | mkline71 | dariusg | NoodlesWIU - I really appreciate your quick responses.  Please give me a day or so to consume the materials, run some tests and I'll get back to you.

Just to clarify some of the questions:
- Yes, I'm thinking of Windows 2008 R2
- Yes, FSMO roles are all on one DC and it's not an Exchange server.  I'm thinking of doing a swing migration of Exchange as we do have new servers for it

I only have you experts as my supports, so please do give some time for me to sort these out and go through the process.  Thanks.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
Darius Ghassem

Not a problem just let us know
ASKER
Silly013

... still working on this, just want to let you all know.
ASKER
Silly013

The upgrade went through successfully.  Thanks.  If you have any questions on the point
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.