Rollup 6 for Exchange 2010 SP3

Does anyone know when Microsoft is going to release either Rollup 6 or a patch for Exchange 2010 SP3? Rollup 3 for SP3 introduced the following issues: 
“Some users (not all of them) report that they don't see new emails in their Outlook 2010 box on Shared folders, even though they got the new email message envelope. When they change folder and back to the Inbox the new mail is suddenly visible. Same sort
of "delay" happens when users mark a message for follow-up or try to change a message from unread to read.”
We have installed Rollup 5 but it did not address the issue. 

Currently, there is no official document about the release of RU6 for Exchange 2010 SP3. If the RU6 for Exchange 2010 SP3 will be coming, you can find this information in the Exchange Team Blog.
Thanks for your understanding.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

  • Latest Update Rollup for Exchange 2010 SP3

    Currently we are using RU2 for Exchange 2010 SP3. We are facing an issue with OWA through IE 11 (no support for premium). To correct this issue it's recommended to install RU3. Here we are asking the expert opinion about installing RU7
    on all Exchange 2010 servers and whether it makes any different issues or is it enough to install RU3
    Thanks in advance

    Currently we are using RU2 for Exchange 2010 SP3. We are facing an issue with OWA through IE 11 (no support for premium). To correct this issue it's recommended to install RU3. Here we are asking the expert opinion about installing RU7
    on all Exchange 2010 servers and whether it makes any different issues or is it enough to install RU3
    Thanks in advance
    Personally, if you are going to update the servers, you should apply the latest RU regardless. So I would go with RU7.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • What is the total space Update Rollup 7 For Exchange 2010 SP3 (KB2961522) will take after installation?

    Quick question. 
    What is the total space Update Rollup 7 For Exchange 2010 SP3 (KB2961522) will take after installation?

    Your question is a big vague. Extracting the rollup will use some space but you can delete the files afterwards.
    Are you concerned about space while installing? If you have adequate space it shouldnt be a problem.
    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    I am asking space after installation, it will definitely install some files so how much space extra space it needed in exchange directory drive. 

  • Support Forefront Protection 2010 for Exchange 2010 SP3

    I have a simple question: Is there a full support of FPE 2010 (Version 11.0.727.0) for Exchange 2010 SP3 (and Rollup Updates)?

    It seems that FPE 2010 for exchange 2010 SP3 is supported and you need to install the Rollup 4. For more detailed information, please refer to the link below:
    Hotfix Rollup 4 for Microsoft Forefront Protection for Exchange
    Updates for Microsoft Forefront and Related Technologies
    Hope this helps!

  • Unable to install rollup4 for Exchange 2010 SP3

    I'm unable to install KB2905616 on my multi-role Exchange 2010 SP3 server. The setup wizard gets stuck at "the setup wizard is generating native images for .NET assemblies........"
    I know that this process will take some time to complete but I have waited 10 hours.
    I've tried to reboot the server and restart the setup.
    Exchange is functioning perfectly otherwise.
    Any help would be greatly appreciated :)
    /Søren Emig

    I recommend you check if the anti-virus has been disabled before you start the upgrade process.
    If you didn't ,the update could fail or take an extended amount of time. 
    Also, disable all other third-party apps/plugins that might be installed (like backup agents).
    In addition,the following articles for your reference:
    Install the Latest Update Rollup for Exchange 2010
    When you install an update rollup package, Exchange tries to connect to the certificate revocation list (CRL) Web site. Exchange examines the CRL list to verify the code signing certificate. (To download and view the CRL list, see
    CodeSignPCA.crl.) If Exchange can't connect to the CRL Web site, the following symptoms may occur:
    The installation takes a long time to complete.
    You receive the following message during the installation: Creating native images for .Net assemblies
    When Exchange isn't connected to the Internet, each CRL request must complete before the installation can continue.
    To work around this issue and to reduce installation times, turn off the
    Check for publisher’s certificate revocation option on the server that is being upgraded. Use the following steps:
    Start Internet Explorer.
    On the Tools menu, click Internet Options.
    Click the Advanced tab, and then locate the Security section.
    Clear the Check for publisher’s certificate revocation check box, and then click
    After the update rollup installation is complete, select the Check for publisher’s certificate revocation option.
    Generating NGEN images takes longer than expected
    Hope this helps!
    Niko Cheng
    TechNet Community Support

  • Issue with Update Rollup 5 for Exchange 2010 SP3 - Mailboxes that were auto mapped not working

    Below is  my response in another thread but creating a new one in the hopes that someone has the same issue and a solution besides mine below.
    Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
    Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
    What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
    Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
    the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
    I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
    This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

    Not sure why it was suggested to use the auto mapping feature to grant permissions because that is the component that is causing the issue. Also, there is nothing wrong with the auto configuration because the user can access their own mailbox just fine and
    also select mailboxes in their Outlook that were NOT auto mapped.
    With that said, here is how I fixed them all.
    Remove the permissions using the Exchange Console. Don't forget Send As
    Wait about 15 minutes. The mailbox should disappear from the users Outlook
    Open an Exchange PowerShell window and run the following command:
    .\add-mailboxpermissionsnoautomap.ps1 -Identity mailbox -User user -AccessRights FullAccess
    Have the user add the mailbox to their Outlook using the manual process.
    All is well....
    If you don't have the PS script add-mailboxpermissionsnoautomap.ps1, you can download it. I stumbled across it a few years ago and use it all the time. If you can't find it, just use the Exchange built in command for adding mailbox folder permissions but
    specify automap $false.
    The idea here is to grant the user access without auto mapping.

  • Exchange 2010 SP3 Update Rollups

    Hi All,
    I have a question about installing Update Rollups for Exchange 2010 SP3. After some organizational changes I have to take care of windows updates and our WSUS server. During the last check I found out that there are:
    Update Rollup 5,6,7 listed in WSUS for our Exchange which is (CAS, HUB, MB). I've checked also some information about installing Update Rollup but it's not very clear for me. i saw also a problems after installing Update Rollup 6 and also some info from
    The release contains fixes for customer reported issues and previously released security bulletins. Update Rollup 7 is
    not considered a security release as it contains no new previously unreleased security bulletins. Customers running
    any Service Pack 3 Update Rollup for Exchange Server 2010 can move to Update Rollup 7 directly.
    So, what is the best way to do it? 
    - Decline old Update Rollups, Install all other security and critical updates from WSUS, reboot the server, install Update Rollup 7, reboot the server?
    Thanks in advance

    Hi kondio
    Thank you for your question.
    Service packs and update rollups are part of the servicing strategy for Exchange 2010. They provide an effective and easy-to-use method to distribute Exchange 2010 fixes and modifications. We recommend that you install the latest service pack and update
    rollup to keep the product up-to-date.
    I suggest you update manually instead of WSUS.
    You  can refer to the following link to read about RU:
    If there are any questions, please let me know.
    Best Regard,

  • Exchange 2010 SP3 Update 7 breaks OWA for some IE11 users

    I had issues earlier with OWA on some clients running Internet Explorer 11 (as
    documented in this thread), and managed to resolve it by disabling compatiblity mode in IE11.
    After SP3 Update Rollup 7 the issue came back, and no tinkering with the compatibility mode will solve it.
    Have anyone encountered this issue before? The issue only appears on certain machines in their own AD OU as well as own subnets.

    I haven't heard that Exchange 2010 SP3 Update Rollup 7 has this issue so far. In your case, I would like to verify if you remove all interim updates for Exchange 2010 SP3 before installing Rollup 7. If no, remove it and check the result.
    Here is a kb for your reference.
    Update Rollup 7 for Exchange Server 2010 Service Pack 3
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Rollup 8 for Exchange 2010 SP2 causes EWS error with bad parameter for Exchange.MailboxReplicationService.ProxyService

    When I installed Rollup 8  for Exchange 2010 SP2 it caused an error in EWS
    EWS failed with the error:
    exchange web service could not load file or assembly Exchange.MailboxReplicationService.ProxyService bad parameter
    When I uninstalled the rollup all worked fine again.
    Any ideas, Thanks in advance?

    To apply this update rollup, you must have Exchange Server 2010 SP2 installed. And remove all interim updates for Exchange Server 2010 SP2 before you apply this update rollup. Please check your installation deployment by the following article:
    Install the Latest Update Rollup for Exchange 2010
    Description of Update Rollup 8 for Exchange Server 2010 Service Pack 2
    If all requirements and preparations are configured properly, please collect your error logs to check your installation. It would be helpful to post some event logs here for further analysis.
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 SP3 RU8

    I am trying to rollback Exchange 2010 SP3 RU8. When I uninstall the update the installer asks for exchangeserver.msi for Exchange 2010 SP3 RU7. I downloaded RU7 from the Microsoft website. It did not accept it as the correct msi. I ran the Exchange 2010
    SP3 RU7 update I download and it comes up as RU8. I need the exchangeserver.msi from Exchange 2010 SP3 RU7. Thank you for your help.

    You may need the original SP3 binaries located here:
    See this thread for more ideas about rolling back:
    Update:Microsoft has released version 2 of SP3 RU8 today. The link should be live soon.
    Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Event ID 9877, Exchange 2010 SP3 RU4

    On 2/19 I installed RU4 for Exchange 2010 SP3 on a server at a client's site.  This is a single server with all the roles on it, with about 40-45 mailboxes. Ever since then, during the busiest hours of the day (around 7AM to 5:30PM or so), I get the
    following event log error on this server:
    Log Name:      Application
    Source:        MSExchangeIS Mailbox Store
    Date:          2/20/2014 6:58:49 AM
    Event ID:      9877
    Task Category: Content Indexing
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
    Mailbox Database: Mailbox Database 0784353824
    Error Code: 0x80043629
    Event Xml:
    <Event xmlns="">
        <Provider Name="MSExchangeIS Mailbox Store" />
        <EventID Qualifiers="49198">9877</EventID>
        <TimeCreated SystemTime="2014-02-20T11:58:49.000000000Z" />
        <Security />
        <Data>Mailbox Database 0784353824</Data>
    The frequency of these errors varies and it definitely seems to be related to the amount of traffic. Over the weekend it only occured about 5-10 times a day.  For the past couple of days, it's been pretty constant about every 15 minutes or
    so all day.
    I've looked this up, but I've only found a few posts mentioning similar errors, all relating to earlier versions of Exchange 2010. Supposedly this problem was fixed in one of the rollups to SP1 or SP2, I think.  I never saw these errors, though,
    until the SP3 RU4 rollup.  I haven't heard any complaints from users, but I'm concerned that this might escalate and start causing noticeable searching issues.
    Any ideas would be appreciated.

    Hi Deb,
    We're getting the same error as you on Exchange 2010. We have exchange 2010 and exchange 2013 running in a coexisting environment. Since we applied Service Pack 1 for Exchange 2013, we've had nothing but issues!
    I've tried the rebuild of the index catalogues by following these instructions:
    This failed to resolve the issues too. We've rebooted the server, restarted all the search services and still nothing! We're pulling our hair out here!
    The only thing I haven't tried is the prepareAD commands in this post:
    I'm unable to try this during the day as we have no testing
    environment and would hate to mess the production environment up if this went wrong.
    If you're able to try this during the day, would you let us know how it goes?
    Many thanks,

  • Exchange 2010 SP3, Windows 2008 R2, Windows Installer 5.0

    Windows 2008 R2 uses Windows Installer 5.0
    Windows 2008 R2 is a supported OS for Exchange 2010 SP3
    Why is Windows Installer 5.0 not shown as compatible with Exchange 2010 SP3?
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

    There is no official document about the reason Windows Installer 5.0 is not compatible with Exchange 2010 SP3 for our reference currently. We have to wait for update. Thanks for understanding.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 SP3 upgrade - Event ID 4999 - Address Book Crash

    I just upgraded an Exchange 2010 SP1 CAS server to SP3 - since then anytime an outlook client connects to the CAS server, the Address Book service crash's and event 4999 is logged in App log.  I can reproduce the issue by attempting to create a new
    outlook profile and checking the name against the CAS server.  This crash's the service and the client recieves an error message.  The contents of event ID 4999 is below.  I've tried re-installing the CAS role, re-applying the schema extension
    for SP3.  I've installed all windows updates, enabled logging but I'm not getting anywhere.  If anyone can help with this issue, I would greatly appreicate it.
    Watson report about to be sent for process id: 10168, with parameters: E12, c-RTL-AMD64, 14.03.0123.004, M.E.AddressBook.Service, M.Exchange.Rpc, M.E.R.R.RfriRpcOperationBase.Complete, System.ArgumentException, a3e, 14.03.0123.002.
    ErrorReportingEnabled: True
    That error is followed by a message that the Address Book service has sucessfully started

    For exchange 2010 sp3, there is no article to explain the issue.
    I suggest you run EXBPA aganist your exchange server health check.
    Cara Chen
    TechNet Community Support

  • Exchange 2010 SP3 Update Rollup 6 breaks first OWA login (timezone selection) on SBS 2011

    The Exchange 2010 SP3 Update Rollup 6 broke the OWA for Users who access OWA for the first time and have to set a timezone. They get this error:
    Url: https://xxxxx:443/owa/languageselection.aspx
    User: xxxxxx
    EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=xxxxx
    SMTP Address: xxxxxx
    OWA version:
    Exception type: System.ArgumentNullException
    Exception message: Value cannot be null. Parameter name: value
    Call stack
    Microsoft.Exchange.Clients.Owa.Core.Utilities.RenderDirectionEnhancedValue(TextWriter output, String value, Boolean isRtl)
    ASP.languageselection_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
    System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
    System.Web.UI.Page.Render(HtmlTextWriter writer)
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    This Server is an SBS2011.
    The update broke nothing on a "normal" 2008R2 with exchange 2010.
    Uninstalling RU6 helped but thats obviously not the desired way.
    Removing the RenderTimeZoneSelection() call from languageselection.aspx obviously helped but then there is no timezone dropdown displayed anymore. The timezone dropdown is working normaly in other places like ecp. Afaik this error occours only in the languageselection.aspx
    file which is displayed for "new" OWA users. (Users without a timezone set)
    my workaround was to set the language and timezone for these mailboxes via exchange shell.

    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2010 SP1 Update Rollup 6 to Exchange 2010 SP3

    Hi there,
    I am planning to install Exchange 2010 SP3 next week and after reading some of the related comments on this site I got a little worried.
    Our current Exchange environment consists of the following:
    1 x CAS/HT Server
    2 x Mailbox Server (members of a DAG)
    The OS of the 3 servers is Windows Server 2008 R2 SP1. All servers are running Exchange 2010 SP1 Update Rollup 6.
    The Execution Policies on our Exchange servers are set as follows:
    – CAS/HT Server:
      Scope ExecutionPolicy
      MachinePolicy Undefined
      UserPolicy Undefined
      Process Undefined
      CurrentUser Undefined
      LocalMachine Unrestricted
    – Mailbox Servers:
      Scope ExecutionPolicy
      MachinePolicy Undefined
      UserPolicy Undefined
      Process Undefined
      CurrentUser Undefined
      LocalMachine RemoteSigned
    Please note that we do not have any Group Policies that defined the PowerShell script execution policy.
    I would be very grateful if you (or any of the kind readers) could help me with following questions:
    1- Do I have to change the execution policy on our Exchange servers before installing SP3? If I have to change a policy, what should I change? And how would you recommend I should do this?
    2- After installing SP3 on a server, can I install the latest rollup update on this server before moving to the next server? For example, can I do the following:
      i. Install SP3 followed by RU 5 on the CAS/HT server -> Apply the our custom settings
      ii. Install SP3 followed by RU 5 on the first mailbox server
      iii. Install SP3 followed by RU 5 on the second mailbox server
    Many thanks,

    Hi Amit,
    Many thanks for the swift reply.
    That's correct.  We didn't set the Powershell execution policy via Group Policy.  We only configured the execution policy of "LocalMachine" to "Unrestricted" on the CAS/HT server using the "Set-ExecutionPolicy" command on the server.
    The mailbox servers' execution policies have not been changed and are set to those values by default.
    I must admit, I go event more confused when I read the "" and "" articles.
    But it looks like I shouldn't worry as our current Powershell execution policies shouldn't affect the upgrade. Right?

Maybe you are looking for