locked
Exchange Server 2016 CU 3 with.Net Framework 4.6.2 upgrade to CU5 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote


    Hi all.  Currently we are on Exchange Server 2016 with CU 3, and with .Net Framework 4.6.2 installed.  We would like to upgrade to CU5, this is the latest CU available at this moment.  However, I've had a question on the .Net Framework requirement.

    Per the article here, "Exchange 2016 CU5 Released" (https://blogs.technet.microsoft.com/rmilne/2017/03/23/exchange-2016-cu5-released/?replytocom=106865#respond).  From the comments section, it indicates Exchange 2016 running on CU1 to CU3 should be upgrade to CU4, and then install .Net Framework 4.6.2, and then finally upgrade to CU5. 

    However, according to the Exchange 2016 matrix here, https://technet.microsoft.com/en-us/library/ff728623, Exchange 2016 CU3 do supported .Net Framework 4.6.2.  Can any one please confirm this, whether I can directly upgrade to CU 5 with CU 3 running on .Net Framework 4.6.2, or I need to remove .Net Framework 4.6.2, then upgrade to CU 4, then re-install .Net Framework 4.6.2, then upgrade to CU5.


    Thank you.

    Monday, July 24, 2017 8:28 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Since .NET 4.62 framework support was first added in Exchange 2013 CU15 and Exchange 2016 CU4 (for Windows Server 2012 and 2012 R2) this adds an upgrade step.  Framework 4.6.2 is not supported on earlier versions of Exchange when installed on Windows 2012 and Windows 2012 R2.  Exchange 2016 CU3 when installed onto Windows Server 2016 required .NET 4.6.2 though at the time of writing most customers are not in this position.

    This means that you must consider the currently installed CU and also the currently installed .NET framework when planning this upgrade.

    Ideally Exchange 2013 servers will already be on CU15, and Exchange 2016 servers will already be on CU4.  If this is the case then .NET can be upgraded prior to installing Exchange 2013 CU16 and Exchange 2016 CU5.  However if this is not the case then you cannot upgrade directly to the latest CU, you must:

    • Upgrade to Exchange 2013 CU15 or Exchange 2016 CU4
    • Only then perform the .NET upgrade to 4.6.2
    • Then upgrade to Exchange 2013 CU16 or Exchange 2016 CU5

    Refer to: https://blogs.technet.microsoft.com/rmilne/2017/03/27/exchange-2013-cu16-and-exchange-2016-cu5-net-framework-requirement/

    Hope it helps.

    Regards,

    Jason Chao

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Jason.Chao Wednesday, July 26, 2017 2:04 AM
    • Marked as answer by Tinha2010 Friday, August 11, 2017 7:47 PM
    Wednesday, July 26, 2017 2:03 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote


    Hi all.  Currently we are on Exchange Server 2016 with CU 3, and with .Net Framework 4.6.2 installed.  We would like to upgrade to CU5, this is the latest CU available at this moment.  However, I've had a question on the .Net Framework requirement.

    Per the article here, "Exchange 2016 CU5 Released" (https://blogs.technet.microsoft.com/rmilne/2017/03/23/exchange-2016-cu5-released/?replytocom=106865#respond).  From the comments section, it indicates Exchange 2016 running on CU1 to CU3 should be upgrade to CU4, and then install .Net Framework 4.6.2, and then finally upgrade to CU5. 

    However, according to the Exchange 2016 matrix here, https://technet.microsoft.com/en-us/library/ff728623, Exchange 2016 CU3 do supported .Net Framework 4.6.2.  Can any one please confirm this, whether I can directly upgrade to CU 5 with CU 3 running on .Net Framework 4.6.2, or I need to remove .Net Framework 4.6.2, then upgrade to CU 4, then re-install .Net Framework 4.6.2, then upgrade to CU5.


    Thank you.

    CU6 is the latest, not CU5.

    https://www.microsoft.com/en-us/download/details.aspx?id=55520

    The O/S was key.  Since you have 4.6.2 installed, you should be good to go.

    .Net 4.6.2 is included with Windows Server 2016. Customers deploying Exchange on Windows Server 2016 must use .Net 4.6.2 and Cumulative Update 3 or later. We plan to add support for .Net 4.6.2 on Windows Server 2012 or Windows Server 2012R2 in our December releases of Exchange Server 2016 and 2013. .Net 4.6.2 will be required for Exchange Server 2016 and 2013 on all supported operating systems in March 2017. We advise customers to start evaluating requirements to move to .Net 4.6.2 now.

    https://blogs.technet.microsoft.com/exchange/2016/09/20/released-september-2016-quarterly-exchange-updates/


    Monday, July 24, 2017 8:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Yes, you can update to CU5 or CU6 directly.

    Regards,

    Jason Chao

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 25, 2017 6:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry, I forgot to mention the OS is Windows Server 2012 R2, not Windows Server 2016....

    From the statement below, so Exchange 2016 CU3 running on Windows Server 2012 R2 is the December release, and supports .Net 4.6.2? 

    "We plan to add support for .Net 4.6.2 on Windows Server 2012 or Windows Server 2012R2 in our December releases of Exchange Server 2016 and 2013."

    Thank you. 

    Tuesday, July 25, 2017 3:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry, I forgot to mention the OS is Windows Server 2012 R2, not Windows Server 2016....

    From the statement below, so Exchange 2016 CU3 running on Windows Server 2012 R2 is the December release, and supports .Net 4.6.2? 

    "We plan to add support for .Net 4.6.2 on Windows Server 2012 or Windows Server 2012R2 in our December releases of Exchange Server 2016 and 2013."

    Thank you. 


    hmm, then you are in an unsupported state. In theory, you can still upgrade to CU5 or 6 however. I am hesitant to recommend a course of action.
    Tuesday, July 25, 2017 5:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I see.  I guess the only option available to fall back to a supported state is to uninstall .Net 4.6.2, then apply Exchange 2016 CU4, then re-install .Net 4.6.2, and then finally apply the latest available Exchange 2016 CU....

    Thank you. 

    Tuesday, July 25, 2017 7:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I see.  I guess the only option available to fall back to a supported state is to uninstall .Net 4.6.2, then apply Exchange 2016 CU4, then re-install .Net 4.6.2, and then finally apply the latest available Exchange 2016 CU....

    Thank you. 

    This should still apply if you want to remove 4.6.2

    Consider opening a case with Microsoft support for the best guidance perhaps.

    Tuesday, July 25, 2017 8:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Since .NET 4.62 framework support was first added in Exchange 2013 CU15 and Exchange 2016 CU4 (for Windows Server 2012 and 2012 R2) this adds an upgrade step.  Framework 4.6.2 is not supported on earlier versions of Exchange when installed on Windows 2012 and Windows 2012 R2.  Exchange 2016 CU3 when installed onto Windows Server 2016 required .NET 4.6.2 though at the time of writing most customers are not in this position.

    This means that you must consider the currently installed CU and also the currently installed .NET framework when planning this upgrade.

    Ideally Exchange 2013 servers will already be on CU15, and Exchange 2016 servers will already be on CU4.  If this is the case then .NET can be upgraded prior to installing Exchange 2013 CU16 and Exchange 2016 CU5.  However if this is not the case then you cannot upgrade directly to the latest CU, you must:

    • Upgrade to Exchange 2013 CU15 or Exchange 2016 CU4
    • Only then perform the .NET upgrade to 4.6.2
    • Then upgrade to Exchange 2013 CU16 or Exchange 2016 CU5

    Refer to: https://blogs.technet.microsoft.com/rmilne/2017/03/27/exchange-2013-cu16-and-exchange-2016-cu5-net-framework-requirement/

    Hope it helps.

    Regards,

    Jason Chao

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by Jason.Chao Wednesday, July 26, 2017 2:04 AM
    • Marked as answer by Tinha2010 Friday, August 11, 2017 7:47 PM
    Wednesday, July 26, 2017 2:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi all.  I've ended up uninstalled .Net 4.6.2 from our Exchange servers, and then install Exchange 2016 CU 4, then re-install .Net 4.6.2, and then finally installed Exchange 2016 CU 6.  All works good.  Thank you all. 
    Friday, August 11, 2017 7:45 PM