locked
Upgrade from Exchange 2013 to Exchange 2016 RRS feed

  • Question

  • Hi everyone,

    Are the still no guides for this process?

    Thanks,

    Ivan

    Tuesday, October 20, 2015 2:09 PM

Answers

  • Bringing up an Exchange 2016 in an Exchange 2016 will be very much easier

    There is something called Up-version proxy by which your Exchange 2013 CAS can handle all the connections for Exchange 2016 mailbox servers.

    By having this you have a flexibility to introduce Exchange 2016 servers configure DAG on them , Move the mailboxes and do not worry about the CAS URL's , since exchange 2013 have the capability to route the connections to exchange 2016 mailboxes.

    Later you can introduce the CAS services into your LB's , point your CAS URL's to Exchange 2016 services

    So the best approach would be

    prepare your AD
    bring Exchange 2016 servers
    configure the URL's
    configure the certificates
    Move few pilot users and test the coexistence
    configure DA
    point all your CAS URL's to point to your exchange 2016 services

    This might help you for the certificates
    http://social.technet.microsoft.com/wiki/contents/articles/31783.configure-ssl-certificate-in-exchange-server-2016.aspx

    Also there is Exchange 2016 sizing calculator is out. Please use them to configure according to your environment.


    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

    • Marked as answer by Andy DavidMVP Friday, October 23, 2015 3:00 PM
    Tuesday, October 20, 2015 3:06 PM
  • Hi guys,

    and many thanks for your time and answers.

    But my question was: Are the still no guides for this process?

    Aparently there not updated as Mark Gossa says somewhere in his replay. 

    I need official documentation in case something goes wrong, so I guess I'll just have to wait. On the https://technet.microsoft.com/en-us/office/dn756393.aspx link, it says coming soon. So patience.

    Regards,

    Ivan

    • Marked as answer by Andy DavidMVP Friday, October 23, 2015 3:00 PM
    Friday, October 23, 2015 8:46 AM
  • Thanks for your replay Sathish, but I was looking for some thing a little more official as https://technet.microsoft.com/EN-US/library/ee332309(v=exchg.150).aspx . That's the link for upgrade from Exchange 2010 to Exchange 2013.

    Regards,

    Ivan

     

    Hi,

    Currently the Exchange Deployment Assistant has not been updated to include Exchange 2013 to 2016 migration steps. However the process will be very similar to introducing new Exchange 2013 servers into your environment as Exchange 2013 can proxy requests to Exchange 2016 and Exchange 2013 and Exchange 2016 can exist in the same load balanced CAS array.

    You can use the below process to do an Exchange 2013 to Exchange 2016 migration which is almost the same as migrating from Exchange 2013 to Exchange 2013:

    1. Upgrade all Exchange 2013 servers to CU 10
    2. Ensure that any Exchange 2010 servers are upgraded to SP3 UR 11
    3. Decommission any Exchange 2007 servers
    4. Install Exchange 2016 servers (this will prepare AD and prepare the domains automatically but you can do these as separate tasks if done by a different team etc)
    5. Configure Service Connection Point using Set-ClientAccessService -AutodiscoverServiceInternalUri on each Exchange 2016 CAS server
    6. Install certificates on the Exchange 2016 CAS servers
    7. Migrate the URLs to Exchange 2016 servers or replace Exchange 2013 servers in the CAS load balanced cluster with Exchange 2016 servers (both Exchange 2016 and Exchange 2013 can coexist in the same CAS load balanced cluster)
    8. Move mailboxes and public folder mailboxes to Exchange 2016 servers
    9. Migrate mail flow
    10. Decommission old Exchange 2013 servers

    Note that steps 4 and 5 can be done independently of each so this means step 5 can be done before step 4.

    More information about the Exchange Deployment Assistant can be found here: https://technet.microsoft.com/en-us/office/dn756393.aspx.

    Exchange 2016 Requirements: https://technet.microsoft.com/en-us/library/aa996719(v=exchg.160).aspx.

    Let me know if you have any questions.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.



    Hi,

    There are no instructions as yet on the Exchange Deployment Assistant so yes, it is just a waiting game till then or you can test out my instructions above in a test lab and go from there. 

    Thanks.



    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Friday, October 23, 2015 2:56 PM

All replies

  • Bringing up an Exchange 2016 in an Exchange 2016 will be very much easier

    There is something called Up-version proxy by which your Exchange 2013 CAS can handle all the connections for Exchange 2016 mailbox servers.

    By having this you have a flexibility to introduce Exchange 2016 servers configure DAG on them , Move the mailboxes and do not worry about the CAS URL's , since exchange 2013 have the capability to route the connections to exchange 2016 mailboxes.

    Later you can introduce the CAS services into your LB's , point your CAS URL's to Exchange 2016 services

    So the best approach would be

    prepare your AD
    bring Exchange 2016 servers
    configure the URL's
    configure the certificates
    Move few pilot users and test the coexistence
    configure DA
    point all your CAS URL's to point to your exchange 2016 services

    This might help you for the certificates
    http://social.technet.microsoft.com/wiki/contents/articles/31783.configure-ssl-certificate-in-exchange-server-2016.aspx

    Also there is Exchange 2016 sizing calculator is out. Please use them to configure according to your environment.


    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

    • Marked as answer by Andy DavidMVP Friday, October 23, 2015 3:00 PM
    Tuesday, October 20, 2015 3:06 PM
  • Thanks for your replay Sathish, but I was looking for some thing a little more official as https://technet.microsoft.com/EN-US/library/ee332309(v=exchg.150).aspx . That's the link for upgrade from Exchange 2010 to Exchange 2013.

    Regards,

    Ivan

     
    Tuesday, October 20, 2015 4:19 PM
  • Hi,

    steps in the link you provided should work for Exchange 2013 - 2016 as well.

    Before that, you will need to install CU10 on your Exchange 2013 servers.

    There aren't a lot of Changes in Exchange 2016, so the upgrade is easier than from 2010 - 2013.


    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

    Tuesday, October 20, 2015 9:09 PM
  • Thanks for your replay Sathish, but I was looking for some thing a little more official as https://technet.microsoft.com/EN-US/library/ee332309(v=exchg.150).aspx . That's the link for upgrade from Exchange 2010 to Exchange 2013.

    Regards,

    Ivan

     

    Hi,

    Currently the Exchange Deployment Assistant has not been updated to include Exchange 2013 to 2016 migration steps. However the process will be very similar to introducing new Exchange 2013 servers into your environment as Exchange 2013 can proxy requests to Exchange 2016 and Exchange 2013 and Exchange 2016 can exist in the same load balanced CAS array.

    You can use the below process to do an Exchange 2013 to Exchange 2016 migration which is almost the same as migrating from Exchange 2013 to Exchange 2013:

    1. Upgrade all Exchange 2013 servers to CU 10
    2. Ensure that any Exchange 2010 servers are upgraded to SP3 UR 11
    3. Decommission any Exchange 2007 servers
    4. Install Exchange 2016 servers (this will prepare AD and prepare the domains automatically but you can do these as separate tasks if done by a different team etc)
    5. Configure Service Connection Point using Set-ClientAccessService -AutodiscoverServiceInternalUri on each Exchange 2016 CAS server
    6. Install certificates on the Exchange 2016 CAS servers
    7. Migrate the URLs to Exchange 2016 servers or replace Exchange 2013 servers in the CAS load balanced cluster with Exchange 2016 servers (both Exchange 2016 and Exchange 2013 can coexist in the same CAS load balanced cluster)
    8. Move mailboxes and public folder mailboxes to Exchange 2016 servers
    9. Migrate mail flow
    10. Decommission old Exchange 2013 servers

    Note that steps 4 and 5 can be done independently of each so this means step 5 can be done before step 4.

    More information about the Exchange Deployment Assistant can be found here: https://technet.microsoft.com/en-us/office/dn756393.aspx.

    Exchange 2016 Requirements: https://technet.microsoft.com/en-us/library/aa996719(v=exchg.160).aspx.

    Let me know if you have any questions.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.



    • Edited by Mark Gossa Thursday, October 22, 2015 7:12 PM
    • Proposed as answer by Mark Gossa Thursday, October 22, 2015 7:12 PM
    Tuesday, October 20, 2015 10:34 PM
  • Also use these two during the sizing & planning

    http://blogs.technet.com/b/exchange/archive/2015/10/15/ask-the-perf-guy-sizing-exchange-2016-deployments.aspx

    http://blogs.technet.com/b/exchange/archive/2015/10/15/exchange-server-role-requirements-calculator-update.aspx


    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

    Wednesday, October 21, 2015 3:38 AM
  • Hi,

    Exchange 2007 and earlier won't be supported for coexistence, but Exchange 2010 and Exchange 2013 will be supported .Upgrades from Exchange 2010 to Exchange 2016 will be essentially the same as going from Exchange 2010 to Exchange 2013 was. The steps to do so will include:

    1.Prepare the environment (e.g., Active Directory and servers)
    2.Install Exchange 2016
    3.Configure 2016 server URLs
    4.Import certificates
    5.Reconfigure load balancers to point to Exchange 2016
    6.Configure database availability groups (DAGs)
    7.Move mailboxes
    8.Reconfigure mail flow to point to Exchange 2016

    Regards,

    David 



    • Edited by David Wang_ Wednesday, October 21, 2015 6:06 AM
    Wednesday, October 21, 2015 6:05 AM
  • Hi guys,

    and many thanks for your time and answers.

    But my question was: Are the still no guides for this process?

    Aparently there not updated as Mark Gossa says somewhere in his replay. 

    I need official documentation in case something goes wrong, so I guess I'll just have to wait. On the https://technet.microsoft.com/en-us/office/dn756393.aspx link, it says coming soon. So patience.

    Regards,

    Ivan

    • Marked as answer by Andy DavidMVP Friday, October 23, 2015 3:00 PM
    Friday, October 23, 2015 8:46 AM
  • Thanks for your replay Sathish, but I was looking for some thing a little more official as https://technet.microsoft.com/EN-US/library/ee332309(v=exchg.150).aspx . That's the link for upgrade from Exchange 2010 to Exchange 2013.

    Regards,

    Ivan

     

    Hi,

    Currently the Exchange Deployment Assistant has not been updated to include Exchange 2013 to 2016 migration steps. However the process will be very similar to introducing new Exchange 2013 servers into your environment as Exchange 2013 can proxy requests to Exchange 2016 and Exchange 2013 and Exchange 2016 can exist in the same load balanced CAS array.

    You can use the below process to do an Exchange 2013 to Exchange 2016 migration which is almost the same as migrating from Exchange 2013 to Exchange 2013:

    1. Upgrade all Exchange 2013 servers to CU 10
    2. Ensure that any Exchange 2010 servers are upgraded to SP3 UR 11
    3. Decommission any Exchange 2007 servers
    4. Install Exchange 2016 servers (this will prepare AD and prepare the domains automatically but you can do these as separate tasks if done by a different team etc)
    5. Configure Service Connection Point using Set-ClientAccessService -AutodiscoverServiceInternalUri on each Exchange 2016 CAS server
    6. Install certificates on the Exchange 2016 CAS servers
    7. Migrate the URLs to Exchange 2016 servers or replace Exchange 2013 servers in the CAS load balanced cluster with Exchange 2016 servers (both Exchange 2016 and Exchange 2013 can coexist in the same CAS load balanced cluster)
    8. Move mailboxes and public folder mailboxes to Exchange 2016 servers
    9. Migrate mail flow
    10. Decommission old Exchange 2013 servers

    Note that steps 4 and 5 can be done independently of each so this means step 5 can be done before step 4.

    More information about the Exchange Deployment Assistant can be found here: https://technet.microsoft.com/en-us/office/dn756393.aspx.

    Exchange 2016 Requirements: https://technet.microsoft.com/en-us/library/aa996719(v=exchg.160).aspx.

    Let me know if you have any questions.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.



    Hi,

    There are no instructions as yet on the Exchange Deployment Assistant so yes, it is just a waiting game till then or you can test out my instructions above in a test lab and go from there. 

    Thanks.



    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Friday, October 23, 2015 2:56 PM
  • Thanks for your replay Sathish, but I was looking for some thing a little more official as https://technet.microsoft.com/EN-US/library/ee332309(v=exchg.150).aspx . That's the link for upgrade from Exchange 2010 to Exchange 2013.

    Regards,

    Ivan

     

    Hi,

    Currently the Exchange Deployment Assistant has not been updated to include Exchange 2013 to 2016 migration steps. However the process will be very similar to introducing new Exchange 2013 servers into your environment as Exchange 2013 can proxy requests to Exchange 2016 and Exchange 2013 and Exchange 2016 can exist in the same load balanced CAS array.

    You can use the below process to do an Exchange 2013 to Exchange 2016 migration which is almost the same as migrating from Exchange 2013 to Exchange 2013:

    1. Upgrade all Exchange 2013 servers to CU 10
    2. Ensure that any Exchange 2010 servers are upgraded to SP3 UR 11
    3. Decommission any Exchange 2007 servers
    4. Install Exchange 2016 servers (this will prepare AD and prepare the domains automatically but you can do these as separate tasks if done by a different team etc)
    5. Configure Service Connection Point using Set-ClientAccessService -AutodiscoverServiceInternalUri on each Exchange 2016 CAS server
    6. Install certificates on the Exchange 2016 CAS servers
    7. Migrate the URLs to Exchange 2016 servers or replace Exchange 2013 servers in the CAS load balanced cluster with Exchange 2016 servers (both Exchange 2016 and Exchange 2013 can coexist in the same CAS load balanced cluster)
    8. Move mailboxes and public folder mailboxes to Exchange 2016 servers
    9. Migrate mail flow
    10. Decommission old Exchange 2013 servers

    Note that steps 4 and 5 can be done independently of each so this means step 5 can be done before step 4.

    More information about the Exchange Deployment Assistant can be found here: https://technet.microsoft.com/en-us/office/dn756393.aspx.

    Exchange 2016 Requirements: https://technet.microsoft.com/en-us/library/aa996719(v=exchg.160).aspx.

    Let me know if you have any questions.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010

    Blog: http://markgossa.blogspot.com

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.



    Hi,

    I've finally got round to doing a test migration from Exchange 2013 to 2016 and have created instructions which you can find here: http://markgossa.blogspot.com/2015/12/exchange-2013-to-2016-migration-part-1.html.

    Thanks.


    Please mark as an answer if this answers your question

    Mark Gossa

    MCSE 2003, MCITP Enterprise Administrator 2008 R2, MCSA 2012 R2, MCTS Exchange 2010, MCTS SQL 2012, MCTS SharePoint 2007, VCP4, VCP5, CCNA

    Blog: http://markgossa.blogspot.com   LinkedIn:

    Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Friday, December 18, 2015 12:25 AM