Released: Update Rollup 4 for Exchange 2010 SP1
Published Jun 22 2011 07:55 AM 7,892 Views

Update 7/13/2011: Exchange 2010 SP1 RU4 has been removed. See Exchange 2010 SP1 RU4 Removed from Download Center for details.

Earlier today the Exchange CXP team released Update Rollup 4 for Exchange Server 2010 SP1to the Download Center.

This update contains a number of customer-reported and internally found issues since the release of RU1. See 'KB 2509910: Description of Update Rollup 4 for Exchange Server 2010 Service Pack 1' for more details. In particular we would like to specifically call out the following fixes which are included in this release:

  • 2519359Unable to Create a 'Reply With' Rule on Public Folders Even With Owner and Send As Permissions
  • 2394554Generating DSN fails if original mail uses non-support encoding charset.
  • 2490134 Outlook 2007 does not deliver "Delayed Delivery" Messages against an Exchange 2010 Server in Online mode with any additional Transport loaded in the Outlook Profile

Some of the above KnowledgeBase articles are not replicated/live at the time of writing this post. Please check back later in the day if you can't reach them.

Update Rollup 5 for Exchange Server 2010 Service Pack 1 is currently scheduled to release in August 2011.

General Notes

Note for Exchange 2010 Customers using the Arabic and Hebrew language version: We introduced two new languages with the release of Service Pack 1, Arabic and Hebrew. At present we are working through the process of modifying our installers to incorporate these two languages. Customers running either of the two language versions affected are advised to download and install the English language version of the rollup which contains all of the same fixes.

Note for Forefront users: For those of you running Forefront Security for Exchange, be sure you perform these important steps from the command line in the Forefront directory before and after this rollup's installation process. Without these steps, Exchange services for Information Store and Transport will not start after you apply this update. Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.

Kevin Bellinger

62 Comments
Not applicable

It will be on Windows update and wsus when?

Not applicable

I read your note on the bottom of the page. I see Forefront Security for Exchange don't you mean Forefront Protection for Exchange 2010?

Not applicable

Any word on when Exchange 2007 SP3 RU4 will be out?

Not to take a swipe at you guys, but can you tell us if you guys tested this a little more thuroughly than Exchange 2010 SP1 RU3? I would hate to apply this only to turn around and apply an RU4-V2 or V3.

Not applicable

Installed without a hitch...

Not applicable

Are the PDF issues with Macintosh senders resolved?   blogs.technet.com/.../mixed-ing-it-up-multipart-mixed-messages-and-you.aspx

Not applicable

Doesn't install here. I even removed the previous Rollup 2 and 3 and retried the install.

Not applicable

I'm wondering along the lines as Bootstrap Bill there, I don't see anything in the KB about the "fix" to Mac emails with attachments, which created problems in E2007SP3HFRU3 and was supposed to be included in E2010SP2HFRU4 here, I'm definiately waiting till I hear confirmation that it is or isn't in there, and if it is, that it's not causing grief.

Not applicable

@Susan - We will release on July 28th for Microsoft Update.

@Hotfix - We expect to release Exchange 2007 SP3 RU4 sometime next week. We're completing our testing currently for that release. Both releases have been thoroughly tested.

@William & Korbyn - Yes, the fix for the PDF issue is in this release. Given it was completed late in our release cycle the KB article is still being written, the Master KB will be updated once it is completed.

Not applicable

Had to run "Program FilesMicrosoftExchange ServerV14BinUpdateCas.ps1" post installation to resolve OWA "Couldn't find a base theme (folder name=base)" error when accessing OWA.

Not applicable

two questions:

Should we be removing prior rollups first?  After installing rollup 4 the server shows as having rollup2 and rollup4 installed.

We applied rollup 4 to a server which then showed rollup 2 and rollup 4 as installed patches.  The next day windows update was run and the admin picked the default and installed all updates.  Rollup 3-v3 was then installed.  Why?  I though the rollups were cumulative.  Arn't the rollups smart enough to not install over a higher version?

Not applicable

Did this rollup has fix the NDR issue generating who ever are using outlook 2003?

This message could not be sent. Try sending the message again later, or contact your network administrator. The client operation failed. Error is [0x80004005-0x0004b9-0x000501

Not applicable

@Kevin - is it the Fixed "fix" version, or the screwed "fix" like it was in 2007SP3RU3?  Sorry, a lovely mix of mac users and mac clients, and I can't really affrod to not be clear on if they might break or not.

Not applicable

Won't install on SBS2011 servers.  Fails while stopping services and results with error 1603.  Servers were patched with latest .NET updates prior.

Pete

Not applicable

@Brian: same here. Installed a fresh new Exchange 2010 SP1 server, updated to RU4. When running Windows Update it installed RU3-V3 also. Now both RU's show up as installed, to be sure I ran RU4 again since I don't know for sure if RU3 overwrites some of the files RU4 has updated already.

Not applicable

@Franc & Brian, RUs do not require installing or removing previously released RUs first. You can always install the latest RU over previous ones and yes they are cumulative. The reason RU3v3 was offered by Microsoft Update is probably because RU4 has not yet been released to MU so the logic to detect it isn't there yet.

Not applicable

@Brian: Ok, but if Windows Update installed RU3 again while RU4 was already present, did it overwrote some of the files of RU4 and do you need to reapply RU4 again? Installing RU3 by windows update took quite some time, so it looks like it was actually installing instead of just quitting because RU4 was already installed.

Not applicable

Failed to install.  "Ended prematurely" on my test system.

I think I'll wait a while.

Not applicable

@Brian Day wrote : RUs do not require installing or removing previously released RUs first

But In the KB : Any Interim Updates for Exchange Server 2010 must be uninstalled prior to installing this update rollup.

So ?

Not applicable

@Franc - RU3 should not have installed if you had RU4 already installed. However if you believe it did I would re-run RU4 just to make sure that any files that might have been overwritten were up to date.

@BWRC - An Interum Update is more or less like an individual hot fix, and a Rollup Update is a collection of IUs packaged nicely. You will know if you have an IU applied because you would have to to request it from Microsoft, and you do need to remove them before you apply an RU. Otherwise if you have just RUs installed you don't need to worry about uninstalling anything.

Not applicable

Tried installing it unsuccessfully on two different CAS servers; both ended with "Setup Wizard for Update Rollup 4 for Exhange Server 2010 Service Pack 1 (KB2509910) ended prematurely"

Not applicable

The RU4 update fixed my online mailbox search problem. Thnx guys!

Not applicable

To get around the "ended prematurely" problem I had to "run as administrator" from command prompt.  

Not applicable

How does this impact those of us with BES 5.x in place?

Not applicable

@Johnny Dallas - you should ALWAYS run your RUs as an Administrator (through a command window running under the evelvated Administrator context) if you have User Account Control still enabled.

@Arthur - Microsoft and RIM worked very hard together to resolve some issues with Exchange 2010, and most of those were resolved in the latest versions of each product. Exchange 2010 SP1 RU3 had some issues with duplciate messages showing up, but those were resolved in the RU3 V2 version. So RU4 should have those fixes in place but I would encourage you to reach out to RIM support to confirm what levels they want you at. If nothing else you can check this informative Technet article on the issue: technet.microsoft.com/.../gg670940.aspx

Not applicable

After applying RU4 to server with HT role, mails to emaill enabled public folders (regardless, if they are in E2007 or E2010) won't be delivered, error msg is:

#554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn‘t found. ObjectNotFoundException: The Active Directory user wasn‘t found. ##

When using a HT server without RU4, the same mail gets delivered without error.

Any suggestions?

Not applicable

I installed this update yesterday, and now uninstalling it from mailbox servers.

After installing the update, I cannot copy folder structures in Public Folders. When I copy a folder with subfolders, only the top folder is copied. Bad situation for us using Public folders with large subfolder structures. After uninstalling from mailbox servers I can do the copying again… So, not everything is OK with this rollup.

Not applicable

Same problem occurs if I move a folder structure from a Public folder to a mailbox or to another public folder. The top folder and messages are moved, but all subfolders and content is not moved, just deleted…

Not applicable

@Jens Jensen - Thanks for reporting these issues.  We will look into them.  Based on the description, have you checked to see if the data that was lost during the move resides in dumpster?  You should be able to recover the data from there.  Also, please open a case with Premier/CSS so that they can assist you and start the escalation process.

Ross

Not applicable

Is this problem fixed in this patch or could you please tell me when it will be fixed?

Exchange 2010 connects to a random Exchange 2003 PF store when querying the availability of an Exchange 2003 mailbox. Even when explicitly set to a designated Exchange 2003 PF store, it randomly picks another Exchange 2003 PF store.

Not applicable

@Jens Jensen and @Ross Smith IV [MSFT]

I have the same issue when I use Outlook 2010 (without SP1) to copy PF's including subfolders and mail.. Only the empty root-folder is copied. No data is available within the dumpster.

BUT, when i use OWA to copy, everything is working fine. Every mail and every subfolder is copied well.

So i think it's a bug in OL 2010 or whats your opinion.

Not applicable

@Jens Jensen and @Tzwen – We have identified the issue.  In SP1 RU4 we addressed the issue where you could not recover deleted public folders from dumpster. However, Outlook incorrectly passes a flag that indicates the item has been deleted when it has not.  As a result, when you perform a copy or move in the manner Jens described, the sub-folders are deleted.  As mentioned previously, you can recover these deleted folders from dumpster.  We’ve contacted the Outlook team to assist in further diagnosis of the issue and to help us determine the right vehicle for a fix, we’ll provide more details soon – in the meantime please open a CSS case.

Ross

Not applicable

I didn't notice anything in the 'fixed' list mentioning Outlook 2003 delay issues and the BES email issues from the previous RU.  Are these all set in this RU?

Not applicable

Nice to see the move/copy of PublicFolders may be relatively minor. More concerning to my organization though, Is the any update on the non-delivery issue with mail-enabled Public Folders?

Not applicable

@Jamal - Rollups are inclusive and include all changes that were introduced in prior rollups. So if you install SP1 RU4, you also receive all the changes we have made to E2010 SP1 since its release (i.e.,  SP1 RU1, SP1 RU2, SP1 RU3).

@Jim - I'm unaware of the issue concerning NDRs when sending to mail-enabled public folders.  It would be best to open a CSS case.

Ross

Not applicable

@Tzwen and @Ross Smith IV [MSFT]

We are only running our exchange servers in production, so had to remove UR4 from Mailbox servers in order to keep up functionality. So I cannot test the issue more. But as you say, I agree that the problem is most likely with Outlook. Only checked the problem with Outlook 2010, have not tested with Outlook 2007 or OWA.

Not applicable

Similarly to the Public Folders issue, after installing RU4 on ExSrvr2010, when a Folder is copied from a user mailbox to a PST, only the folder itself survives the copy, all messages are deleted. Singular or groups of messages will copy OK, but not a folder with messages. Tested (and failed) with both Outlook 2007 and 2010.

Not applicable

@spiridon, Could you provide more details about how to hit the issue? Such as your topology structure and the detailed steps to hit the issue. With RU4, sending mails to mail enabled public folders works on my side.

@Jim, Do you meet the non-delivery issue with mail enabled public folders as well? If yes, could you provide the details info? Or you are just afraid that spiridon's post may affect your environment?

Not applicable

@Jingping

our current environment is mixed 2010/2007/2003. Public folder stores with mail enabled folders exist in 2007 + 2010.

E2010 SP1 RU3-v3 with currently 9 Boxes: 4 CAS, 2 HT, 3 MBX. After applying RU4 to all CAS and one HT, every mail for public folders ends with the above mentioned NDR, whether it is intended for E2007 or E2010 public folder. Today I recognized, that even the public folder replication messages (hierarchy + content) which have been routed through the RU4 HT, haven't been delivered to and from E2010

.

If I disable the HT service on the RU4 box, which means, mail gets routed over the RU3-v3 box, everything's fine.

We stopped deploying RU4 (especially MBX) until this issue is fixed and opened a support case.

Not applicable

Any harm in uninstalling UR4?  We are having the issue where it mail gets deleted when moving folders to a PST.

Not applicable

@Jaiping, That is exactly my fear. My environment has gone from Exchange 2000 to 2003 to 2007 to 2010 with the last 2003 server having been uninstalled two weeks ago. After installing RU2 we experienced an issue related to Outlook 2007 clients scheduling rooms. Troubleshooting that issue took over a month of calls to MS Support and 3 escalations to get to the correct person so I am leery of installing this rollup and having to run through a similar issue.

Not applicable

Anyone know the correct process for uninstalling Update Rollup 4?  Thinking that Update Rollup 3 should be installed afterwards?  Any help would be much appreciated.  

Not applicable

@Ross

I understand that thanks but my question is with RU3 Outlook 2003 users (operation failed errors and delay when deleting/moving emails) and BES environments (duplicate emails being sent) were having problems still so will I be inheriting these problems with RU4 or did RU4 address these issues and resolve them?  I am currently on SP1 RU2 and have been hesitant to move to anything else -- basically trading off one issue for another.  Thanks.

Not applicable

@spiridon - Can you fill out the form blogs.technet.com/.../contact.aspx so that we can discuss your issue?

@Jamal - Yes SP1 RU3 addressed the BES duplicate sent item issue and does include UDP notification support for Outlook 2003.  See blogs.technet.com/.../announcing-the-re-release-of-exchange-2010-service-pack-1-update-rollup-3-v2.a... and the associated articles for more information.

@joe - Yes you can uninstall a rollup.  Once uninstalled the system is back to the state it was in prior to teh installation (so if you upgraded from SP1 RU3 to RU4, you will be back with SP1 RU3).

Ross

Not applicable

@Ross

PSS case has been solved:

After deleting the „servers“ container in one of the old still existing e2003 admin groups through adsiedit, everything’s fine. Public folder content gets replicated as well as the hierarchy.

Regular emails to public folders get delivered as expected.

The reason for being aware of this issue during deployment of RU4 may be, that the E2010 HT services have been restarted the first time after the E2003 servers have been deinstalled in this admin group.

Not applicable

Since RU5 is slated for release in August, does that mean RU4 breaks something in the meantime?

Not applicable

@Joe - we follow a regular release pattern (every 6-8 weeks) for delivering code fixes for issues discovered within the product.

Ross

Not applicable

We are seeing a mailbox size mismatch issue where the Server Data is much larger than the Local Data ... and the bulk of the Server data for the mailbox is sitting in the Outbox folder.  Anyone else seeing this issue and know of any fixes?  Thnx.

Not applicable

Any update on the moving content situation that is described in the posts of Jens Jenson and Rob.

I would like to know if we can advise the update to some customers...

Not applicable

Top link is wrong - took me to the 2010 RTM rollup 4 page (was curious as to why it wouldn't apply hehe)

http://geekcroft.wordpress.com

Not applicable

Top link is wrong - took me to the 2010 RTM rollup 4 page (was curious as to why it wouldn't apply hehe)

Version history
Last update:
‎Jul 01 2019 04:00 PM
Updated by: