Today the Exchange Team released RU6 for Exchange Server 2010 Service Pack 1 (KB2608646). This update raises Exchange 2010 version number to 14.1.355.2.

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

• 2431609  An update is available that updates the message of a retention policy in OWA for Exchange Server 2010
• 2449266  EWS drops the TCP connection to the EWS client application without any error message in a Microsoft Exchange Server 2010 environment
• 2480474  A Users do not receive quota warning messages after applying SP1 for Exchange 2010
• 2514820  An incoming fax message is not delivered to the recipient in an Exchange Server 2010 SP1 environment
• 2521927  Disabling the Exchange ActiveSync Integration feature for OWA does not take effect in OWA Premium clients in an Exchange Server 2010 environment
• 2528854  The Microsoft Exchange Mailbox Replication service crashes on a computer that has Exchange Server 2010 SP1 installed
• 2535289  The Microsoft Exchange Information Store service crashes occasionally when you run an antivirus application on an Exchange Server 2010 Mailbox server
• 2536313  Slow message delivery and mailbox access for journaling mailboxes on an Exchange Server 2010 server
• 2544246  You receive a NRN of a meeting request 120 days later after the recipient accepted the request in an Exchange Server 2010 SP1 environment
• 2548246  The Microsoft Exchange Information Store service crashes occasionally when a folder view is corrupted on an Exchange Server 2010 mailbox server
• 2549183  “There are no objects to select” message when you try to use the EMC to specify a server to connect to in an Exchange Server 2010 SP1 environment
• 2549289  A RBAC role assignee can unexpectedly run the Add-MailboxPermission command or the Remove-MailboxPermission command on an Exchange Server 2010 server that is outside the role assignment scope
• 2555851  A mailbox does not appear in certain address lists after you run commands on the mailbox in an Exchange Server 2010 SP1 environment
• 2559814  A user cannot add or remove delegates from a mailbox by using Outlook in an Exchange Server 2010 environment
• 2561514  Exchange Server 2003 user cannot view the free/busy information of a user in a different federated organization
• 2563860  You cannot create a new mailbox database if you already have 1000 mailbox databases in an Exchange Server 2010 environment
• 2567409  Certain free/busy messages are not replicated from an Exchange Server 2010 server to an Exchange Server 2003 server
• 2571791  Retention policies are applied to Contact items unexpectedly in an Exchange Server 2010 environment
• 2572052  Certain properties of a recurring meeting request from external email accounts are missing in an Exchange Server 2010 SP1 environment
• 2575005  You cannot start the EMC or the EMS in an Exchange Server 2010 Service Pack 1 environment
• 2578631  Certain users cannot send email messages to a mail-enabled public folder in an Exchange Server 2010 environment
• 2579172  Items that are deleted or moved still appear in the original folder when you use Office Outlook in online mode to access an Exchange Server 2010 mailbox
• 2579671  No results returned when you use the ExpandGroup method in EWS to retrieve a list of members of a Dynamic Distribution Group in an Exchange Server 2010 environment
• 2582095  The SmtpMaxMessagesPerConnection property of a send connector is not replicated to the subscribed Edge Transport server in an Exchange Server 2010 environment
• 2600835  The RPC Client Access service crashes when you delete an attachment of an item by using Outlook in online mode in an Exchange Server 2010 SP1 environment
• 2601701  The memory usage of the MSExchangeRepl.exe process keeps increasing when you perform a VSS backup on Exchange Server 2010 databases
• 2616127  “0x80041606” error code when you use Outlook in online mode to search for a keyword against a mailbox in an Exchange Server 2010 environment
• 2617126  The Store.exe process crashes when you send an email message that has attachments in an Exchange Server 2010 SP1 environment
• 2627769  Some time zones in OWA are not synchronized with Windows in an Exchange Server 2010 environment

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

I’d recommend to thoroughly test this rollup in a test and acceptance environment first, prior to implementing it in production.

Note that when running ForeFront Protection for Exchange, you need to stop all ForeFront services before installing the rollup. While not entirely perfect, this is a welcome improvement over earlier rollups, where you had to disable and re-enable ForeFront using fcsutility /disable and fcsutility /enable respectively.

For the correct procedure on how to update a DAG and its members, check here.

You can download Exchange 2010 SP1 Rollup 6 here.

Today the Exchange Team released Rollup 5 for Exchange Server 2007 Service Pack 3 (KB2602324). This update raises Exchange 2007 version number to 8.3.213.1.

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

• 981820  New X-headers of a message item do not appear when the message item is retrieved by IMAP4 or by POP3 in an Exchange Server 2007 SP2 environment
• 2292150  A deleted hyperlink remains in the HTML source of an email message if you create the email message by using OWA in an Exchange Server 2007 environment
• 2411423  The Msftefd.exe process constantly consumes up to 100 percent of CPU resources when your mailbox language is set to German on an Exchange Server 2007 server
• 2450078  The sent time in an email message body is incorrect when you reply or forward the email message by using an EWS application in an Exchange Server 2007 environment
• 2451415  “There was a problem logging onto your mail server” error message when you use a POP3 client to access a mailbox in an Exchange Server 2007 SP3 environment
• 2536652  EdgeTransport.exe randomly stops responding on a Hub Transport server after you configure public folder replication in Exchange Server 2007
• 2536695  “Some items cannot be deleted” error message when you try to delete or modify an email message in a public folder in an Exchange Server 2007 environment
• 2536697  DBCS characters in a rule name are converted to question marks after you move a mailbox from Exchange Server 2003 to Exchange Server 2007
• 2537783  The EdgeTransport.exe process crashes occasionally after you install Update Rollup 2 for Exchange Server 2007 SP3
• 2538958  Extended Protection Warning Displayed in Exchange Management Console and Exchange Management Shell After Installing RU2 for Exchange 2007 SP3
• 2554575  Items accumulate in the MRM submission folder when managed folder assistant journal items in an Exchange Server 2007 environment
• 2556751  The EdgeTransport.exe process crashes when processing certain email messages on an Exchange Server 2007 Hub Transport server
• 2557304  The Store.exe process may consume excessive CPU resources and memory resources intermittently when a user opens a calendar item by using OWA in an Exchange Server 2007 SP3 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, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.

You can download Exchange 2007 SP3 Rollup 5 here.

Today the Exchange Team released RU5 for Exchange Server 2010 Service Pack 1 (KB2582113). This update raises Exchange 2010 version number to 14.1.339.1.

I’d recommend to thoroughly test this rollup in a test and acceptance environment prior to implementing it in production. After the RU3 and RU4 debacles, I can’t emphasize this enough: test, test. test.

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

• 2275156  The inline contents disposition is removed when you send a “Content-Disposition: inline” email message by using EWS in an Exchange Server 2010 environment
• 2499044  You cannot save attachments in an email message by using OWA if the subject line contains special characters in an Exchange Server 2010 environment
• 2509306  Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2010 environment
• 2514766   A RBAC role assignee can unexpectedly run the Add-ADPermission command on an Exchange Server 2010 server that is outside the role assignment scope
• 2529715  Slow network or replication issues after you change the number of virus scanning API threads in Microsoft Exchange Server 2010
• 2536704  Mailbox users who are migrated by using ILM 2007 cannot use the Options menu in OWA in an Exchange Server 2010 environment
• 2537094  French translation errors occur when you edit a response to a meeting request by using OWA in an Exchange Server 2010 SP1 environment
• 2554604  A RBAC role assignee can unexpectedly manage certificates that are outside the role assignment scope in an Exchange Server 2010 environment
• 2555800   You cannot use the GetItem operation in EWS to retrieve properties of an email message in an Exchange Server 2010 environment
• 2555850   You cannot delete a mailbox folder that starts with a special character in its name by using Outlook in an Exchange Server 2010 environment
• 2556096  The columns in the .csv logging file are not lined up correctly when you perform a discovery search on a mailbox in an Exchange Server 2010 environment
• 2556107  The columns in the .csv logging file are not lined up correctly when you perform a discovery search on a mailbox in an Exchange Server 2010 environment
• 2556133   A device that uses Exchange ActiveSync cannot access mailboxes in an Exchange Server 2010 environment
• 2556156  Extra.exe crashes when it performs RPC activity checks against an Exchange Server 2010 server
• 2556352  “ChangeKey is required for this operation” error message in Outlook for Mac 2011 in an Exchange Server 2010 environment
• 2556407  Certain client-only message rules do not take effect on email messages that are saved as drafts in an Exchange Server 2010 environment
• 2559926   “There are no items to show in this view.” error message when you try to view a folder by using Outlook in an Exchange Server 2010 environment
• 2572958  The “Test-OutlookConnectivity -Protocol HTTP” command fails with an HTTP 401 error 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.

For the correct procedure on how to update a DAG and its members, check here.

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

You can download Exchange 2010 SP1 Rollup 5 here.

Just a quick notice that few minutes ago the Exchange Team pulled Exchange Server 2010 Service Pack 1 Rollup 4.

As reported earlier, there were potential data loss issues with this rollup when moving folders around in public folders or PST files using any version Outlook; Note that moving folders using OWA through Exchange Web Services works fine.

A fix for this issue will be incorporated in the RU5 update which is scheduled for August. So, like RU3 v2 v3 which took about a month to appear after the initial RU3 release was pulled, we’ll have to wait until August for RU5.

For those who already deployed RU4 an interim update has been made available that fixes this issue. The interim update can be obtained by contacting support.