Best practices to update Exchange 2013 servers
Posted on 2014-11-21
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?