We help IT Professionals succeed at work.

Migrate Exchange 2003 to 2010

507 Views
Last Modified: 2012-02-16
Hi,
We will be upgrading from exchange standard 2003 to standard 2010. A new server is being order of course with 08 standard as well. We currently have 2 existing 2008 R2 servers on the domain and the domain functionality mode is in the 2008 state.
 
Basically what i am looking for is some good information about the migration process. I have read both servers are brought up and somewhat functioning together. One of my main concerns is not causing too much down time since right now we use OWA on a dmz and thats what our iphone people connect to. But from what our server sales rep has mentioned is that owa runs on the exchange sever itself in our type of situation with under 100 mail boxes.

Can someone comment on the migration aspects or exchange and owa, also if you are using a past article or post that is great too.
Comment
Watch Question

CERTIFIED EXPERT
Author of the Year 2010
Top Expert 2010

Commented:
For 100 users you can use a single server.

Install your new 2010 server with typical roles (CAS, Mailbox, Hub Transport)

As far as ActiveSync is concerned the CAS server will deal with requests for 2010 and 2003.

For OWA you will need 2 public IP addresses.

You will need 2 A records in your external DNS your existing OWA one which will be forwarded to the 2010 server.

The second will be legacy.domainname.com and this will be forwarded to the 2003 front end server on port 443.

All requests for OWA will come to the CAS server.  Any mailboxes on the 2003 server will then be automatically redirected to the legacy.domainnane.com URL.

Again, both URL's must be available externally.

Author

Commented:
Thanks.
So i currently have owa.myname.com this is OWA of course,
The the other A record i believe is just mail.myname.com

Do these just stay the same and my firewall would redirect to the right server or do i need to make additional A records for the new server that comes online as well?
CERTIFIED EXPERT
Author of the Year 2010
Top Expert 2010

Commented:
owa.myname.com would be forwarded to your 2010 server.

If you have mail.myname.com already and this isn't being used by any other service then update this so your firewall forwards this IP to the 2003 server.  You would then set this up as the legacy URL
The safe route for this process is to move mailboxes in the evening while mail traffic is low. If a mailbox migration fails, the mailbox remains on the 2003 server and is still operational.

Mailbox migration time is depenant upon these factors:

1. Speed of old and new servers
2. Nic and switch speeds
3. Size of the mailboxes
4. If any mailboxes fail due to corrupt messages.
5. The amount of network traffic at that time.

I suggest you start small by taking a few small mailboxes and migrate them in one evening. This provides an idea of what you should encounter with the remaining mailboxes.

Author

Commented:
have you seen or even wrote a comprehensive article on the migration process from 2003 to 2010. I have found bits and pieces through online searches but not much from start to finish.

Author

Commented:
i guess i am just getting confused when i read that both old and new servers are active and the new server is handling most of the mail even though the mailboxes arent moved yet. Then to throw a wrench in it i need to worry about am i killing the connection to my iphones out in the world.
CERTIFIED EXPERT
Author of the Year 2010
Top Expert 2010
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
CERTIFIED EXPERT
Author of the Year 2010
Top Expert 2010

Commented:
As I said the iPhones won't be a problem just change your port 443 to go to the CAS server instead of the 2003 server.  That will solve that one.

It's OWA that needs both IP's to be active externally.

Alternatively just move all mailboxes over a weekend?

Both systems need to be operational inside your network otherwise you won't be able to move mailboxes and clients won't update themselves.  It's pretty standard practice during a migration.

Author

Commented:
Hi demazter, i got all your info and it is very handy. I know you said the article was for SBS so i just had a clarifying question. In there it says to make the new server a Domain Controller? I thought that was not typically a role exchange should be running? Or if anyone else can clarify this?

Author

Commented:
joensw, seriously the link is not even in English!
CERTIFIED EXPERT
Author of the Year 2010
Top Expert 2010

Commented:
It is a supported configuration it's just not a recommended one.

When you get to that stage just split the roles up so they are on different servers.  The steps are the same.
CERTIFIED EXPERT

Commented:
sorry for the links his in frensh yes
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.