Installing Cumulative Updates on Exchange Server 2013 DAG
This article will demonstrate the step by step process for installing cumulative updates for Exchange Server 2013 DAG Servers.
The steps for installing cumulative updates on Exchange 2013 are:
Prepare by downloading update files, checking backups, and reviewing known issues
After downloading CU Mount into your DVD ROM drive.
Put DAG Member into maintenance mode.
Updates Active Directory Schema
Install CU Update.
Take out DAG member from maintenance mode.
Before you install any cumulative updates on your Exchange 2013 servers, you should first:
Download the cumulative update from Microsoft. Do not download from any third party websites. You can download the latest cumulative update and upgrade an Exchange 2013 to the latest version in one update. You do not need to install all of the cumulative updates released between your current version and the latest version.
Verify that you have confirmed, working backups of your Active Directory.
Verify that you have confirmed, working backups of your Exchange servers and databases.
Verify that you have documented any customizations to your Exchange server that will need to be re-applied, such as custom OWA login pages, web.config changes, registry changes, or third party add-ons. Generally speaking you do not need to re-apply standard Exchange configurations that are set via the Exchange Admin Center or Exchange management shell (e.g. changing default message size limits).
Verify that your Exchange SSL certificates have not expired.
Check the Exchange Sup-portability Matrix and verify that you are maintaining the .NET Framework on your servers to remain compatible with Exchange 2013
Performing maintenance on DAG members
Before performing any type of software or hardware maintenance on a DAG member, you should first place the DAG member into maintenance mode. This involves moving all active databases off the server and blocking active databases from moving to the server. It also ensures that all critical DAG support functionality that may be on the server (for example, the Primary Active Manager (PAM) role) is moved to another server and blocked from moving back to the server.
Note: If you are running load-balanced Client Access servers in a site then you should configure the load balancer to remove the server from the pool of hosts, and allow any existing connections to close, before you install the cumulative update.
The exact steps for this will depend on the load balancing solution that you use, and you should refer to your vendor documentation for those.As each Client Access server is updated join it to the pool again and then repeat the process for the next server.Specifically, you should perform the following tasks:
To begin the process of draining the transport queues, run Set-ServerComponentState <ServerName> -Component HubTransport -State Draining -Requester Maintenance
To initiate the draining of the transport queues, run Restart-Service MSExchangeTransport
To begin the process of draining all Unified Messaging calls, run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Draining -Requester Maintenance
To redirect messages pending delivery in the local queues to the Mailbox server specified by the Target parameter, run Redirect-Message -Server <ServerName> -Target <MailboxServerFQDN>
To pause the cluster node, which prevents the node from being and becoming the PAM, run Suspend-ClusterNode <ServerName>
To move all active databases currently hosted on the DAG member to other DAG members, run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $True
To prevent the server from hosting active database copies, run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Blocked
To place the server into maintenance mode, run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Inactive -Requester Maintenance
To verify that a server is ready for maintenance, perform the following tasks:
To verify the server has been placed into maintenance mode, run Get-ServerComponentState <ServerName> | ft Component,State -Autosize
To verify the server is not hosting any active database copies, run Get-MailboxServer <ServerName> | ft DatabaseCopy* -Autosize
To verify that the node is paused, run Get-ClusterNode <ServerName> | fl
To verify that all transport queues have been drained, run Get-Queue
Active Directory Schema Changes and Updates
Note: Mount your CU into CD or DVD-ROM. You must to execute all command from mounted location using CMD prompt.
Most cumulative updates will include Active Directory schema changes, as well as other updates such as changed to RBAC roles. In some cases, the existence of changes will depend on which previous CU you’re upgrading from. So as a general rule you should plan for AD schema changes and updates to occur.
The AD preparation tasks can be run in advance of your server upgrades, or they can be allowed to run automatically as part of the first server upgrade process. In either case, Enterprise Admins and Schema Admins rights will be required. And if you’re running the update from an Exchange server, the RSAT-ADDS feature must be installed.
Run setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms (requires Enterprise Admins and Schema Admins permissions, and must be performed in the same AD Site as the Schema Master on a server with the RSAT-ADDS-Tools feature installed – the Schema Master itself would meet these requirements)
Run setup.exe /PrepareAd/IAcceptExchangeServerLicenseTerms
Finally Install CU.
Setup.exe /m:upgrade /IacceptExchangeServerLicenseTerms
After the maintenance is complete and the DAG member is ready to return to service, you can take the DAG member out of maintenance mode and put it back into production by performing the following tasks:
To designate that the server is out of maintenance mode, run Set-ServerComponentState <ServerName> -Component ServerWideOffline -State Active -Requester Maintenance
To allow the server to accept Unified Messaging calls, run Set-ServerComponentState <ServerName> -Component UMCallRouter -State Active -Requester Maintenance
To resume the node in the cluster and enable full cluster functionality for the server, run Resume-ClusterNode <ServerName>
To allow databases to become active on the server, run Set-MailboxServer <ServerName> -DatabaseCopyActivationDisabledAndMoveNow $False
To remove the automatic activation blocks, run Set-MailboxServer <ServerName> -DatabaseCopyAutoActivationPolicy Unrestricted
To enable the transport queues and allow the server to accept and process messages, run Set-ServerComponentState <ServerName> -Component HubTransport -State Active -Requester Maintenance
To resume transport activity, run Restart-Service MSExchangeTransport
To verify that a server is ready for production use, perform the following tasks:
To verify the server is not maintenance mode, run Get-ServerComponentState ServerName | ft Component,State -Autosize.
If you are installing an Exchange update, and the update process fails, it can leave some server components in an inactive state, which will be displayed in the output of the above Get-ServerComponentState cmdlet. To resolve this, run the following commands:
Set-ServerComponentState MAILSERVER -Component ServerWideOffline -State Active -Requester Functional
Set-ServerComponentState MAILSERVER -Component Monitoring -State Active -Requester Functional
Set-ServerComponentState MAILSERVER -Component RecoveryActionsEnabled -State Active -Requester Functional.
Note: Please comment for any help .
*** All The Best ****
© 2018, Techrunnr. All rights reserved.