HOW TO INSTALL EXCHANGE 2013/2016/2019 CUMULATIVE UPDATES

Pre-installation Checklist:

Before diving into the update process, it’s essential to ensure your environment is ready. This preparation can significantly reduce the likelihood of encountering issues during the update.

1. Backup: Begin by backing up your Exchange Server and Active Directory. This step is crucial for recovery in case of an unexpected failure during the update process.
2. Windows Updates: Ensure that the server is up to date with the latest Windows updates. This practice avoids compatibility issues with the CU.
3. Prerequisites: Check the CU release notes for any new prerequisites. Microsoft may introduce additional requirements or software components with each CU.
4. .NET Framework: Verify that your server runs a supported .NET Framework version for the CU you’re installing. Upgrading the .NET Framework might be necessary.
5. Health Check: Perform a health check of your Exchange Server using the Exchange Server Health Checker script available on GitHub. Address any identified issues before proceeding.
6. Third-party Integrations: Review any third-party software or integrations for compatibility with the new CU.
7. Documentation: Familiarize yourself with the CU’s release notes and any known issues. Planning for these can mitigate potential problems post-installation.

Preparing for Maintenance

To minimize impact and ensure a smooth CU installation process, it’s vital to prepare your Exchange Server for maintenance. Begin by gathering information about your Exchange Server using PowerShell:

powershellCopy code

Get-ExchangeServer | fl Name,Edition,AdminDisplayVersion        

This command fetches details about the server’s name, edition, and version, which are essential for documentation and troubleshooting purposes.

Setting HubTransport to Draining State

powershellCopy code

Set-ServerComponentState -Identity "exch2" -Component HubTransport -State Draining -Requester Maintenance        

This command is critical for managing mail flow during the update. It sets the server’s HubTransport component to a draining state, preventing new messages from being processed while allowing existing messages to complete.

Redirecting Queued Messages

If there’s another Exchange Server in the organization, it’s prudent to redirect queued messages to ensure continuity:

powershellCopy code

Redirect-Message -Server exch1 -Target "exch2.xxx.local"        

This step ensures that messages are not lost and are processed by another server without the one undergoing maintenance.

Handling Database Availability Groups (DAG)

For servers within a DAG, it’s necessary to suspend the cluster node and manage database copy activations:

powershellCopy code

Suspend-ClusterNode "exch1" 
Set-MailboxServer "exch1" -DatabaseCopyActivationDisabledAndMoveNow $true 
Set-MailboxServer "exch1" -DatabaseCopyAutoActivationPolicy Blocked        

These commands prevent the server from becoming a primary node for database copies and ensure that the database is moved to another DAG member, enhancing stability during the update.

Entering Maintenance Mode

powershellCopy code

Set-ServerComponentState "exch1" -Component ServerWideOffline -State Inactive -Requester Maintenance        

Placing the server in maintenance mode is crucial for preventing access and modifications during the update. It ensures the integrity of the server’s state and data.

To verify the server is in maintenance mode:

powershellCopy code

Get-ServerComponentState "exch1" | Select Component, State        

Installing Cumulative Update

Before proceeding with the CU installation, ensure the necessary prerequisites, such as the .NET Framework, are met. Download and install the required .NET version if necessary. For Exchange Server CU prerequisites, refer to the specific CU’s documentation.

1. NET Framework Installation (if required):

• Download and install from the provided URLs.
• Installing Microsoft .NET Framework 4.8

2. Download the Microsoft Exchange Cumulative update file—download link.

• Active Directory Preparation:

Install-windows feature RSAT-ADDS

Run the command prompt with as administrator: 

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms_DiagnosticDataON
setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms_DiagnosticDataON
setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms_DiagnosticDataON        

• CU Installation: Navigate to the mounted CU ISO or directory and run:
• Run the PowerShell with the administrator:
• cd F: \Setup.exe /Mode:Upgrade /IAcceptExchangeServerLicenseTerms

Post-Installation Steps

After the CU installation, it’s time to bring the server back to its operational state:

powershellCopy code

Get-ExchangeServer | Fl
Set-ServerComponentState “exch1” –Component ServerWideOffline –State Active –Requester Maintenance
Set-ServerComponentState exch1 –Component HubTransport –State Active –Requester Maintenance
Set-MailboxServer exch1 –DatabaseCopyAutoActivationPolicy Unrestricted
Set-MailboxServer exch1 –DatabaseCopyActivationDisabledAndMoveNow $false        

These commands re-enable the server components and database copy auto-activation, ensuring the server resumes its full operational capabilities.

Finally, verify the server’s cluster node status and ensure all services are running as expected:

powershellCopy code

Get-ClusterNode "exch1"        

Installing a Cumulative Update on Exchange Server 2013, 2016, and 2019 requires careful planning and execution. By meticulously following the outlined steps, administrators can ensure a seamless update process, maintaining the server’s stability, security, and performance. Always refer to the specific CU documentation for any additional steps or considerations unique to the update at hand.

Website Link: HOW TO INSTALL EXCHANGE 2013/2016/2019 CUMULATIVE UPDATES

Video Link: How to Install Exchange 2013/2016/2019 Cumulative Updates