Setting my foundation to migrate from 2003 to 2007 - Your advise pls

[southbeach]

I have just received my new Exch 2007 media. I have been asked to migrate from 2003 to 2007 ASAP. I have very little experience, respect but do not fear the challenge before me and I am eager to learn as much as possible.

That said, I cannot afford to learn at the company's expense, I mean, by bringing the exchange server down.

I have
(1) Exchange 2003 Server
(1) MySQL, Apache and PHP Server (web stuff)
(2) DNS servers - w/ Active Directory
(1) File Share Server - running W2000
(1) Printer Server - running XP
(1) Server available for Exchange 2007

I wonder if I should:
(a) Install Exch 2007 on server while on network?
(b) Install Exch 2007 off line?
(c) How does one go about running migration tests?

I have printed and will start reading through a number of articles I found online. My posting of this question is part of my data gathering to prepare myself for what I know lies ahead.

Thank you in advance for your assistance!

 

[58sniper]

a) You have to
b) you can't
c) virtualize a lab and duplicate your environment in it

You need an Exchange design, an implementation and migration plan, a backout plan, and a lab to test in.

That said, I cannot afford to learn at the company's expense, I mean, by bringing the exchange server down.

No offense, but you, and your company, are in for a rude awakening. You can certainly migrate with little downtime, but it requires a lot of homework and testing. Based on the questions you're asking, I somewhat doubt that will happen without an external consultant.

Pat Richard MVP

 

[southbeach]

58sniper,

No offense taken. I will be the 1st one to admit it and humbly expose my ignorance on the subject.

I am a developer by trade. I have spent the last 20 years writing accounting applications. I am now, don't ask how it happened, a Sys Admin, Network Admin, Exchange Admin, Web Developer, SQL Admin, VoIP Admin, etc.

I do not mind stepping into new grounds, but knowing how bad things can go. This is why they say you cannot teach an old dog new tricks, being aware makes us afraid.

Hope this is a case where fear is a good thing!

Thanks,

 

[Davetoo]

You need to install and configure the Exchange 2007 on it's own, new, server (it has to be on an x64 OS). You can do that without effecting your current Exchanger environment (I just did it). Once you have the 2007 box up and running and tested out fully, then you can, at your leisure, begin migrating your users to the new box (bearing in mind they have to have at least Outlook 2003 (I believe) to work...I do know that Outlook 2000 won't).

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[theravager]

I would be going and doing a course on 2007. There is a lot of things involved in the migration and if you can't afford a consultant to do the design i would be definately doing a lot of training first.

 

[NJForensics]

Southbeach...

There are several major considerations for your task. Specifically, google some MSExchangeTeam articles on the move. Specifically, some major things to note in the transition...

1. Public folder replicas
2. Offline Address Book Generation
3. Routing Groups between Exchange servers (DONT CREATE A SEND CONNECTOR ON THE E2K7 BOX UNTIL YOU ARE READY TO GO LIVE)
4. Movement of mailboxes
5. Link State (only applicable with multiple routing groups in pre-2007 releases of Exchange)
6. Read 2 or 3 books... or hire a consultant ... you can bone your environment rather easily if you don't plan carefully and execute effectively.

Chris Clancy, EnCE CCE
MCTS: Exchange 2007

http://www.milestechnologies.com

" ... when you can't figure out what the problem is, find out what it isn't.... "

 

[58sniper]

There are some great articles at my old site, MSExchange.org that detail how to migrate as well.

Pat Richard MVP

 

[ShackDaddy]

The basics would be this:
-Install the OS
-Join the new server to the domain.
-Begin the Exchange 2007 install, which will require more base install software downloads and some AD-prep scripts that will prepare your existing Exchange org to integrate with E2007. You should know the difference between mixed mode and native mode at this point, because your existing domain won't be able to remain in mixed mode.
- Once the basic E2007 install is complete, no mailboxes will exist on the new server and mailflow should continue to be what it was before installing E2007.

You can usually get this far without screwing anything up too bad. And this is where you have to start making more complex and informed decisions. Typically organizations start by migrating a couple of test mailboxes over and doing mailflow tests from the outside using host files to simulate a DNS change. But because the creation of some send/receive connectors are required in order to get testing done, you risk disrupting the stable mailflow of your existing server.

Several factors would contribute to decisions about connectors at this point, including: are you using a smarthost for outbound mail? Any spam filtering on inbound? Would it be possible to use multiple public addresses for a while? Do you have a cert already or do you need to get one? Is it a SAN cert or just a single-name cert?

I would try and work with someone who understands Exchange routing well in order to help you with this part of the plan.

Dave Shackelford
Shackelford Consulting

 

[58sniper]

Dave's right. I'll put a plug in for his training series at Train Signal. You'll learn tons of info from it, and that may help with your migration.

Pat Richard MVP