locked
Currently on CU19 and .NET 4.8 - upgrading to latest CU23 okay? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I remember back in the CU15 to CU21 times M$ caught a lot of slack for their unpreparedness with older .NET versions and Exchange 2013.

    I've currently got an Exchange 2013 CU19 with .NET 4.8. Are there any known issues with going directly from CU19 to CU23? Do I need to do anything special or performed a half-step upgrade first (to something in between)?

    TIA!

    Friday, March 27, 2020 3:25 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    You can go directly to CU23, however if you are on .net 4.8 on an unsupported CU it can cause issues so i advise you upgrade as soon as possible. .NET 4.8 is only supported on CU23.

    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, March 28, 2020 11:42 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    You can go directly to CU23, however if you are on .net 4.8 on an unsupported CU it can cause issues so i advise you upgrade as soon as possible. .NET 4.8 is only supported on CU23.

    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, March 28, 2020 11:42 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Alceryes,

    Because each CU is a full installation of Exchange and includes updates and changes from all previous CU's, and.NET Framework 4.8 can be used with CU23 according to the supportability matrix in this official link, so agree with Edward that you can go directly to CU23. 

    As regards to your concern about the known issues, according to the release note of CU23, there is a known issue that The Set-SendConnector cmdlet does not work for Exchange Server 2013 in hybrid scenarios that have a Edge server installed. But a workaround has been provided and documented in KB 4523519.  

    Hope this can be helpful.

    Regards, 

    Yuki Sun

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

    Monday, March 30, 2020 6:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Alceryes,

    Just checked in to see how things are going with this thread.  If the information above was helpful, it would be appreciated that you can help mark it as answer. If you still have further concerns on this, please feel free to report back.

    Regards,

    Yuki Sun

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

    Thursday, April 2, 2020 7:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for your answers - all good on the upgrade.

    Just had the stupid IIS virtual directories certificate reset that always seems to occur with Exchange upgrades but that was expected.

    Tuesday, April 7, 2020 2:42 PM