Upgrading to Exchange Server 2010 Service Pack 2

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.

  1. Client Access servers, starting with the internet-facing ones
  2. Hub Transport and Edge Transport servers
  3. Mailbox servers
  4. 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:

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.

About Paul Cunningham

Paul is a Microsoft Exchange Server specialist for one of Australia's largest companies, and is the Publisher of ExchangeServerPro.com. He is also an MCP, MCSA, MCSE, MCTS, and an MCITP for Exchange Server 2007/2010. Connect with Paul on Twitter, LinkedIn and Google+.

Comments

  1. George Caba says:

    Hi,

    I just want to say … THANK YOU … for your articles regarding upgrading MS Exchange Server 2010 to SP2, saved me lots of time. I had some issues at the beginning when I started installing SP2 on CAS/HT servers, setup failed requesting to have some hotfixes previously installed . See messages bellow:

    Setup cannot continue with the upgrade because the ‘beremote’ () process (I
    D: 3120) has open files. Close the process and restart Setup.

    Client Access Role Checks FAILED
    Install hotfix Microsoft Knowledge Base article 982867 from http://code.msd
    n.microsoft.com/KB982867.

    This computer requires the update described in Microsoft Knowledge Base art
    icle 979744 (http://go.microsoft.com/fwlink/?linkid=3052&kbid=979744). Please in
    stall the required update to proceed.

    Install hotfix Microsoft Knowledge Base article 983440 from http://code.msd
    n.microsoft.com/KB983440.

    This computer requires the update described in Microsoft Knowledge Base art
    icle 977020 (http://support.microsoft.com/kb/977020). Please install the require
    d update to proceed.

    Setup cannot continue with the upgrade because the ‘beremote’ () process (I
    D: 3120) has open files. Close the process and restart Setup.

    The Exchange Server setup operation didn’t complete. More details can be found
    in ExchangeSetup.log located in the :\ExchangeSetupLogs folder.

    Exchange Server setup encountered an error.

    I’ve downloaded all four of them, stopped BackupExec agent and installed two of them for the other I got a message saying that they are not for that OS, KB’s were .net 2.0 related which wasn’t installed. I’ve ended installing all Windows updates, including SP1 then re-ran setup and everything went smoothly.

    • I take it you were upgrading from Exchange 2010 RTM?

      If that is the case then yes, its a good idea to update the server OS to latest service pack before installing Exchange 2010 SP1 or SP2.

    • Prajwal says:

      Yes windows update is required .. Even i faced the same kind of issue, but installed the updates manually…

Speak Your Mind

*