Exchange Migration
Exchange Migration
Gareth Gudger
With Exchange 2003 going end of life in less than two weeks, I have had a significant influx of
lastminute migrations and migration questions.
You may be able to find a consultant that can help with Exchange 2003 for years to come. Keep in
mind, that finding someone with that knowledge and skillset will diminish over time.
Real World: A couple of years ago I helped a friend with a failed Exchange 5.5 box. Yes, that is not a
typo. We were able to get it operational. The miracle is that I remembered a best-kept secret from
5.5 to get it going. These were things I hadn't thought about in 12 years!! I truly shocked myself.
The larger concern, however, is the complete lack of updates. If an exploit were to be found in the
product, after April 8th, you are on your own.
"Seventy-five?" you might say, "Isn't that the max number of users for Small Business
Server 2003?"
Yes, yes it is.
I will be focusing on a small company running Exchange 2003 Standard. While this will focus on
the full version of the product, you can easily transpose this for Small
Business Server.
https://www.printfriendly.com/p/g/xYHqav
8/26/2021 Migrating Exchange 2003 to 2010 — Part I
-
We will focus on transitioning from a single server running Exchange 2003 to a single
server running 2010. We will use a Cisco ASA 5505 as our firewall. Our network will
look like this.
Microsoft has not released an upgrade path from 2003 to 2013. If your final goal is to
get to Exchange 2013, Microsoft recommends you go to 2007, or, 2010 first. Exchange
2003 and 2013 cannot co-exist in the same forest.
Tip: Now you can cheat, and use products like MigrationWiz, to perform what they call
a cross-forest migration. And it will get you directly to Exchange 2013. But that is
exactly what you will get. A brand new forest and a brand new domain. And that
comes with its own set of challenges. Don't get me wrong, MigrationWiz is a fantastic
product. In fact, keep your eyes peeled for an article in April that covers transferring
mailboxes from Lotus Notes to Exchange 2010 using MigrationWiz. But for now, let's
follow Microsoft best practice.
First things first. The prerequisites. We need to do this before we even consider putting
in the Exchange DVD.
8/26/2021 Migrating Exchange 2003 to 2010 — Part I
https://hm,w.' printfriendly.com/p/g/xYHqav
Before we can get started we need to do some checking in of
Active Directory and the current Exchange environment.
4. Click Ok.
Note: You can NOT do this if you have any Server 2000 (or
older) domain controllers in the environment. Those will
need to be upgraded or decommissioned first.
6. You will be prompted to confirm and wamed the action is irreversible. Click Ok.
7. You will receive a dialog determining whether or not this was successful. Click Ok.
8. TO confirm this worked, right-click on your domain and select Raise Domain
Functional Level again. It should look like the screenshot below. Click Close.
Next, we need to determine the forest functional level.
Like we did with the domain level, we need to make sure
this is a minimum of Server 2003.
Note: If you have more than one domain in your forest, all
domains must be at a Server 2003 domain functional level
before the forest functional level can be raised.
Click Ok.
7. To confirm this worked, right-dick on
the top-level node and select Raise
Forest Functional Level
again. It should look like the
screenshot below. Click Close.
2 Go to Start, right-click on My
Computer and select Properties.
3. Under the General tab, in the System section,
look for a Service Pack level.
4. Repeat this for all domain controllers.
https://docs.microsoft.com/enus/previous-versions/office/exchange-server2010/
dd346700(v=exchg.141 )
That's all for Part l. In the next part in our series we will extend the Active
Directory Schema to allow for Exchange 2010 and begin preparing our server that
will host all our Exchange roles.