In November, we launched the Exchange Server 2010 Deployment Assistant. In the initial version of the Deployment Assistant, content was available for customers upgrading from Exchange 2003. We are happy to announce that today we've released content for the following scenarios to http://technet.microsoft.com/exdeploy2010:

  • Upgrading from Exchange Server 2007
  • Upgrading from a mixed Exchange Server 2003/2007
  • New Exchange Server 2010 installation

The Deployment Assistant allows you to create Exchange 2010 deployment instructions that are customized to your environment. The Deployment Assistant asks a small set of questions, and based on your answers, it provides a set of instructions that are designed to get you up and running on Exchange 2010. Instead of reading dozens of topics in the Exchange 2010 library, you simply answer a few questions, and the Deployment Assistant gives you customized content to install Exchange 2010.

The feedback on our initial release was very positive. We would love your feedback on these new scenarios, as well. Feel free to leave a comment here, or send an email to edafdbk@microsoft.com via the 'Feedback' link located in the header of every page of the Deployment Assistant. Send us your 'success stories' after using this tool! We'd love to hear about them, too!

-- Katie Kivett
Microsoft Exchange Deployment Assistant PM

Not applicable
Excellent Post! Many, many thanks for this as it is very useful and will make my life a lot easier!   :)

However, I have a quick question: I selected “Upgrade from Exchange 2007” with no to disjointed namespace, yes to public folders and no to Edge and UM.

On the “Add digital certificates on the Client Access server” step, you mention the creation of the legacy.contoso.com namespace.

On the “Configure legacy host name” step you also mention it: “You need to create a legacy domain name system (DNS) host name so that Exchange 2003 and Exchange 2010 can coexist. (...)”

But is this true if we are migrating from a pure Exchange Server 2007 environment? Or am I right in assuming that, in this case, we don’t need the legacy namespace?

Thank you very much and excellent work!
Not applicable
Hi Nuno,

Thanks very much for your kind words, and for reporting this.  The legacy name space is needed for both Exchange 2003 and Exchange 2007 upgrades.  The topic is being modified to reflect this.  Right now it refers only to Exchange 2003, but that is being modified to include Exchange 2003 and Exchange 2007 (referred to as your legacy Internet-facing Exchange server).  The topic update should be published shortly.

Thanks again for the feedback!
Not applicable
Great Post!

Haven't read all the steps yet but it will be a life saver for sure. we might migrate from 2003/2007 to 2010 very soon.

Thank you very much...
Not applicable
Thank you a lot for your update !

However I might require additional information about 2003 to 2010 Cross-Forest Migrations.

Any New-MoveRequest command in the target Forest fails with the following error message "You must use the RemoteTargetDatabase parameter for remote push move requests."
Even though I follow Technet documentation : http://technet.microsoft.com/en-us/library/dd298174.aspx
I am trying to pull the Exchange 2003 Mailbox to my Exchange 2010 server. (Remote Legacy Mailbox Moves)

I would appreciate any additional link or information regarding this matter, but can't find any as nobody seems to have succeeding such a scenario yet.

Keep up the good work !
Not applicable
Just going through the tool again, but it looks like it's having an issue.  I'm able to choose "Upgrade from Exchange 2007", but after making my initial 4 Yes/No choices and hitting next I get a pop-over box informing me of an unknown error and letting me know that I can try starting over.  I've tried with both IE and Firefox, but no difference.
Not applicable
Jason: So sorry for the inconvenience. We are having an issue with the site today that is in the process of being fixed. It should be back up soon.
Not applicable
Thanks for reporting the issue.  The issue is resolved now and you can access the Assistant online at http://technet.microsoft.com/exdeploy2010