Microsoft has released Update Rollup 7 for Exchange Server 2010 Service Pack 3.

This update includes a number of fixes that are listed in KB2961522.

Deploying Exchange Server 2010 SP3 Update Rollup 7

The standard order of deployment for Exchange Server updates applies.

  1. Client Access servers, starting with the internet-facing ones. See this article for how to patch a CAS array.
  2. Hub Transport servers
  3. Unified Messaging servers
  4. Mailbox servers. See this article for how to patch a Database Availability Group.
  5. Edge Transport servers

About the Author

Paul Cunningham

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com.

Comments

  1. Frank

    Hi Paul
    Pls could you help me out on this.

    I succesfully Intsalled the following Programes and updates on Windows server 2012 and 2012R
    before deploying Exchange server 2010 Sp3.
    1. Windows8.1-KB2908279-v2-x64
    2. FilterPack64bit

    And Setup failed, Pls. what do I need to do.

    Thanks.

    1. Bart

      Try running installation file from elevated command prompt / powershell window

  2. Harry

    Thank you Paul for quick reply.

    Hi Paul,

    I understand we should apply SP3 and/or its rollup 7 to Internet faced CAS first…

    I don’t do CAS proxy, so all CAS are Internet faced. Questions are:

    1. We have F5 HW LB that load balance of two Internet faced CAS servers, there are several other Internet faced CAS standalone CAS servers that are not managed by F5 LB. some of just standby CAS servers, some of them are dedicated for BES use only. Can we update one of the standby CAS servers first to test it exclusively see if everything is OK. Then upgrade F5 CAS server farm later? Will this cause any potential issue.
    2. Rollup 7 for Exchange 2010 is out about one month ago. Is there any known issue if do SP3 upgrade with rollup 7 directly?

    Thanks,
    Harry

    1. Paul Cunningham

      1. I don’t think it will matter in your case, if the CAS are not proxying any connections to other CAS in internal AD sites.

      2. None that I’m aware of.

  3. Harry

    Hi Paul,

    Is there any reason why we change order of upgrade for rollup 7 to

    1.Client Access servers, starting with the internet-facing ones. See this article for how to patch a CAS array.
    2.Hub Transport servers
    3.Unified Messaging servers
    4.Mailbox servers. See this article for how to patch a Database Availability Group.
    5.Edge Transport servers

    from rollup 6, you put the order of patches

    1.Client Access servers, starting with the internet-facing ones. See this article for how to patch a CAS array.
    2.Hub Transport servers and Edge Transport servers
    3.Mailbox servers. See this article for how to patch a Database Availability Group.
    4. Unified Messaging servers

    1. Paul Cunningham

      At some point the upgrade order advice changed from Microsoft and I only noticed recently. I haven’t gone back to check all prior articles that may include the info.

  4. Aliyu Garba

    Dear Sir Paul

    am having this error during Upgrade from exchange 2010 to Exchange 2013.

    Error:
    The following error was generated when “$error.Clear();
    if ($server -eq $null)
    {
    Add-RoutingGroupMember -DomainController $RoleDomainController -ServerName $RoleNetBIOSName
    }
    ” was run: “Could not find the default Routing Group ‘Exchange Routing Group (DWBGZMFD01QNBJR)’.”.

    please i need help

    Thanks

Leave a Reply