Exchange 2013 DAG CU19 Upgrade
Here is the step that I will do to upgrade the Exchange 2013 to CU19, with the new .NET Framework 4.7.1.
Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 SP1 was in effect CU4, and CU18 is the fourteenth post SP1 release. Updating from any CU to any CU is supported, however to the best of my knowledge Microsoft only tests updates from N-2 builds. For example, when Microsoft released CU19, they would test the update process from CU17 and CU18 as they were the previously supported builds. It means that when we are updating from CU10 to CU19, it’s possible that we will encounter some problem that Microsoft has not identified in their testing. Although that risk exists, in my opinion, it has diminished over time as the quality of the Exchange 2016/2013 code has improved. Microsoft best practices are to keep the Exchange upgrade with the two last version available, so now we should have been at CU17 or CU18, but since we are not, the best approach, in my opinion, is go directly to CU19.
After the Exchange 2013 CU16 the .NET 4.6.2 is a requirement, and to make a smooth transition, the CU15 was working with .NET 4.6.1 and .NET 4.6.2, so we could upgrade the .NET without getting big downtimes.
Since the CU15 is no longer available the bridge has washed out, so we need to upgrade the .NET first and then the Exchange.
How to Upgrade from Exchange 2013 CU10 to CU19 on DAG Members
- Backup/Snapshot of all Server
- I will check if the databases are healthy (Check the links below for more information about this step)
- Put one node in Maintenance mode (Check the links below for more information about this step)
- Reboot the Server
- Install .Net 4.7.1
- Reboot the Server
- Disable the Antivirus
- Install the CU19 (This step will take between 1 hour to 2 hours) – Note: We need to make sure there is disk space available, it makes sense to extract the CU to another drive than C: drive.
- Reboot the server after the successful CU installation.
- Wait a few minutes for the servers to get sorted, and check if the databases are healthy (Check the links below for more information about this step)
- Remove the server from Maintenance mode (Check the links below for more information about this step)
- Re-check if the databases are healthy (Check the links below for more information about this step)
- Repeat the same steps to update the Other DAG member
More information for the Steps 2,3,10,11 and 12 on this links below:
Installation failure recovery
Experience will show whether this is a major concern or not. Update rollups are usually able to roll back seamlessly if they encounter an error. Whether the cumulative update failed installation recovery process becomes a burden or not, only time will tell.
Some Items for Consideration
- Make a full backup of the Exchange servers
- The customs customisations can be lost, especially on the OWA
- Third-party software integrations
Exchange .NET Framework Support Table
I believe that is all, the important things that we need to think about, off course, Microsoft have made it much simple the Exchange upgrades, and normally this runs smoothly, but be sure that you have a full backup of the servers.
Best of luck and hope this can help you.