Exchange Service Packs and Rollups – Up to Date or Not?

As an administrator for Exchange, knowing what service pack or roll-up update has been released is important if you want to keep Exchange version current. A quick way to find out what has been released by Microsoft in terms of updates, is listed here. This page currently contains the service pack and rollup list for Exchange 2003, 2007, 2010 and even 2013 (preview and RTM). The information is provided in convenient tables with the name, version number, when it was released and relevant links to the service Pack or rollup:

— Sample table from the page —

Now that you have a list of the available updates, how do you determine what version your Exchange Server is? Read my blog article here for a good place to start which referenes a PowerShell script that has been written by Bhargav Shukla located here. This script will give you more than the GUI or get-exchangeserver |fl *version* command.

Now that you have your service Pack and rollup update level, you can review the list of updates you are missing. If you are not up to date, check the latest update and the date it was released. As a rule of thumb I like to wait about 30 days before I consider applying a rollup update or service pack. The reason is, if you look at the complete list of updates on the Microsoft Wiki page, a few of these updates have had to be re-released due to customer issues with the patches. In some cases the 30 day window does not always work, as in the case of Rollup 7 for Exchange Server 2010 SP1 reveals. However, most of the time this give Microsoft enough time to work out the majority of the issues that can happen when people start applying the patch to their servers.

Before I run a service Pack or rollup, I like to see what exactly is being updated. First I click on the link in the table for the update I want to apply. So for Exchange 2010 SP2 Rollup Update 4 a link to KB2706690 is listed:

Once on the update page, scroll down to the Introduction Section which lists all the changes in this update:

Issues that the update rollup resolves:

Update Rollup 4 for Exchange Server 2010 SP2 resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

  • 2536846
    Email messages sent to a mail-enabled public folder may be queued in a delivery queue on the Hub Transport server in an Exchange Server 2010 environment
  • 2632409
    Sent item is copied to the Sent Items folder of the wrong  mailbox in an Exchange Server 2010 environment when a user is granted the Send As permission
  • 2637915
    “550 5.7.1” NDR when an email message is sent between tenant organizations in a multi-tenant Exchange Server 2010 environment
  • 2677727
    MRM cannot process retention policies on a cloud-based achive mailbox if the primary mailbox is in an on-premises Exchange Server 2010 organization
  • 2685001
    Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment
  • 2686540
    Journal report is not delivered to a journaling mailbox in an Exchange Server 2010 environment
  • 2689025
    Performance issues when you use the light version of Outlook Web App in an Exchange Server 2010 environment
  • 2698571
    Some email messages are not delivered when you set the MessageRateLimit parameter in a throttling policy in an Exchange Server 2010 environment
  • 2698899
    Add-ADPermission cmdlet together with a DomainController parameter fails in an Exchange Server 2010 environment
  • 2700172
    Recipient’s email address is resolved incorrectly to a contact’s email address in an Exchange Server 2010 environment
  • 2701162
    User A that is granted the Full Access permission to User B’s mailbox cannot see detailed free/busy information for User B in an Exchange Server 2010 environment
  • 2701624
    ItemSubject field is empty when you run the Search-MailboxAuditLog cmdlet together with the ShowDetails parameter in an Exchange Server 2010 environment
  • 2702963
    The “Open Message In Conflict” button is not available in the conflict notification message in Exchange Server 2010
  • 2707242
    The Exchange Information Store service stops responding on an Exchange Server 2010 server
  • 2709014
    EdgeTransport.exe process crashes intermittently on an Exchange Server 2010 server
  • 2709935
    EdgeTransport.exe process repeatedly crashes on an Exchange Server 2010 server
  • 2713339
    Multi-Mailbox Search feature returns incorrect results when you perform a complex discovery search in an Exchange Server 2010 environment
  • 2713371
    Throttling policy throttles all EWS applications in Exchange Server 2010
  • 2719894
    The Microsoft Exchange RPC Client Access service consumes 100 percent of CPU resources and stops responding on an Exchange Server 2010 Client Access server
  • 2723383
    Incorrect time zone in a notification when the Resource Booking Attendant declines a meeting request from a user in a different time zone in an Exchange Server 2010 environment
  • 2724188
    A subject that contains colons is truncated in a mixed Exchange Server 2003 and Exchange Server 2010 environment
  • 2726897
    Admin sessions are exhausted as a result of delegate access in an Exchange Server 2010 environment
  • 2743871
    Microsoft Exchange Transport service does not restart automatically after an Exchange update is installed

Update Rollup 4 for Exchange Server 2010 SP2 also resolves the issue that is described in Microsoft Security Bulletin MS12-058.<BR>For more information about Security Bulletin MS12-058, click the following article number to view the article in the Microsoft Knowledge Base:<BR>


MS12-058: Vulnerability in Microsoft Exchange Server WebReady document viewing could allow remote code execution: August 14, 2012<

Don’t forget if you are installing your updates on a DAG cluster to follow this Microsoft article – This is a great article to read prior to performing the update.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s