Announcing the updated Exchange Deployment Assistant site

[The_Exchange_Team]

Today we’re announcing a new site for the Exchange Deployment Assistant – https://assistants.microsoft.com! Like the rest of the Exchange documentation, the Deployment Assistant has lived on TechNet since it was created. With the move towards the docs.microsoft.com platform, we needed to make a similar migration for the Deployment Assistant. With the move to the new assistants.microsoft.com site, we’ve updated the Deployment Assistant to focus solely on on-premises deployments. For online and hybrid scenarios, we’ve had two different resources offering the same guidance: the EDA, and the Office 365 mail migration advisors. Rather than having the same guidance in two different places, we’re standardizing on the Office 365 mail migration wizards for online and hybrid deployments. When you go to the new site, you’ll see two options: The first option, On-premises Exchange deployments, will go to the Deployment Assistant and all the on-premises deployment options you know and love today. You can select questions and answers to build checklists that help you deploy new Exchange 2013 or Exchange 2016 organizations, or upgrade to them from previous versions of Exchange. Exchange 2019 scenarios are coming soon! The second option, Migrate Exchange to Office 365 will take you to the Office 365 mail migration advisors. The Office 365 mail migration advisors offer the best solutions for helping you migrate your organization to Office 365. These include staged and cut-over migrations and all flavors of hybrid migrations. They’ll help you decide which migration option is best for you and even make sure your Office 365 tenant is ready for the migration! For those of you who are in the middle of an on-premises deployment or migration to Office 365, the existing Deployment Assistant will remain available until the end of April 2019. After that, and for everyone who’s looking to start a new deployment or migration, please start using the new Deployment Assistant at https://assistants.microsoft.com. Finally, we want to host additional assistants at https://assistants.microsoft.com in the future, for Exchange and other products. What are some guided assistants you’d like to see? Let us know in the comments! Thank you! The Exchange Content Team

[#2]

Isn't it time to add Exchange 2019 to the deployment guide?

[#3]

In an Exchange 2010 to Exchange 2016 migration, the Exchange URLs are updated before the Certificates are configured. Isn't this going to break existing clients when they switch to the new servers when AutoDiscover fires?

Also, when installing certificates, reminding folks to update the load balancers may be helpful

[#4]

If you update the cert before too. The good way of doing this is configuring AutoD Endpoint before anything else and ensure everyone is directed to the legacy (e.g. Ex2010) endpoint. The obviously since mailboxes are not yet migrated, they won't access the new Urls. This leaves all necessary time to update both Urls and Cert and push them to the LB too when doing SSL termination here.

The wizard tells to enter the Product Key after moving mailboxes, same for H/A. This is not logical.

1) trial edition has limitations in term of number of DB, hence in term of scalability

2) DAG should be built right after configuring the FE part and obviouslu before anything else in regard of moving the service

3) Arbitration Mailboxes and System Mailboxes only after DAG too (don't forget this is a must-do to have Admin Audit Logs be stored correctly into the System Mailbox)

[martylist]

What about Exchange 2019?

[Navishkar Sadheo]

There should be option to upgrade Exchange Server installations that have a hybrid component enabled.