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

MS Exchange 2007 to MS Exchange 2010 Migration

I have a MS Exchange 2007 server that has been up and running without issues for a couple of years now.  I am migrating to Ex2010 by installing a new server and migrating mailboxes over.  I have all services on one server.  Both are Server 2008, the new one is R2, with all of the latest service packs.

I have moved my mailbox to the new server and I am able to send and receive.  The only issue at this point is that I get a server cert error when I open Outlook.  This occurs if I am on the network and when I am using Outlook Anywhere.  This will go away once I move all of the mailboxes over this weekend and change DNS, etc. but I would like to start moving the users that don't work remotely starting today to get that done.  Is there a way I can move mailboxes and not have them get this message?  

1 Solution
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Hi, the point here is that you have installed Exchange 2010, i assume all 3 roles (MBX, HT and CAS) on the same box. So the first thing you need to do is:

1- configure all CAS url's, internal and external. You can leave the internal url's as is but you need to configure the external, for OA, OWA, EWS, OAB and ActiveSync. Also for POP and IMAP if you are using it.
2- after the url's are configured use the Exchange Management Console to create a new certificate (go to server configuration, select the server on the right hand pane and start a new certificate wizard). If you have one internal CA than use it to issue the cert.

after the certificate is issue you will need to change the HT mail flow to exchange 2010. by default you are able to send and receive but if you done nothing mail is coming through 2007 and in order to be able to uninistall it in the end, you will need to change that.

finally you will need to move 1 mailbox, test and if everything is ok move all the others. The tests should include all external and internal services (OA, OWA, etc) and also dont forget to test autodiscover.

one more point is that if both servers are on the same AD site and you want to have coexistence (provide external services to 2007 and 2010 users on the same period) you will need an extra URL for the OWA external access.

hope it helps.
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

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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