Microsoft has released Exchange Server 2010 Service Pack 2. Here is how you can deploy it to your existing organization.
Service Pack 2 deployment follows the same installation sequence as the initial Exchange install or any other update.
- Client Access servers, starting with the internet-facing ones
- Hub Transport and Edge Transport servers
- Mailbox servers
- Unified Messaging servers
Note: if you are installing to multi-role servers just prioritize based on the same order above.
Upgrading Client Access Servers to Exchange 2010 SP2
When you install Service Pack 2 on Client Access servers you may receive an error message for a missing IIS component. This issue and the solution are described in the following article:
- Error Message “The ‘IIS 6 WMI Compatibility’ component is required” During Exchange 2010 SP2 Upgrade
If you’re updating a CAS array of servers in a Windows Network Load Balancing cluster then refer to the following article to learn how to perform the update without disrupting clients:
Upgrading Database Availability Groups to Exchange 2010 SP2
If you are updating the members of a DAG to Service Pack 2 then refer to the following article for instructions on how to perform the upgrade without requiring an outage for mailbox users:
Exchange MVP Andy Grogan has already released an updated version of his RUPS Tool for installing Service Pack 2.
Upgrading Management Tools to Exchange 2010 SP2
Any management servers or workstations that have the Exchange 2010 Management Tools installed on them will also need to be upgraded to be able to manage some of the new features of Exchange 2010 SP2 and to avoid the initialization error that can occur due to mismatched versions. Simply run the setup wizard to upgrade those computers.