Solved

Best practices to update Exchange 2013 servers

Posted on 2014-11-21
9
183 Views
Last Modified: 2014-12-15
Apart from probably staggering the schedules for downtime for critical and security update installs, amongst one's Exchange 2013 clusters, is there any information on best practices for critical and security update installations?

We have two physical sites, say (a) and (b).  Site (a) has one main virtual Exchange 2013 server, along with a 2nd. Exchange 2013 server from site (b) for possible disaster recovery, in that, if site (b) goes down, site (b) can continue to function as it has a server at site (a), etc.

Is there a routine or order in which the servers are updated and then rebooted?
0
Comment
Question by:nurturer69
  • 5
  • 4
9 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40459112
You can only update passive servers - if you attempt to patch an active server then it will failover to become the passive.
Therefore the rule is usually to do the current passive first (rather than trigger a failover), then failover and do the active.
However be aware that in a lot of cases, once you have failed over to the later version, you cannot fail back to an older version. This is because changes are made to the database.

The CAS role is AD site wide, so you will have clients using all servers in an AD site for CAS connectivity - it doesn't matter which DAG the server is a member of. As such, you should patch both servers in the same AD site so that the CAS role is at the same version, then patch the other site.

Simon.
0
 

Author Comment

by:nurturer69
ID: 40462868
The updates to install are from Windows Update in Control Panel, or is there a different setup file or executable to run?
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40463206
Windows Update will just update Windows and other applications - it doesn't do Exchange.
Exchange 2013 Cumulative Updates have to be done separately by downloading the update file and running setup.exe

Simon.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:nurturer69
ID: 40464719
Will the server need to be placed into maintenance mode thru power shell on the server to be updated?

Example:

Set-ServerComponentState –Identity Server1 –Component HubTransport –State Draining –Requester Maintenance Get-Queue –Server Server1 | Format-Table Identity, MessageCount
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40465639
It doesn't have to be, although you can choose to do so.
I usually do so, but every now and then will not, which gives the failover capability a test.

Simon.
0
 

Author Comment

by:nurturer69
ID: 40465679
And is it necessary to update the schema?
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40465750
If the update requires it then it will do it for you.

Simon.
0
 

Author Comment

by:nurturer69
ID: 40466900
So, as a synopsis:

PART 1:
1) Download Cumulative update to passive server on site 1
2) Place server in maintenance mode (or don't - decision is arbitrary)
3) Launch Cumulative update setup.exe file
4) Wait for completion of updates
5) When complete, reboot server.

PART2:
1) Fail active server as passive, making recently updated passive server the active server on site 1
2) Download Cumulative update to passive server (normally active server) on site 1
2) Place server in maintenance mode (or don't - decision is arbitrary)
3) Launch Cumulative update setup.exe file
4) Wait for completion of updates
5) When complete, reboot server.
6) Fail active server over making it the passive server again.

STEP 3:
Perform testing by logging into EAC and OWA to check mailbox accessibility and Outlook functionality.

STEP 4:
Repeat same steps for site 2

Am I missing anything?
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 40469720
That is pretty much it. It isn't a difficult process by any means.
However if the schema master is not in the same site as the first server you are updating, you may find you have to wait for the schema updates to fully replicate before you can continue.

Simon.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The article will show you how you can maintain a simple logfile of all Startup and Shutdown events on Windows servers and desktops with PowerShell. The script can be easily adapted into doing more like gracefully silencing/updating your monitoring s…
The reason that corporations and businesses use Windows servers is because it supports custom modifications to adapt to the business and what it needs. Most individual users won’t need such powerful options. Here I’ll explain how you can enable Wind…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question