• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 44
  • Last Modified:

Migrate Exchange 2003 Std to Exch 2010 DAGs

Hi There, I have been tasked with completing a migration from Exchange 2003 to Exchange 2010 that was left unfinished by the previous IT guy who was let go.

To give you a bit of back ground I have recently been employed by this business and one of the tasks is to complete the migration to Exch 2010. As it stands they have a head office with 1 Exchange 2003 server that stores all the mailboxes (200) and is where all outlook clients connect to access their mail. They also have a BES server in the head office with 100 users. (please also see image attached).

We have an offsite Datacentre with a 100Mbit connection between sites that has another DC and the Exchange 2010 on Server 2008 Std. One of the requirements that I have been asked is resilience which in other words means to have DAGs and the previous guy has made the error not to install Exchange 2010 on Server 2008 Enterprise to enable this functionality.

The way it has been left at the moment is that the Exchange 2010 server in the Data Centre has the MBox, Hub and CAS roles installed but is ONLY routing mail to the mailboxes on the Exchange 2003 server in the HQ. it is not used for CAS and it does not have ANY mailboxes stored on it at present. However all prep work and prerequisites have been done to enable exchange 2003 & 2010 co-existence.

The end goal is to achieve the following:

1. All 200 mailboxes on a 2 node DAG cluster one of which will be in the DC and the other in HQ (HQ will be the active DAG).

2. As DAGs do not support public folders we must replicate the public folder database on each database server in HQ and DC.

3. The BES server needs to be re-configured to connect to mailboxes on the Exch 2010 DAG.

4. There will be a CAS and Hub Transport server in both the DC and Head Office on separate servers to the DAGs mailbox server.

5. The BES server will stay in the Head Office and have its MAPI profile configured for the Exchange 2010 DAG.

My plan is to do the following:

1. Deploy an Exchange 2010 std server on Server 2008 R2 Enterprise into the Exchange organisation alongside the other 2 servers and configure this as a 1 node DAG.

2. Deploy an additional Exchange 2010 std server with the Hub and CAS roles in the Head Office and route all inbound mail to this server.

3. Move all 200 mailboxes over to the new single node Exchange 2010 DAG.

4. Move the BESADMIN mailbox over the the Exchange 2010 DAG and re-configure BES for Exchange 2010 such as the CDO and MAPI etc.

5. Replicate the Public Folders from the Exch 2003 server to the Exch 2010 server.

6. De-commission the old Exchange 2003 server from the organisation.

7. Deploy another Exchange 2010 std server on Server 2008 R2 Enterprise in the Data Centre and join this to the DAG as a second cluster node and replicate the Public Folders.

8. Re-configure the existing Exchange 2010 server in the Data Centre which is on Server 2008 R2 Std as a CAS and HUB transport server.

Please can you advise if my procedure is best practice or if there is any major steps or requirements I am missing?

My main concern is if any of the steps will break the existing exchange 2003 / 2010 co-existence in the configuration it is currently in.

Also some insight on moving the BES server without having to re-sync the devices again would be great.

2 Solutions
It looks like you have the right idea. I did this about a year ago and didnt have any major problems. If you can create a test environment with 2003 and test the migration to 2010. I just did a lot of research and then tested it. Sounds like you are part way there if you have 2003 and 2010 running already.  

for the public folders be careful of the initial sync to 2010. I know that for me it created big backlogs of smtp traffic when the public folder information was sent from 2003 to 2010. I had to spread the sync out over several days to keep the rest of the mail flowing quickly.

i didnt handle the BES portion so I cant help you there.

Simon Butler (Sembee)ConsultantCommented:
BES is easy.
Shutdown and disable all BES Services.
Remove the ESM management tools from the server.
Reboot the server.
Move the BESADMIN mailbox to the new platform.
Install the MAPI CDO tools.
Adjust the MAPI profile using the Blackberry Control Panel.
Change the BES services back to automatic.
Reboot the server.

Don't forget to deploy an RPC CAS Array, if you don't you make life a lot more difficult later on.
You can't have a 1 Node DAG.

Although personally I would suggest getting a consultant in to do the job for you. That will ensure nothing is missed and you can concentrate on getting up to speed with management skills.

Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now