Exchange 2010 rollup

Dear all,
I am new to exchange and i have upgraded my exchange 2010 server SP1 to SP3 14.3.123.4. Do I need to download all below rollups manuanly and install one by one ? Or I can go for
Update Rollup 9 for Exchange Server 2010 SP3?
Update Rollup 1 for Exchange Server 2010 SP3
14.3.146.0
5/29/2013
KB2803727
Update Rollup 2 for Exchange Server 2010 SP3
14.3.158.1
8/13/2013
KB2866475
Update Rollup 3 for Exchange Server 2010 SP3
14.3.169.1
11/25/2013
KB2891587
Update Rollup 4 for Exchange Server 2010 SP3
14.3.174.1
12/10/2013
KB2905616
Update Rollup 5 for Exchange Server 2010 SP3
14.3.181.6
2/25/2014
KB2917508
Update Rollup 6 for Exchange Server 2010 SP3
14.3.195.1
5/23/2014
KB2936871
Update Rollup 7 for Exchange Server 2010 SP3
14.3.210.2
8/26/2014
KB2961522
Update Rollup 8-v2 for Exchange Server 2010 SP3
14.3.224.2
12/12/2014
KB2986475
Update Rollup 9 for Exchange Server 2010 SP3
14.3.235.1
3/17/2015
KB3030085
Many thanks,
MS

No. UR 9 is cumulative, so if you just install it, the rest will be covered.

Similar Messages

Exchange 2010 Rollup 2 SP3 update cannot find installation package exchangeserver.msi file on SBS 2011... NEED HELP!!!

Hello,
I am running a windows SBS 2011 standard system and there was currently an update for Exchange 2010 Rollup 2 Service Pack 3 and it keeps failing. It says that it cannot find the installation package (exchangeserver.msi) and it is looking for it
in E:\Software\Exchange2010-SP3-x64\ folder but there never was this folder. There is only an Exchange2010-SP3-x64.exe file.
The only exchangeserver.msi file that I find on the server any where is in C:\ProgramFiles\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1 but it won't accept it (says not authorized for this update or something alike).
Please help. It is currently causing issues with email. Some of the features are not working because it says exchange is currently under maintenance.
Any suggestions would be greatly appreciated. Thank you.

Susan you are correct: After I installed Exchange 2010 SP3, I deleted the msi just to "clean up' my hard disk... While trying to install Rollup 2 for SP3, the installer is trying to find it. I downloaded the installer, used 7-zip to get
the msi and I pointed the installer to it when asked.
The installation failed 3 times...
NOTE: I was using WSUS to install the Rollup: I downloaded the Rollup installer and I executed: I could see where the installer was hanging up! First it asked me to stop an SBS service and something else (sorry I do not remember), I stopped
the services and installation continued. Then it asked me for more files from the SP3 installation which I found on the installation folder that I created with 7-zip. I copied to the path that the installer was looking and installation finished
(finally!)...
NOTE 2: If you have any firewall appliance that denies Internet access to un-authenticated requests, you better turn that rule off because the installer accesses the internet (not sure why - probably for Dot Net assemblies)...
Susan THANKS for all your help to the community! You have helped so much!
All the Best
Constantine

Outlook Client Issues following Exchange 2010 Rollup 8

Update Rollup 8 For Exchange 2010 SP3 (KB2986475) was applied to our Exchange server last night.
All appears to be fine, but users are having all kind of trouble using the Outlook Client to connect to their mailboxes.
Randomly they can't view certain folders (Inbox/Sent Items). Can no longer save to their Calendars. Errors relating to permissions and Outlook notifications?!?!?!?!
This is ONLY when using the Outlook Client - webmail works fine.
There are also no issues when running Outlook in safe mode.
Any advice would be very much appreciated.
Thanks
David

The following has been posted onto the Exchange team site:
http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx
Update 12/10/2014:
An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update until the
new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.
The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will publish
further updates to this blog post regarding RU8.
This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 Rollup 6

I have a (2) server DAG with (9) databases, including Public Folders. The databases are all mounted on Server1. Do I upgrade Server2 first and then move the database copies from Server1 to Server2, then upgrade Server1. Or upgrade
Server2, leave the DB's on Server1 but put them in maintenance mode and run the upgrade. Just trying to get the process correct. Thanks

So I ran the rollup on "Server2", since all the active DB's were mounted on "Server1". This is the results:
1) In the EMC it still shows "Server2" at the same "old" version level, which is Version 14.3 (Build123.4). It's not reflecting the rollup 6 version, even after refreshing. However, the installation went fine and I rebooted the server.
I haven't upgraded "Server1" yet.
2) One of the databases (the largest) database copies went "failed" and never would resume. I had to suspend and then reseed. That's going to take awhile.
Once the reseed completes I will work on upgrading Server1, just wondering why Server2 isn't showing that it's been upgraded to the latest version.
Any thoughts?

Outlook 2010 Profiles Not Creating with Exchange 2010 Backend

In an enterprise environment. Issue has been replicated on multiple Windows Terminal Servers, with multiple accounts.
With multiple accounts have recreated the user profiles from scratch, and launched outlook 2010. The profile does not autocreate, it was working in production about a week ago. Windows Updates were applied for December 2014.
Does anyone know if a Local Windows Client side patch would cause Outlook 2010 not to resolve a profile correctly. Could this be the outlook mapi rpc issue that was part of RU8. Have searched several hundred artciles on this on google and twitter
in the last weeks time frame and cannot find anywhere online that lists excatly what a user experiences when RU8 fails. Have not heard back from the Exchange administrator if RU8 was deployed. There are also multiple Windows Updates for December
2014 for Office that may have caused the problem.
Might be having exactly the same issue as this guy.
http://exchangetips.us/2014/12/exchange-users-unable-to-connect-with-outlook-2010/
Microsoft did pull/release a version #2 of an exchange patch in December which might be the root cause.
https://nakedsecurity.sophos.com/2014/12/12/microsoft-pulls-patch-tuesday-fix-outlook-cant-connect-to-exchange/
not sure if we are we running “Exchange Server 2010 SP3 Update Rollup 8”
–version #1 or version #2
http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx
https://social.technet.microsoft.com/Forums/en-US/1f77b07b-8330-453c-bc4e-4322d21d1aa3/outlook-error-code-0x800040050x800040050x000501?forum=exchangesvrclientslegacy
http://www.anywherexchange.com/2014/12/mapi-http-support-now-available-for.html
http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx
http://windowsitpro.com/blog/exchange-2010-sp3-ru8-withdrawn-due-bug-mapi-rpc-layer
http://www.reddit.com/r/sysadmin/comments/2oxfdf/microsoft_exchange_2010_sp3_ru8_breaks_outlook/?utm_medium=twitter&utm_source=twitterfeed
http://blogs.technet.com/b/exchange/archive/2014/12/09/exchange-releases-december-2014.aspx
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8?forum=exchange2010
https://social.technet.microsoft.com/Forums/en-US/8a66406b-2047-4108-bd5a-9a178114c424/exchange-2010-sp3-rollup-8-and-rollup-7?forum=smallbusinessserver2011essentials

There are known issues with Outlook connections if you are using Exchange 2010 SP3 UR8 (as you have found). You can check which update you are running by going to
Control Panel/Uninstall a Program, then click the
View Installed Updates selection (upper left). Your
Exchange Server 2010 - Software Updates will show a definite difference between UR8 and UR8V2. To be safe, I'd fully remove UR8 and install UR8V2 after a system restart.

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:
http://www.microsoft.com/en-us/download/details.aspx?id=36768
See this thread for more ideas about rolling back:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8
Update:Microsoft has released version 2 of SP3 RU8 today. The link should be live soon.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

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.

After Exchange 2010 SP3 and rollup 4 update conditional formatting causes messages not to appear in Outlook 2010

Hi,
after updating to exchange 2010 sp 3 from sp 2 and also updating to rollup 4, users who use conditional formatting cannot see new message unless they close and reopen Outlook.
If you decide to change the font colour for unread messages, the messages do not appear in Outlook but a pop up indicates that a new message has arrived.
If you reopen Outlook, the unread messasge appears.
remove the conditional formatting and no issue with viewing unread messages as they arrive.
running Outook version 14.0.7106.5003
is this a known issue? a user who never used conditional formatting will experience this right away.
Thanks,
rudif

Hi rudif,
If the issue only happens to users who use conditional formatting and OWA can work well for all mailbox, I think the issue should be in client side.
Please try to reset View then set the conditional formatting back to have a try. If the issue continues, please try to recreate the Outlook profile to check whether the issue persists. Also try restarting Outlook in Safe mode by running
Outlook /safe switch.
Thanks,
Winnie Liang
TechNet Community Support

Install or not install - exchange 2010 update rollup 4 sp3

Hi guys!
We have Exchange2010 SP3 with update rollup 2.
Users with IE11 are having problems with OWA opening only in light mode. I have read on the internet that CU 4 solves this problem but on the other hand this CU makes additional problems with outlook 2007 clients.
Some of the comments of this issues from other companies are: In Outlook 2007 if you choose to change the current view with Arrange By 'Categories' the following is noticed: - Items that you set unread or read are not changed until you refresh the view
- If you open an unread email by doubleclicking, it's status stays unread until you refresh the view. - New mail items are not automatically seen until refresh. This is a very annoying issue, and our servicedesk already received a lot of calls for this issue
Is there any workaround to fix IE11 OWA light mode and not corrupt Outlook 2007 user clients?
bostjanc

It happens as MSIE token is removed from the user-agent string in IE11. This made the Exchange team provide an update on the Exchange side to fix this issue. The workaround is to use Compatibility Mode in IE11 for OWA. As for the fixes:
2003: Use workaround, no fix will be released
2007: Use workaround until a fix is released, currently a fix is tentatively planned for release in E2007 SP3 RU12
2010: Install
E2010 SP3 RU3 or use workaround
2013: Install
E2013 CU3 or use workaround
O365: Issue is already fixed, no action is required
Thanks,
Jason
Jason Apt, Microsoft Certified Master | Exchange 2010
My Blog

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:
Request
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: 14.3.195.1
Exception
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)
Microsoft.Exchange.Clients.Owa.Core.LanguageSelection.RenderTimeZoneSelection()
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.

Hello,
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,
M

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 "http://support.microsoft.com/kb/2668686" and "http://support.microsoft.com/kb/2810617" articles.
But it looks like I shouldn't worry as our current Powershell execution policies shouldn't affect the upgrade. Right?

Exchange 2010 SP3 Rollup Update 6

Our Exchange environment is currently on Exchange 2010 SP3 RU3 and the Forefront Protection 2010 for Exchange server version is 11.0.713.0 (Rollup 3).
We planning to upgrade Exchange servers and install Exchange 2010 SP3 RU6, question which I have is it Mandatory to upgrade the Forefront Protection 2010 for Exchange server version is 11.0.727.0 (Rollup 4) before we install Exchange 2010 SP3 RU6 on the
Exchange servers.
Thanks,
AJ

Thanks Adam for the prompt response and yes I recall these cmdlets to disable and there is a similar cmdlet to enable it. Also after Exchange 2010 SP2 after some RU there is no need to disable FPE before installing RU however it is recommended to disable
it.
If you refer the comments section mentioned in the blog below it talks about it:-
http://blogs.technet.com/b/exchange/archive/2014/05/27/released-update-rollup-6-for-exchange-2010-service-pack-3.aspx
If you read the comment posted by James Knoch posted on this blog which is as below,
SP3 & the Rollup Updates are not supposed to require you to disable Forefront anymore, but it doesn't hurt to be safe and disable/enable it anyways. Make sure you are running Forefront Rollup 4 (http://support.microsoft.com/kb/2619883)
& the latest security update (http://www.microsoft.com/en-us/download/details.aspx?id=41836).
Above stated confused me a bit, is it mandatory to upgrade Forefront or it is NOT.
Thanks,
AJ

Error 1603 when installing Rollup 4 for Exchange 2010 SP2

Hi There,
I have began upgrading our Exchange servers to Rollup 4 for Exchange 2010 SP2 last week and the first 3 servers all successfully installed it without any problems. However I have hit a problem with my 4th server.
I am receiving the 'common' error 1603 in my Application log and I have already ran through many potential fixes to this problem on various posts on this and other forums, but to no avail.
I have tried the following without success:
Turning off UAC
Running from elevated CMD prompt
Running from elevated Powershell command
Removing and re-adding "Exchange Trusted Subsystem" from the Administrators group
Re-downloading the RU4 install package to the local disk on the server
Adding more RAM and CPU resources
I have watched the installation process and it seems to update of the native assembly files and comes to the "Starting Services" process, with which it appears to do fine as I have watched the Services starting within Server Manager while this has been running,
but then all of a sudden just begins "Rolling back actions".
The only difference with this server to the others is the fact that a colleague of mine had to recover this server within the last 6 months and ran the Setup /m:RecoverServer command
to do so, could this have anything to do with it?
I have installed Exchange 2010 Service Pack 2 on this server since the recovery though.
I am running out of ideas so any help would be greatly appreciated.

skippy-85,
Any updates on this Issues?
In case if the issue stands
resolved, Please mark Solution for this Thread and close this.
In case if you still have
the issue with the RU4 installation do let us know!
Thanks
Exchangeexperts.in ~ ( Exchange | 2003/2007/2010/E15(2013)) ~Mark this if Helpful~ This Information is provided "AS IS" and confers no Rights!!

Exchange 2010: Installing Server Rollup

Environment: (2) Servers in a DAG with (9) databases, all db's residing on Server1. I have already patched Server2. What is the proper procedure for installing the rollup on Server1? Not all the databases have copies on Server2,
i.e. public folders and a couple others.
Sorry, I didn't see a forum for Exchange 2010.
Thanks,

Hi,
To install update on DAG members, you can look at the article provided by Andy.
If users want to access public folders during the process of installing the rollup on Server1, you need to create a public folder database on Server2 and set this new public folder database as default public folder database for all mailbox databases.
Before you install update on Server1, you need to move active database to Server2 first.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2010 SP3 Rollup 8 and Rollup 7

Hi
I have a customer with a Small Business Server 2010 with Exchange 2010 SP3.
The Customer installed updates on the server 10/12/2014 where Rollup 8 for Exchange was included.
After that the Customer has a lot of problems with connection from Outlook to Exchange and they phoned us.
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
The customers still has problems with connection from Outlook.
One of the errors:
From: Systemadministrator
Sent: 15. december 2014 10:54
Subject: Unable to be delivered: Test
This message did not reach one or all of the recipients.
      Subject:     Test
      Sent:15-12-2014 10:54
Unable to deliver to the following recipient(s):
      MST the 15-12-2014 10:54
            This message could not be sent. Try to send the message again later, or contact the networkadministrator. Error [0x80004005-00000000-00000000].
Another error in Application log:
Log Name:      Application
Source:        MSExchange Common
Date:          16-12-2014 08:09:00
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <servername>.<domain>.local
Description:
Watson report about to be sent for process id: 9340, with parameters: E12, c-RTL-AMD64, 14.03.0224.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.ViewCache.IsRowWithinUnreadCache, System.IndexOutOfRangeException, 8e38, 14.03.0224.001.
ErrorReportingEnabled: False
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="16388">4999</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-16T07:09:00.000000000Z" />
    <EventRecordID>174679</EventRecordID>
    <Channel>Application</Channel>
    <Computer><servername>.<domain>.local</Computer>
    <Security />
</System>
<EventData>
    <Data>9340</Data>
    <Data>E12</Data>
    <Data>c-RTL-AMD64</Data>
    <Data>14.03.0224.001</Data>
    <Data>M.E.RpcClientAccess.Service</Data>
    <Data>M.E.RpcClientAccess.Handler</Data>
    <Data>M.E.R.H.ViewCache.IsRowWithinUnreadCache</Data>
    <Data>System.IndexOutOfRangeException</Data>
    <Data>8e38</Data>
    <Data>14.03.0224.001</Data>
    <Data>False</Data>
    <Data>
    </Data>
</EventData>
</Event>
What to do ?
Best Regards
John B

Hi John,
Please type
outlook /safe in RUN to start Outlook in safe mode and then check if this issue still exists. Meanwhile, please run Exchange Best Practices Analyzer and check if find relevant issues.
à
This message could not be sent. Try to send the message again later, or contact the networkadministrator.
Error [0x80004005-00000000-00000000].
The issue typically occurs if send messages to a large number of recipients.
When this issue occurred, did you check if send message successfully via OWA?
à
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
Did you mean this article:
Exchange releases: December 2014?
à
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
From the Event ID 4999, I noticed that point to
14.03.0224.001, it should mean the old Exchange Server 2010 SP3 Update Rollup 8. From above
mentioned article (Exchange releases: December 2014),
Exchange Server 2010 SP3 Update Rollup 8 has been re-released to the Microsoft download center resolving a regression discovered in the initial release. The update RU8 package
corrects the issue which impacted users connecting to Exchange from Outlook. The updated RU8 package is version number 14.03.0224.002. Just a confirmation, did you
reinstall that re-released Exchange Server 2010 SP3 Update Rollup 8? Any difference?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange 2010 rollup

Similar Messages

Maybe you are looking for