Saturday, August 17, 2013

Getting Ready to Deploy or Upgrade to Exchange 2013!

Exchange Server 2013 is the latest release of the Microsoft Exchange server product family which provides more core functionality than its predecessors and now its time for the organizations to test this product and deploy it in production and upgrade the existing environment to the latest build and provide enhanced user experience to end users.

Microsoft already started to upgrade to Exchange Server 2013 in the O365 Environment for its Tenants and now its time for the Onpremises Customers to start the migration.

There are many materials and guide lines available outside to learn more on Exchange 2013 to plan your deployment or upgrade accordingly . Below is the link to Exchange server pro blog post on Exchange Server 2013 where you can know more on this product, its features, installation requirements along with deployment and upgrade guidelines all available in one place.

Once you are aware on the feature changes with the new Exchange and the requirements, download this presentation on Exchange Server 2013 Deployment and Coexistence to get an overview how to do a real time upgrade from previous versions described perfectly.

Finally, Access the Exchange 2013 Deployment Assistant and use the step by step procedure and start your work.


Microsoft team updated the Exchange Deployment Assistant tool which will not support Edge server deployment with 2013 and also includes automated process to obtain Hybrid License key and also more enhancements to support Multi-forest deployment scenario and much more are on its way to the Tool.

Access this EHLO Blog post to know more : Updated: Exchange Server Deployment Assistant

*Review this below excellent EHLO Blog post from our Ross Smith IV to get to know how  the exact requirements for designing the proper preferred Architecture to perform a successful Exchange 2013 deployment. You can consider these points given here in the article as a guidance and make it flexible according to your needs and this is the Microsoft suggested design plan which will work perfectly if you go with this route.

Access here: The Preferred Architecture

No comments:

Post a Comment