Multiple December Update Rollup Releases

Earlier today the Exchange CXP team released a number of Update Rollups for versions of Exchange Server to the Download Center and via Microsoft Update.

Update Rollup 2 for Exchange Server 2010 SP1

This update contains a number of customer reported and internally found issues since the release of RU1. In particular we would like to specifically call out the following fixes which are included in this release:

  • 2322161 Passive DAG Copy Doesn't Replay Logs if "Don't mount this database at startup" is Checked
  • 2431500 Cannot connect using Outlook Anywhere as the same user from multiple XP Clients
  • 2409597 Implement OpenFlags.AlternateServer for PublicLogon

Update Rollup 3 for Exchange Server 2010 Service Pack 1 is currently scheduled to release in February.

Update Rollup 2 for Exchange Server 2007 SP3

This update contains a number of customer reported and internally found issues since the release of RU1. In particular we would like to specifically call out the following fixes which are included in this release:

  • 972186 Need to include the server service as a required service for Exchange 2007 running on Server 2008
  • 2290105 OWA Sharepoint/UNC Access is broken after SP3

Update Rollup 3 for Exchange Server 2007 Service Pack 3 is currently scheduled to release in February.

Update Rollup 5 for Exchange Server 2010 RTM

This update contains an internally found issue which can impact upgrades from RTM RU4 to Service Pack 1. We have opted to release an out-of-band update rollup for Exchange 2010 RTM proactively to ensure customers have as smooth an upgrade experience as possible.

  • 2266458 Setup cannot perform a mode:/uninstall on a HT role server since RU2 delivered MSFTE.msi

Currently, we have no plans to release future update rollups for Exchange Server 2010 RTM. We strongly recommend customers upgrade to Service Pack 1 with the latest Update Rollup after installing this update.

Update Rollup 5 for Exchange Server 2007 SP2

This security update was released earlier this morning via the Microsoft Security Response Center. Details of this bulletin and it's fix can be found below:

Currently, we have no plans to release future update rollups for Exchange Server 2007 SP2. Instead, we strongly recommend customers upgrade to Service Pack 3 with the latest Update Rollup.

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. Due to the timing of RU1 we were unable to complete this work in time.

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, 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 back up.  You will need to disable ForeFront via "fscutility /disable" before installing the patch and then re-enable after the patch by running "fscutility /enable" to start it up again post installation. 


- Kevin Bellinger

Comments (45)
  1. Karsten says:

    Thanks for the info.

    The link to 2266458 does not work.

  2. Simon says:

    Why can’t you automate the Forefront-stuff? Would be nice.

  3. Dave says:

    Since the Exchange vulnerability reported in MS10-106 affects only Exchange 2007 Service Pack 2 servers with the Mailbox Role installed, should Update Rollup 5 for Exchange Server 2007 Service Pack 2 only be installed on Mailbox servers?  Do you recommend that it be installed on CAS and Hub Transport servers as well?

  4. susan says:

    What about a fix for the new receive connector broken after update rollup 1 of Exchange 2007 sp3 is installed?  Is that fix included in rollup 2?

  5. Ron says:

    I installed it in my test environment and it appears to fix the problem with creating a send connector.  I am surprised this fix it not mentioned in the issues that the update rollup fixes.

  6. Helgard says:

    Finally! My oh my, I had to postpone our migration from E2K7 to E2K10 for almost 2 months due to the permanent store crashes w/ PF replication enabled.

    With RU2 the crashes went along, finally! Thanks for the fix @the dev’s!

    Nevertheless, I have to:

    <rant on>

    It was impossible for me to get the KB2423776 patch which would’ve fixed that specific issue in my setup. I didn’t expected to get the patch for free. I opened a ticket, paid 300 bucks, got called back – ‘uhm, sorry, but not for you’. Even though I’ve got SA on Exchange, I couldn’t get that ‘private patch’, because ‘your support level is too low/weak/whatever’ – oh, thanks..

    I know that the Exchange dev department is not responsible for the MS support strategy, but hey, please please inform your managers that denying an _existing_ bugfix/patch from people, who request exactly that patch to solve their server problem, does not only annoy admins..

    And to the tops: Even though the message at the support portal said: ‘no charge if your issue doesn’t get solved’, I did got charged of the 300 bucks for a support call that just made clear, that I’m not ‘worth’ enough to get the support I paid for.. another thanks there..

    </rant off>

    Anyhow, thanks again to the Exchange dev team! I visited your blog almost every day in the last weeks, and felt a big relief today seeing the RU2 release.

  7. Joe says:

    Thank you, I’m installing this in my test environment and will do production soon. I really hope this fixes my continuous disconnect issue that I have with outlook clients.

    I’ve got everything installed according to best practice and my clients are continuously disconnecting.

    (fingers crossed)

  8. Exchange says:

    @ Susan: If you received an interim update (between two official updates) from our support team, you will need to remove it befroe you install the rollup.

    @ Helgard: Can you please email me privately so I can look into this? I’d need your support case number. ninob AT microsoft DOT com.

  9. thomas says:

    I hope this RU2 Update for Exchange 2010 will finnally fix our Problems with redirected mails.

    Because nobody could see the sender’s email address after redirecting.

    Exchange 2010 is always removing the sender address in an redirected email message.

    So its impossible for us to reply to an mesage :-(

  10. the exchnage guy says:

    The OWA language setting bug still is not fixed.

    If you set the language with the cmdlets:

    Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -LogonAndErrorLanguage 2057    


    Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -DefaultClientLanguage 2057

    users cannot go to ‘see all options’ in OWA. When they do, they get asked to set their language again and then get a ‘page cannot be displayed’ error.

    I have had to unset it again by setting the language to 0.

    Please, please, please can someone fix this. The ability to set the default language for OWA is very desireable for customers as they’d prefer that their users do not have to do this the first time they use OWA. You’d be amazed at how many users call the helpdesk.

  11. the exchnage guy says:

    I should have mentioned that I was referring to RU2 for Ex2010 SP1. The Set-OwaVirtualDirectory language bug has been in Exchange 2010 since day one…

  12. the exchnage guy says:

    @ me

    Fixed it myself. Well, me and my friend, Google.

    I switched to using the Set-MailboxRegionalConfiguration cmdlet.

    Thus my cmdlet to set the default language to UK for all mailboxes is:

    Get-Mailbox –Resultsize unlimited | Set-MailboxRegionalConfiguration –Language en-gb –TimeZone "GMT Standard Time"

  13. Exchange says:

    @ Dave: usually we’d recommend that you install latest updates to all servers, but you will be OK if you install on mailbox only.

  14. Exch Admin says:

    I have Exchange 2010 SP1 + Rollup1 Organization with child domains.

    Today installed Exchange 2010 SP1 Rollup2 on one of the child domain and got problems.

    1. Can’t send new email:

    There’s a problem with the recipient’s mailbox. Please try resending the message. If the problem continues, please contact your helpdesk.

    #554 5.2.0 STOREDRV.Deliver.Exception:StoragePermanentException.MapiExceptionCallFailed; Failed to process message due to a permanent exception with message Cannot complete delivery-time processing. 16.55847:F70B0000, 17.43559:00000000A6020000000000000000000000000000, 255.23226:00000000, 255.27962:0A000000, 255.27962:0E000000, 255.27962:0A000000, 255.27962:9E000000, 255.17082:A1FBFFFF, 0.18273:00000000, 4.21921:A1FBFFFF, 255.27962:FA000000, 255.1494:2C000000, 255.1238:80030400, 4.33375:0F010480, 4.36685:0F010480, 1.36537:0B001F0E, 6.5587:0F0104800B001F0E0F010480, 4.33375:0F010480, 1.36537:B0846680, 6.5587:0F010480B08466800F010480, 4.64931:0F010480, 1.36537:00800800, 6.5587:0F010480008008000F010480, 4.33375:0F010480, 4.13300:A1FBFFFF, 0.37373:03001100, 4.45565:A1FBFFFF, 4.43265:A1FBFFFF, 4.63741:A1FBFFFF, 0.55895:B0840110, 4.5041:A1FBFFFF, 4.4465:A1FBFFFF, 4.6833:A1FBFFFF, 0.50217:0300DD3F, 4.5093:A1FBFFFF, 4.5318:A1FBFFFF, 4.10104:A1FBFFFF, 0.57449:40001900, 4.6025:05000780, 4.5257:05000780, 4.4606:A1FBFFFF, 255.1750:00000000, 0.26849:00000000, 255.21817:A1FBFFFF ##

    2. One user subfolder mails disappeard from outlook, in webmail ok.

    3. When moving Public folder Replicas from Exchange 2010 SP1 To new Exchange 2010 SP1+Rollup2, destination Public folder manager tool shows ZERO items in public folder, emty in outlook, in webmail…

    Uninstalled Rollup2, looks like ok now.

  15. Greg Leatherwood says:

    We are running one Exchange 2007 SP3 server and one Exchange 2010 SP1 server in coexistence mode.  I installed the respective Rollup 2s on each machine yesterday.  I’m happy to report that the installs went smoothly and everything is running fine.  

    We’re especially happy to get OWA remote file access back to Exchange 2007 (it’s been missing since SP3).  I hope the Exchange Team will seriously consider adding remote file access functionality back to Exchange 2010 in the next service pack – its really important to small businesses.  

    Good work, Exchange Team.  Happy Holidays!

  16. Matthias Zoss says:

    Update Rollup 2 for Exchange Server 2010 SP1

    gives me the same error als SP1 again:

    "Couldn’t find a base theme (folder name=base) "

    German installation. The last time to fix I had to Powershell "C:Program FilesMicrosoftExchange ServerV14BinUpdateCas.ps1"

  17. Carol Wapshere says:

    Where the heck has Set-PublicFolder gone?? I installed RU2 for 2010 because I have been suffering from is IS crashes (2423776) and now this cmdlet has dissappeared! I know you guys aren’t keen on public folders anymore, but this is a bit much…

  18. Gottfried says:


    i had to manually start all services. After that setup resumed and finished successfully. Anyone else experienced this behaviour here?

  19. tony says:

    I had the same thing happened – on HUB/MBX server, services were enabled back, but only 2-3 of them started. I waited about 10 minutes and manually started all services. After another minute or so, setup completed successfully.

    Not sure if it is related to an issue when during reboot, if one of the services doesn’t start automatically, you would get error Event ID 2604 (MSExchange ADAaccess) repeatedly until you restart Active Directory Topology service (and all other Exchange services along with it). Prior to installing RU2, I rebooted Exchange MBX server and had this error in the log, since I didn’t restart Active Directory Topology service. I wonder if it’s related to this, since I know Exchange is very picky on how services are started, and possibly it cause services not to start automatically as they should have at the end of the RU upgrade?

  20. JayCrumpGP says:

    Any ideas if this UR (UR2 for ex2010SP1) will address any CAS queue issues directly related to Blackberry Enterprise Server version 5.02?  There are several companies that are being bent over right now running this combination.  Huuuuge delays on emails to devices.  Supposedly (read on a couple different forums today) that there is a ‘buddy’ patch worked out between MS and RIM that was to be released any day (patch from MS) to resolve this issue.

  21. Duncan says:

    On the roll up 2 for 2010 Sp 1

    It stops at the begining.

    In the log… it has the following

    MSI (c) (4C:E4) [13:20:42:865]: Note: 1: 1729

    MSI (c) (4C:E4) [13:20:42:865]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (4C:E4) [13:20:42:865]: Transforming table Error.

    MSI (c) (4C:E4) [13:20:42:865]: Transforming table Error.

    MSI (c) (4C:E4) [13:20:42:865]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (4C:E4) [13:20:42:865]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (4C:E4) [13:20:42:865]: Transforming table Error.

    MSI (c) (4C:E4) [13:20:42:865]: Transforming table Error.

    MSI (c) (4C:E4) [13:20:42:865]: Note: 1: 2262 2: Error 3: -2147287038

    MSI (c) (4C:E4) [13:20:42:865]: Product: Microsoft Exchange Server — Configuration failed.

    Any ideas?

  22. Duncan says:

    Ok, I now feel a little silly.

    Right click on cmd.exe, run as administrator.  Fixed.

  23. will says:

    Installed Exchange 2007 SP3 Rollup 2 on my Admin PC last week and now I am getting intermittent errors when using the Console or Shell saying it can’t find the Domain.

    Rollup 1 doesn’t produce this behaviour, anyone have a fix?

  24. vexation says:

    @Susan – RE: "What about a fix for the new receive connector broken after update rollup 1 of Exchange 2007 sp3 is installed?  Is that fix included in rollup 2?"

    Doesn’t look like it. Just installed RU2 and still cannot create new receive-connectors.

    That said, claims that it’s because SP3 doesn’t always extend the schema and offers a fix.. I’ll give that a whirl shortly.. but it begs the question why RU2 doesn’t detect this and prompt you.

  25. Atkscott says:

    @Will: this problem drove me nuts too. The AD problem is profile dependent. Has nothing to do with RU2. If you log on as a different user, you can see you won’t have the problem. So you could delet the offending profile or try this:

    1.Close EMC/EMS.

    2.Open the profile’s Application DataMicrosoftMMC folder and delete "Exchange Management Console" file.

    3.Start EMC/EMS.

    Thanks to Eugene Pogibelny’s solution in TechNet forum for this.

  26. HotFix says:

    After applying 2007 SP3 RU2, any time we connect to a remote server with the EMC we get the "Extended protection has not been enabled." warning that is mentioned here:

    Apparently the moderator’s suggestion to resolve the issue was to uninstall RU2, but that really isn’t a solution.

    Any idea why we are getting this new warning now that we have never seen before?

  27. @HotFix says:

    Did you definitely update the Schema? (over 10 sites that I manage, SP3 didn’t do it automatically) – we had similar errors creating new receive-connectors and/or managing other servers via EMC until we forced the Schema Update.

    Others mentioned using the Exchange 2010 SP1 Schema Update instead but I’d rather stick to the 07 stuff for now.

  28. will says:

    Thanks for the fix Atkscott seems be working at the moment.

    Re-installing RU2 has brought back the annoying "Extended protection has not been enabled." warning though.

    Will have wait for RU3 at this rate!

  29. HotFix says:

    The Exchange 2007 SP3 schema extensions are in place. Specifically the rangeUpper on ms-Exch-Schema-Version-Pt is 14625, which is the SP3 version of the schema for 2007 SP3.

    We don’t have 2010 in our enviornment (yet), so we don’t have the schema extension for it (beyond that which was included in 2007 SP2).

    So… still need some sort of direction/answer on this new warning message we are getting as of 2007 SP3 RU2.

  30. Martin says:

    We have the same  "Extended Protection has not been enabled" error.  We se the error only when using EMC to look at a HUB role on a 2008 server (not R2) from a 2003  server.  The error says KB968389 needs to be installed but this update is already installed on both the 2003 and 2008 server.  

    I also have only found the unistall advice during searches for this error but I agree that this is not an answer.

  31. Kevin says:

    Same here when viewing Server Configuration > Mailbox with EMC on Server 2008 and Server 2003 machines.

  32. Kevin says:

    Same here when viewing Server Configuration > Mailbox with EMC on Server 2008 and Server 2003 machines.

  33. Martin says:


    I’ve applied Exch 2010 SP1  RU2 and got new troubles in Activesync. Original android builtin clients ( 2.1, 2.2.1) cannot send email from mobile. Other phones (like iPhone, touchdown) can send email, but android cannot, this RU2 broke it down, and new errors appear in event log.

    Watson report about to be sent for process id: 2184, with parameters: E12, c-RTL-AMD64, 14.01.0218.011, AirSync, MSExchange ActiveSync, Microsoft.Exchange.Data.Storage.InboundConversionOptions.CheckImceaDomain, UnexpectedCondition:ArgumentException, 2908, 14.01.0218.015.

    with RU1 it was running fine.

  34. dzejzi says:

    very nice

  35. HotFix says:

    Still looking for someone from Microsoft to comment on the "Extended protection has not been enabled." issue.

  36. Aboo Arif says:

    Exchange 2007 SP3 RU1 had issues on CCR. We waited for RU2 to reolve that ssues. Now RU2 shows "Extended protection has not been enabled." issue. What is the sloution now? Why no answer from Microsoft?

  37. will says:

    Getting errors when using EMC again this morning, anyone from Microsoft have a fix?

  38. Diamondas says:

    Can anyone confirm bug with 2010 SP1 RU2 and Android can’ts send mail ?

  39. George says:

    What a crap update.  It disables a load of services to start with, installs the update then fails to enable them again let alone start them!!  The log file shows it has enabled them but it doesn’t.

    This is for Exchange 2010 SP1 RU2…

  40. Carsten17 says:

    I have successfully upgraded a large  environment to 2010 SP1, then RU1 and finally RU2. The latest change was change was the update to FPE on HT & Edge servers. All updates went just fine following ALL known issues and their corresponding procedures.

    Now, MB Roles does not have FPE running so no changes were made there since RU2. Recently we saw a crash in the cluster service following a MAPI Error on one MB Server:

    MB3 reports a MAPI error on MB4, then 24 hours (+- 10 minutes) later MB3’s cluster serice terminates with no good explanation. MB3 and MB4 shares/hosts a DAG group with 12 active, 12 passive DB’s each. The result was that all active DB;s was activated on MB4, and the DAG copies are running/working fine on MB3. That is somewhat confusing; The Cluster service terminated, move all active DB’s to another server, but retain the DB copy function with no complaints….

    Right now, I consider this environment to be in an "unknown state"…..


  41. Albert Gotink says:

    Exchange 2010 SP1 RU2 took me more than 2 hours to install. Why?

    (on a virtual Mailbox Server, Windows 2008 R2, no internet)

  42. Smiliman says:

    We have the same  "Extended Protection has not been enabled" error after applying Exchange 2007 SP3 Rollup 2. Everything is on Windows Server 2008.

  43. Michael Hess says:

    Exchange 2010 SP1 RU2 has still a bug in the Public Folder Management Console. If you have more then 100 Public Folders, can console is not able to display Public Folder Statistics. The console execute the command:

    Get-PublicFolderStatistics  -Identity ‘<Foldername>’ -Server ‘<Servername>’

    But it should use instead:

    Get-PublicFolderStatistics  -Identity ‘<Foldername>’ -Server ‘<Servername>’ -ResultSize Unlimited

    With this bug the console is not really useful if you have more then 100 public folders.

  44. Slayhammer says:

    I’ve figured out that "Extended Protection has not been enabled" is solved by disabling Windows Firewall on the Exchange server to which you try to connect (which settings you try to get) through the console.

    But at this moment I don’t know which firewall setting blocks the request. According to the firewall logging, incoming TCP 135 and outgoing dynamic TCP ports are blocked. Enabling some firewall rules with these ports don’t solve the issue. Maybe there is some special traffic related to NLTMv2, but it is only my suspicion…

  45. Eri says:


    Can anyone confirm if RU2 breaks active sync for Android phones?

Comments are closed.

Skip to main content