Today the Exchange Team released version 2 of Rollup 5 for Exchange Server 2010 Service Pack 2 (KB2785908). This is an updated version of Rollup 5, released on November 14th but pulled due to a DAG issue; this updated Rollup should fix that issue. This update raises Exchange 2010 version number to 14.2.328.10.

For a list of changes included in the original version of Rollup 5, consult the original EX2010SP2RU5 post here. In addition, this version of the Rollup addresses vulnerabilities described in MS12-080 and will fix the following error when running Get-DatabaseAvailabilityGroup after installing of the original version of the Rollup:

An unexpected error has occurred and a Watson dump is being generated: Could not load type ‘Microsoft.Exchange.Rpc.ActiveManager.AmDeferredRecoveryEntry’ from assembly ‘Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′.

Oddly, when comparing the lists of issues fixed, the following fix went MIA in Rollup 5 v2:

• 2748870 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010

I’ll update this article when I receive information on the missing KB2748870 fix.

As of Rollup 4, its no longer required to disable/re-enable ForeFront Protection for Exchange using the fscutility to be able to install the Rollup properly. However, if you want to remain in control, you can disable ForeFront before installing the Rollup using fscutility /disable and re-enable it afterwards using fscutility /enable.

If you want to speed up the update process for systems without internet access, you can follow the procedure described here to disable publisher’s certificate revocation checking.

If you got a DAG and want to properly update the DAG members, check the instructions here.

Note that Rollups are cumulative, i.e. they contain fixes released in earlier Rollups for the same product level (RTM, SPx). This means you don’t need to install previous Rollups during a fresh installation but can start with the latest Rollup.

As with any Hotfix, Rollup or Service Pack, I’d recommend to thoroughly test this rollup in a test and acceptance environment first, prior to implementing it in production.

You can download Exchange 2010 SP2 Rollup 5 v2 here.

Update (November 16th): It turns out there’s a serious bug affecting DAGs after installing RU5. Recommendation is not to deploy RU5 while Microsoft investigates the issue. Meanwhile, the RU was also pulled. Note that this is the exact reason why I emphasize on not rushing updates in production and run them in test and acceptance environments first. When testing is not an option (but there are lots of options there with free virtualization technologies available), I recommend maintaining an incubation period of at least 1 month and monitoring sites like TechNet forum or related comments on the EHLO blog for issues.

Today the Exchange Team released Rollup 5 for Exchange Server 2010 Service Pack 2 (KB2719800). This update raises Exchange 2010 version number to 14.2.328.5.

Here’s the list of changes in this Rollup:

• 2707146 IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment
• 2710975 Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet
• 2712001 ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment
• 2712595 Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment
• 2716145 Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used
• 2717522 Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list
• 2720017 An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment
• 2727802 Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server
• 2733415 Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment
• 2733609 Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment
• 2743761 DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment
• 2748766 Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment
• 2748767 You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment
• 2748870 Declined meeting request is added back to your calendar after a delegate opens the request by using Outlook 2010
• 2748879 You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment
• 2749075 A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment
• 2749593 Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging
• 2750293 Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment
• 2750847 An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network
• 2763886 “The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment

As of Rollup 4, its no longer required to disable/re-enable ForeFront Protection for Exchange using the fscutility to be able to install the Rollup properly. However, if you want to remain in control, you can disable ForeFront before installing the Rollup using fscutility /disable and re-enable it afterwards using fscutility /enable.

If you want to speed up the update process for systems without internet access, you can follow the procedure described here to disable publisher’s certificate revocation checking.

If you got a DAG and want to properly update the DAG members, check the instructions here.

Note that Rollups are cumulative, i.e. they contain fixes released in earlier Rollups for the same product level (RTM, SPx). This means you don’t need to install previous Rollups during a fresh installation but can start with the latest Rollup.

As with any Hotfix, Rollup or Service Pack, I’d recommend to thoroughly test this rollup in a test and acceptance environment first, prior to implementing it in production.

You can download Exchange 2010 SP2 Rollup 5 here.

Today the Exchange Team released Rollup 4 for Exchange Server 2010 Service Pack 2 (KB2706690). This update raises Exchange 2010 version number to 14.2.318.2.

Here’s the list of changes in this Rollup:

• 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 archive 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 Event 14035 or Event 1006 is logged when Admin sessions are exhausted in an Exchange Server 2010 environment

In addition to these fixes, this Rollup also includes a fix for the WebReady security issue described in Microsoft Security Bulletin MS12-058 (KB2740358).

Note that  This Rollup includes changes enabling Retention Tags for Calendar Items and Tasks (see KB2685001). If you wish to retain pre-SP2RU4 functionality, implement the following registry key on each Mailbox server:
HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeMailboxAssistants\Parameters\ELCAssistantCalendarTaskRetentionEnabled=0×00000000 (REG_DWORD); default value is 1. More information on possible implications at the Exchange Team’s blog here.

Important: Be advised that it is reported that installing MS12-058 (KB2740358) means Rollup 4 will be installed on your system. This applies to manual installations but updates installed through Windows Update / WSUS as well, which might pose a challenge (or better, dilemma) for security departments (Thanks to Paul Bendall).

Those who use WSUS to deploy security updates or manually apply MS12-058 will be inadvertently applying Exchange 2010 SP2 RU4 as the security

As of this Rollup, its no longer required to disable/re-enable ForeFront Protection for Exchange using the fscutility to be able to install the Rollup properly. However, if you want to remain in control, you can disable ForeFront before installing the Rollup using fscutility /disable and re-enable it afterwards using fscutility /enable.

Note that Rollups are cumulative, i.e. they contain fixes released in earlier Rollups for the same product level (RTM, SPx). This means you don’t need to install previous Rollups during a fresh installation but can start with the latest Rollup.

As with any Hotfix, Rollup or Service Pack, I’d recommend to thoroughly test this rollup in a test and acceptance environment first, prior to implementing it in production. For the correct procedure on how to update DAG members, check here.

You can download Exchange 2010 SP2 Rollup 4 here.

Today the Exchange Team released Rollup 3 for Exchange Server 2010 Service Pack 2 (KB2685289). This update raises Exchange 2010 version number to 14.2.309.2.

Here’s the substantial list of changes included in this Rollup:

• 2510607  “Cannot open the free/busy information” error message when you try to view folder permissions in Outlook
• 2514700  Extra.exe does not trace a single user whose legacyExchangeDN attribute contains one or more special characters in an Exchange Server 2010 environment
• 2571342  The Folder contacts list is empty when a user views the properties of a mail-enabled public folder in an Exchange Server 2010 environment
• 2572029  Synchronization of an organizational forms library fails when you use Outlook in Cache mode in an Exchange Server 2010 environment
• 2586828  The EdgeTransport.exe process consumes 100 percent of CPU resources on an Exchange Server 2010 Edge Transport server
• 2589233  Meeting requests bypass the requirement for delegate approval and instead book resource mailboxes automatically in an Exchange Server 2010 environment
• 2633043  “There were no writeable domain controllers found in Active Directory site” error message when you run the ExBPA tool in an Exchange Server 2010 organization
• 2647396  You cannot disable a public folder by using the “Disable-MailPublicFolder” cmdlet in an Exchange Server 2010 environment
• 2648263  You cannot open routing log files on Exchange Server 2010 Hub Transport servers in a mixed Exchange Server 2003 and Exchange Server 2010 environment
• 2667120  MSExchangeAutodiscoverAppPool application pool crashes on an Exchange Server 2010 Client Access server when you try to view the free/busy information about a user in a trusted domain
• 2668900  Event ID 2915 is logged when you apply a fallback policy to a service account in an Exchange Server 2010 environment
• 2670099  You cannot open calendar folders that are shared by hidden users in an Exchange Server 2010 environment
• 2671128  RPC Client Access Cross-Site connectivity issues occur in an Exchange Server 2010 environment
• 2673542  MRM retention policy in the Junk E-Mail folder does not work when you manually move email messages in an Exchange Server 2010 environment
• 2673591  Crash occurs in the Autodiscover application pool in an Exchange Server 2010 environment
• 2674185  MAPI_E_CALL_FAILED errors occur when a MAPI application that uses the MAPI function in Outlook 2007 MAPI or in Outlook 2010 tries to access an Exchange Server 2010 server
• 2674445  You cannot change the access permissions of a Calendar folder in an Exchange Server 2010 environment
• 2677872  You cannot use a distribution group in the hierarchical address book when you create the group in Exchange Server 2003
• 2681250  “550 5.6.0″ NDR when a journal report is sent to an external contact in an Exchange Server 2010 environment
• 2682047  You cannot access a mailbox for several hours after you disconnect and then reconnect the mailbox in an Exchange Server 2010 SP2 environment
• 2682408  AddOrganizerToSubject parameter does not take effect when a recurring meeting conflicts with another meeting in an Exchange Server 2010 environment
• 2682895  Error message when a role assignee runs the Get-MailboxExportRequestStatistics cmdlet in an Exchange Server 2010 environment
• 2684583  You cannot delete an empty folder in a .pst file by using Outlook in an Exchange Server 2010 environment
• 2689810  A meeting request that you send from an EWS application is in plain text format instead of HTML format when an attendee opens the request by using Outlook in online mode
• 2695011  Junk Email settings do not work as expected after you migrate or move a mailbox to an Exchange Server 2010 SP1 Mailbox server
• 2695022  The E-mail Signature text box is not editable in Outlook Web App when you use Google Chrome in an Exchange Server 2010 environment
• 2695836  You cannot move a mailbox in an Exchange Server 2010 environment that has a message size limit configured
• 2696642  An additional line of space is added in each paragraph in an email message when you click the Printable View icon in Outlook Web App in an Exchange Server 2010 environment
• 2698927  Resource mailbox that has AutoAccept configured does not process a meeting request that contains custom code or script in Exchange Server 2010
• 2698960  You cannot move some users’ mailboxes from one Exchange Server 2010 mailbox database to another
• 2698976  Managed Folder Assistant does not process a mailbox that has external contacts in another tenant organization in an Exchange Server 2010 environment
• 2699023  Event ID 9646 is logged on the Exchange Server 2010 mailbox server when you access a mailbox that has more than 250 folders by using an IMAP4 client
• 2699577  GAL-related client-only message rule is not applied in Outlook after you apply RU1 for Exchange Server 2010 SP2 in an Exchange Server 2010 environment
• 2699582  Error message when you play a voice mail by using Outlook 2007 in an Exchange Server 2010 environment
• 2700544  Multiple recovery items are added to a subfolder of the Recoverable Items folder in an Exchange Server 2010 environment
• 2705425  UMWorkerProcess.exe consumes large amounts of memory when you try to listen to voice messages by using Outlook Voice Access in an Exchange Server 2010 environment
• 2705555  The Set-Mailbox cmdlet takes a long time to complete configuration in an Exchange Server 2010 environment
• 2705570  An error occurs when a user whose mailbox is hidden from the Exchange address list tries to open the Scheduling Assistant tab by using the light version of Outlook Web App
• 2705647  A user cannot log on to a mailbox that is full by using Outlook Web App in an Exchange Server 2010 environment
• 2705682  Post-reform spelling rules are not used in the Portuguese (Portugal) dictionary in Outlook Web App in an Exchange Server 2010 environment
• 2706523  You cannot create a mailbox or mail-enable a mailbox for a disabled user account in an Exchange Server 2010 environment
• 2708880  You cannot set the “Country/region” attribute of a user mailbox to “Curaçao,” “Bonaire, Sint Eustatius and Saba,” or “Sint Maarten (Dutch part)” by using the Exchange Management Console on an Exchange Server 2010 server

When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.

Note that Rollups are cumulative, i.e. they contain fixes released in earlier Rollups for the same product level (RTM, SPx). This means you don’t need to install previous Rollups during a fresh installation but can start with the latest Rollup.

You can download Exchange 2010 SP2 Rollup 3 here.

Today the Exchange Team released Rollup 2 for Exchange Server 2010 Service Pack 2 (KB2661854). This update raises Exchange 2010 version number to 14.2.298.4.

Here’s the list of changes included in this rollup:

• 2519806  A meeting request that is sent by an external user or by using a non-Microsoft email system is stamped as Busy instead of Tentative in an Exchange Server 2010 environment
• 2556766  Slow performance when you create many contacts by using Exchange Web Services in an Exchange Server 2010 environment
• 2592398  Email messages in the Sent Items folder have the same PR_INTERNET_MESSAGE_ID property in an Exchange Server 2010 environment
• 2601301  Customized contact objects revert to the default form after a public folder database replication in an Exchange Server 2010 environment
• 2625450  You cannot generate an OAB file that is larger than 2GB in an Exchange Server 2010 environment
• 2630808  A user can log on to a mailbox by using Outlook for Mac 2011 unexpectedly in an Exchange Server 2010 environment
• 2632201  MAPI_E_INVALID_PARAMETER errors occur when a MAPI application receives notifications in an Exchange Server 2010 environment
• 2635223  A hidden user is still displayed in the Organization information of Address Book in OWA in an Exchange Server 2010 environment
• 2636387  Event ID 3022 is logged and you cannot replicate a public folder from one Exchange Server 2010 server to another
• 2636883  Returned message items can disappear from the search results view when you use Outlook in online mode in an Exchange Server 2010 environment
• 2641249  Error message when you use the “Folder.Bind” method in an Exchange Server 2010 environment
• 2641753  An email message from an Exchange Server 2003 user is forwarded incorrectly to an external recipient of an Exchange Server 2010 user mailbox
• 2644144  A read receipt is not sent when a receiver does not expand a conversation to preview the message by using OWA in an Exchange Server 2010 environment
• 2644920  The Get-FederatedDomainProof cmdlet fails in an Exchange Server 2010 SP1 environment
• 2645587  An external email message is not delivered to mail-enabled public folders and you do not receive NDR messages in an Exchange Server 2010 environment
• 2649499  Updates for a meeting request are sent to all attendees directly in an Exchange Server 2010 environment
• 2649679  Text in tables is displayed incorrectly in the Conversation view in Outlook Web App in an Exchange Server 2010 environment
• 2652730  You encounter failures when you run the Test-EcpConnectivity cmdlet to test Exchange Control Panel connectivity in an Exchange Server 2010 environment
• 2657103  CPU resources are used up when you use the Set-MailboxMessageConfiguration cmdlet in an Exchange Server 2010 environment
• 2660178  “More than one mailbox has the same e-mail address” error message when you try to manage a mailbox in a tenant organization in an Exchange Server 2010 SP1 Hosting mode environment
• 2661277  An ActiveSync user cannot access a mailbox in an Exchange Server 2010 forest
• 2661294  An email address policy does not generate the email addresses of recipients correctly in an Exchange Server 2010 environment
• 2663581  OK button is not displayed when you change your password in Outlook Web App by using Firefox in an Exchange Server 2010 environment
• 2664365  Certain MailboxStatistics properties are not updated when a user uses a POP3 or IMAP4 client to access a mailbox in an Exchange 2010 environment
• 2664761  DPM protection agent service may stop responding on Exchange Server 2010 servers that are protected by System Center DPM 2010
• 2665806  Error message when you open an RTF email message that has inline attachments in an Exchange Server 2010 environment
• 2672225  A user in a trusted account forest cannot use the EMC to manage an Exchange Server 2010 SP2 server
• 2673087   Error message when you try to copy the Inbox folder to another folder in Outlook in online mode in an Exchange Server 2010 environment
• 2677847  The Microsoft Exchange File Distribution service consumes large amounts of memory in an Exchange Server 2010 environment
• 2678361  The user-agent information about an Exchange ActiveSync device is not updated in an Exchange Server 2010 environment
• 2678414  The display name of a contact in address book is empty in an Exchange Server 2010 environment
• 2681464  An EWS application crashes when it calls the GetStreamingEvents operation in an Exchange Server 2010 environment
• 2685996  Error message when a user who does not have a mailbox tries to move or delete an item that is in a shared mailbox by using Outlook Web App Premium
• 2688667  W3wp.exe consumes excessive CPU resources on Exchange Server 2010 Client Access servers when users open recurring calendar items in mailboxes by using Outlook Web App or EWS
• 2693078  EdgeTransport.exe process crashes in an Exchange Server 2010 environment
• 2694280  Whatif switch does not work in the Set-MoveRequest or Resume-MoveRequest cmdlet in an Exchange Server 2010 environment
• 2694289  Resource mailbox does not forward meeting request to delegates after one of the delegates’ mailbox is disabled in an Exchange Server 2010 environment
• 2694414  The update tracking information option does not work in an Exchange Server 2010 environment
• 2694473  File name of a saved attachment is incorrect when you use OWA in Firefox 8 in an Exchange Server 2010 environment
• 2694474  Incorrect delivery report when you send an email message to a recipient who has configured an external forwarding address in an Exchange Server 2010 environment
• 2696857  EdgeTransport.exe process crashes without sending an NDR message when you send a message to a distribution group in an Exchange Server 2010 environment
• 2696905  Day of the week is not localized in MailTips in Outlook Web App in an Exchange Server 2010 environment
• 2696913  You cannot log on to Outlook Web App when a proxy is set up in an Exchange Server 2010 environment

When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.

Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SP). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup.

You can download Exchange 2010 SP2 Rollup 2 here.