Home
%3CLINGO-SUB%20id%3D%22lingo-sub-591927%22%20slang%3D%22en-US%22%3EReleased%3A%20Update%20Rollups%20for%20Exchange%202007%20%26amp%3B%20Exchange%202010%20and%20Security%20Updates%20for%20Exchange%202013%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-591927%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22alert%22%3E%3CSTRONG%3EUpdate%208%2F14%2F13%3C%2FSTRONG%3E%3A%20Due%20to%20an%20issue%20with%20the%20Exchange%202013%20Security%20Update%20installation%20process%2C%20the%20Exchange%202013%20updates%20have%20been%20removed%20from%20the%20Download%20Center.%20For%20more%20information%2C%20please%20see%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fexchange%2Farchive%2F2013%2F08%2F14%2Fexchange-2013-security-update-ms13-061-status-update.aspx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EExchange%202013%20Security%20Update%20MS13-061%20Status%20Update%3C%2FA%3E.%3C%2FP%3E%20%20%3CP%3EToday%2C%20Exchange%20Servicing%20released%20several%20updates%20for%20the%20Exchange%20product%20line%20to%20the%20Download%20Center%3A%3C%2FP%3E%20%20%3CUL%3E%20%20%20%3CLI%3EUpdate%20Rollup%2011%20for%20Exchange%20Server%202007%20SP3%3C%2FLI%3E%20%20%20%20%3CLI%3EUpdate%20Rollup%207%20for%20Exchange%20Server%202010%20SP2%3C%2FLI%3E%20%20%20%20%3CLI%3EUpdate%20Rollup%202%20for%20Exchange%20Server%202010%20SP3%3C%2FLI%3E%20%20%20%20%3CLI%3EExchange%20Server%202013%20RTM%20CU1%20MSRC%20Security%20bulletin%20MS13-061%3C%2FLI%3E%20%20%20%20%3CLI%3EExchange%20Server%202013%20RTM%20CU2%20MSRC%20Security%20bulletin%20MS13-061%3C%2FLI%3E%20%3C%2FUL%3E%20%20%3CP%20class%3D%22note%22%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3A%20Some%20of%20the%20following%20KB%20articles%20may%20not%20be%20available%20at%20the%20time%20of%20this%20article%E2%80%99s%20publishing.%3C%2FP%3E%20%20%3CH2%20id%3D%22toc-hId-1760083002%22%20id%3D%22toc-hId-1820318290%22%3EExchange%202007%20Rollups%3C%2FH2%3E%20%20%3CP%3EThe%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D39803%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3EExchange%202007%20SP3%20RU11%20update%3C%2FSTRONG%3E%3C%2FA%3Econtains%20two%20fixes%20in%20addition%20to%20the%20changes%20for%20MS13-061.%20For%20more%20details%2C%20including%20a%20list%20of%20fixes%20included%20in%20this%20update%2C%20see%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2873746%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%202873746%3C%2FA%3Eand%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fsecurity%2FBulletin%2FMS13-061%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EMS13-061%20security%20bulletin%3C%2FA%3E.%20We%20would%20like%20to%20specifically%20call%20out%20the%20following%20fixes%20which%20are%20included%20in%20this%20release%3A%3C%2FP%3E%20%20%3CUL%20class%3D%22nobullet%22%3E%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2688667%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2688667%3C%2FSTRONG%3E%3C%2FA%3EW3wp.exe%20consumes%20excessive%20CPU%20resources%20on%20Exchange%20Client%20Access%20servers%20when%20users%20open%20recurring%20calendar%20items%20in%20mailboxes%20by%20using%20OWA%20or%20EWS%3C%2FLI%3E%20%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2852663%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2852663%3C%2FSTRONG%3E%3C%2FA%3EThe%20last%20public%20folder%20database%20on%20Exchange%202007%20cannot%20be%20removed%20after%20migrating%20to%20Exchange%202013%26nbsp%3B%3C%2FLI%3E%20%3C%2FUL%3E%20%20%3CH2%20id%3D%22toc-hId--792073959%22%20id%3D%22toc-hId--731838671%22%3EExchange%202010%20Rollups%3C%2FH2%3E%20%20%3CP%3EThe%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D39863%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3EExchange%202010%20SP2%20RU7%20update%3C%2FSTRONG%3E%3C%2FA%3Econtains%20the%20changes%20for%20MS13-061.%26nbsp%3B%20For%20more%20details%2C%20see%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fsecurity%2FBulletin%2FMS13-061%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EMS13-061%20security%20bulletin%3C%2FA%3E.%3C%2FP%3E%20%20%3CP%3EThe%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D39835%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3EExchange%202010%20SP3%20RU2%20update%3C%2FSTRONG%3E%3C%2FA%3Econtains%20fixes%20for%20a%20number%20of%20customer-reported%20and%20internally%20found%20issues%2C%20as%20well%20as%2C%20the%20changes%20for%20MS13-061.%20For%20more%20details%2C%20including%20a%20list%20of%20fixes%20included%20in%20this%20update%2C%20see%20%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2866475%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB%202866475%3C%2FA%3Eand%20the%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Fsecurity%2FBulletin%2FMS13-061%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EMS13-061%20security%20bulletin%3C%2FA%3E.%20We%20would%20like%20to%20specifically%20call%20out%20the%20following%20fixes%20which%20are%20included%20in%20this%20release%3A%3C%2FP%3E%20%20%3CUL%20class%3D%22nobullet%22%3E%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2861118%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2861118%3C%2FSTRONG%3E%3C%2FA%3EW3wp.exe%20process%20for%20the%20MSExchangeSyncAppPool%20application%20pool%20crashes%20in%20an%20Exchange%20Server%202010%20SP2%20or%20SP3%20environment%3C%2FLI%3E%20%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2851419%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2851419%3C%2FSTRONG%3E%3C%2FA%3ESlow%20performance%20in%20some%20databases%20after%20Exchange%20Server%202010%20is%20running%20continuously%20for%20at%20least%2023%20days%3C%2FLI%3E%20%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2859596%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2859596%3C%2FSTRONG%3E%3C%2FA%3EEvent%20ID%204999%20when%20you%20use%20a%20disclaimer%20transport%20rule%20in%20an%20environment%20that%20has%20Update%20Rollup%201%20for%20Exchange%20Server%202010%20SP3%20installed%3C%2FLI%3E%20%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2873477%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2873477%3C%2FSTRONG%3E%3C%2FA%3EAll%20messages%20are%20stamped%20by%20MRM%20if%20a%20deletion%20tag%20in%20a%20retention%20policy%20is%20configured%20in%20an%20Exchange%20Server%202010%20environment%3C%2FLI%3E%20%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2860037%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2860037%3C%2FSTRONG%3E%3C%2FA%3EiOS%20devices%20cannot%20synchronize%20mailboxes%20in%20an%20Exchange%20Server%202010%20environment%3C%2FLI%3E%20%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fsupport.microsoft.com%2F%3Fid%3D2854564%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3E2854564%3C%2FSTRONG%3E%3C%2FA%3EMessaging%20Records%20Management%202.0%20policy%20can't%20be%20applied%20in%20an%20Exchange%20Server%202010%20environment%3C%2FLI%3E%20%3C%2FUL%3E%20%20%3CH2%20id%3D%22toc-hId-950736376%22%20id%3D%22toc-hId-1010971664%22%3EExchange%20Server%202013%3C%2FH2%3E%20%20%3CP%3EMS13-061%20is%20the%20first%20security%20update%20released%20for%20Exchange%20Server%202013%20utilizing%20the%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fexchange%2Farchive%2F2013%2F02%2F08%2Fservicing-exchange-2013.aspx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Enew%20servicing%20model%3C%2FA%3E.%26nbsp%3B%20MS13-061%20is%20available%20as%20a%20security%20update%20for%3A%3C%2FP%3E%20%20%3CUL%20class%3D%22nobullet%22%3E%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D39910%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3ESecurity%20Update%20for%20Exchange%20Server%202013%20RTM%20CU1%3C%2FSTRONG%3E%3C%2FA%3E%3CSTRONG%3E%20%3C%2FSTRONG%3E%3C%2FLI%3E%20%20%20%20%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D39904%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSTRONG%3ESecurity%20Update%20for%20Exchange%20Server%202013%20RTM%20CU2%3C%2FSTRONG%3E%3C%2FA%3E%3C%2FLI%3E%20%3C%2FUL%3E%20%20%3CP%20class%3D%22note%22%3E%3CSTRONG%3EImportant%3C%2FSTRONG%3E%3A%20If%20you%20have%20previously%20deployed%20CU2%2C%20you%20must%20ensure%20you%20are%20running%20build%20712.24%20in%20order%20to%20apply%20the%20security%20update.%20For%20more%20information%20about%20build%20712.24%2C%20please%20see%20%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fexchange%2Farchive%2F2013%2F07%2F29%2Fnow-available-updated-release-of-exchange-2013-rtm-cu2.aspx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ENow%20Available%3A%20Updated%20Release%20of%20Exchange%202013%20RTM%20CU2%3C%2FA%3E.%3C%2FP%3E%20%20%3CP%3E%3CSPAN%20class%3D%22author%22%3E%3CA%20href%3D%22http%3A%2F%2Fblogs.technet.com%2Fb%2Fexchange%2Farchive%2F2005%2F08%2F25%2Fross-smith-iv-s-biography.aspx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ERoss%20Smith%20IV%3C%2FA%3E%3C%2FSPAN%3E%20%3CBR%20%2F%3EPrincipal%20Program%20Manager%20%3CBR%20%2F%3EExchange%20Customer%20Experience%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-591927%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202007%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eexchange%202010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esetup%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Update 8/14/13: Due to an issue with the Exchange 2013 Security Update installation process, the Exchange 2013 updates have been removed from the Download Center. For more information, please see Exchange 2013 Security Update MS13-061 Status Update.

Today, Exchange Servicing released several updates for the Exchange product line to the Download Center:

  • Update Rollup 11 for Exchange Server 2007 SP3
  • Update Rollup 7 for Exchange Server 2010 SP2
  • Update Rollup 2 for Exchange Server 2010 SP3
  • Exchange Server 2013 RTM CU1 MSRC Security bulletin MS13-061
  • Exchange Server 2013 RTM CU2 MSRC Security bulletin MS13-061

Note: Some of the following KB articles may not be available at the time of this article’s publishing.

Exchange 2007 Rollups

The Exchange 2007 SP3 RU11 update contains two fixes in addition to the changes for MS13-061. For more details, including a list of fixes included in this update, see KB 2873746 and the MS13-061 security bulletin. We would like to specifically call out the following fixes which are included in this release:

  • 2688667 W3wp.exe consumes excessive CPU resources on Exchange Client Access servers when users open recurring calendar items in mailboxes by using OWA or EWS
  • 2852663 The last public folder database on Exchange 2007 cannot be removed after migrating to Exchange 2013 

Exchange 2010 Rollups

The Exchange 2010 SP2 RU7 update contains the changes for MS13-061.  For more details, see the MS13-061 security bulletin.

The Exchange 2010 SP3 RU2 update contains fixes for a number of customer-reported and internally found issues, as well as, the changes for MS13-061. For more details, including a list of fixes included in this update, see KB 2866475 and the MS13-061 security bulletin. We would like to specifically call out the following fixes which are included in this release:

  • 2861118 W3wp.exe process for the MSExchangeSyncAppPool application pool crashes in an Exchange Server 2010 SP2 or SP3 environment
  • 2851419 Slow performance in some databases after Exchange Server 2010 is running continuously for at least 23 days
  • 2859596 Event ID 4999 when you use a disclaimer transport rule in an environment that has Update Rollup 1 for Exchange Server 2010 SP3 installed
  • 2873477 All messages are stamped by MRM if a deletion tag in a retention policy is configured in an Exchange Server 2010 environment
  • 2860037 iOS devices cannot synchronize mailboxes in an Exchange Server 2010 environment
  • 2854564 Messaging Records Management 2.0 policy can't be applied in an Exchange Server 2010 environment

Exchange Server 2013

MS13-061 is the first security update released for Exchange Server 2013 utilizing the new servicing model.  MS13-061 is available as a security update for:

Important: If you have previously deployed CU2, you must ensure you are running build 712.24 in order to apply the security update. For more information about build 712.24, please see Now Available: Updated Release of Exchange 2013 RTM CU2.

Ross Smith IV
Principal Program Manager
Exchange Customer Experience

90 Comments
Not applicable

Stop releasing these messes. I like my job and you're going to kill it.

Not applicable

@Scott RU11 is Ok, Exchange rollups will always include fixes in previous release.

Not applicable

I understand that the delegate Archive naming problem can be fixed by installing Office 2010 SP2 on the client. I'm not sure if it would only be fixed in combination with UR2 or if the combination "Exchange 2010 SP3 UR1" and "Office 2010 SP2" would also work, but I would like to know that.

Since I do not have the problem (this problem is preventing me from installing UR2, and UR1 before) can someone with this problem maybe confirm that installing Office 2010 SP2 on the client fixes the problem?

Not applicable

Looks like KB2866475 needs the SP3 install files in order to install otherwise you may receive the following error: "The feature you are trying to use is on a network resource that is unavailable".

www.stevieg.org/.../update-rollup-2-for-exchange-2010-sp3-prompts-for-install-files

Not applicable

Any way to see what's included in 2010 SP2 RU7?  The link above only shows

support.microsoft.com/.../2874216

which says that RU7 only contains the MS13-061 security update.  Are there no other included fixes?

Not applicable

@tork247, correct that 2010 SP2 RU7 only contains the MS13-061 security fix on top of what had already been released from SP2 RU1-RU6. There are no other updates included in that particular RU. Customers should consider moving from SP2 to SP3 to obtain additional fixes if necessary.

Not applicable

Hi, we are on Exchange 2007 SP3 RU10. Should I rush to install RU11 to solve the "Remote Code Execution"? Or am I already save with RU10? The other fixes are no issue for us at the moment. Thanks, Chris!

Not applicable

Maybe a little update to technet.microsoft.com/.../ee221180.aspx

Not applicable

@Brian, you wrote "Customers should consider moving from SP2 to SP3 to obtain additional fixes if necessary". Does this mean Exchange 2010 SP2 isn't a fully supported SP anymore?

Not applicable

@elrebib, Exchange 2010 SP2 is supported until April 8th 2014 (See:

support.microsoft.com/.../default.aspx) and customers will continue to receive normal support efforts from Microsoft as defined by the support lifecycle policy (Here:

support.microsoft.com/.../lifepolicy) until that date. We continue to release security updates as necessary for SP2 as is seen here with SP2 RU7.

@chris, if you utilize the WebReady Document viewing feature in OWA we would recommend you apply SP3 RU11 to get the latest fixes to the Oracle Outside In library files which WebReady Document Viewing utilizes. This is what MS13-061 (Here:

technet.microsoft.com/.../ms13-061) is for.

Not applicable

So update 7 is simply a security update and does nothing to fix the problem update 6 introduced with deleting email? What a joke!

Not applicable

@James, that particular issue was first fixed in SP3 RU1 (Here: support.microsoft.com/.../en-us) so an upgrade to SP3 RU1 or SP3 RU2 will correct it. Unfortunately not all changes can span across SP branches depending on the risk and complexity of the change.

Not applicable

Just thought I'd mention this to others. After installing Exchange 2010 SP3 rollup 2, I got a few delivery delayed messages. So I double checked my send connector and my smart host settings had be removed. It was a simple re-setup but I thought I'd let others know of the potential issue.

Not applicable

2010 SP3 RU2 is demanding Setup Files(exchangeserver.msi) for installation. Any ideas other than re-downloading whole 2010 SP3 package? Thanks.

Not applicable

@Deniz Irde, is the machine asking for SP3 bits a Small Business Server by any chance?

Not applicable

Hello,

Since I updated our HT/CAS server with the Exchange 2010 SP3 RU2 I got each hour an event entry for ID 4999 (MSExchange Common):

--------------------------------------------------------------

Watson report about to be sent for process id: 3140, with parameters: E12, c-RTL-AMD64, 14.03.0158.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Parser, M.E.R.PropertyValue.CheckValueTypeOnConstruction, System.ArgumentException, 56ca, 14.03.0158.000.

ErrorReportingEnabled: False

--------------------------------------------------------------

The only thing I found for that was an issue that was addresses Exchange 2010 RTM RU1 support.microsoft.com/.../en-us and Exchange 2010 SP2 RU1 support.microsoft.com/.../2599663

Are these problems back with SP3 RU2 ?

Not applicable

@Brian Day, nope. This is a Windows 2008 R2 Std. Server with Exchange Server 2010 SP3 RU1 Std. Server 6. Server is also PDC&GC even it is not recommended. WSUS is also installed. (The company has a very little budget on IT:-))

Installed configuration is one-server scenario(Client Access, Hub Transport and Mailbox Store roles are on the same machine, UM not installed). SP3 is installed by using the download edition and over an existing SP2 version.

If the history is needed, SQL Server 2008 R2 and ForeFront for Exchange were also installed sometime ago in addition to above. These are currently not exist.

Btw, even it is not supported by MSFT(as far as I know); The Windows Management Framework 3.0 and PS 3.0 is installed. My latest knowledge about the issue is written on blogs.technet.com/.../windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx.

I, first tried to install via WSUS. Error code was 8024002D. After that, I tried to install it manually.

I hope that I've written everything :)

Not applicable

We installed Rollup 7 for Exchange 2010 (KB2874216) and users are reporting issues access mailboxes via OWA. They get a message saying, ""The mailbox you're trying to access isn't currently available. If the problem continues, contact your helpdesk." We are only seeing this issue on servers where we installed the rollup. Anybody seeing this issue after installing the rollup?

Not applicable

@Ketan, how are you installing the rollup? Is it being done from an elevated command prompt? Not a command prompt simply opened by an admin, but one opened "as an admin" when UAC is enabled.

Not applicable

Quoting Graham, 15 Aug 2013 2:27 AM

'Looks like KB2866475 needs the SP3 install files in order to install otherwise you may receive the following error: "The feature you are trying to use is on a network resource that is unavailable".

Would this condition prevent the update from installing correctly via SCCM/WSUS? Everything seems to point to a successful installation (Add/Remove, SCCM), except for the build number in Exchange.

Not applicable

It turns out, we needed to apply the roolup on the internet facing CAS servers first. Once we applied the roolup to our NY servers, OWA started working.

Not applicable

Installing on Internet facing first is not an option. To get OWA proxying back you need to install Exchange 2010 SP3 on all 2010 CAS servers at the same time. At least it's not compatible with Exchange 2010 SP2 CU5v2. We learned the hard way...

Not applicable

@Ketan, that is good to hear. Yes, updating Internet facing sites first has always been a requirement.

Not applicable

After RU 7 exchange 2010 sp2 update the exchange server verision shows 14.2.0347.0 instead of 14.2.375.0

Could you please any one check and confirm which verison number is correct?

social.technet.microsoft.com/.../240.exchange-server-and-update-rollups-build-numbers.aspx

Not applicable

The Exchange 2010 SP3 RU2 doesn't update the "AdminDisplayVersion" in a correct way. After the installation of RU2 it still shows the build number of "14.3.123.4" (SP3)  instead of the correct one "14.3.158.1" (SP3 with RU2).

I proofed this issue in two completly independent Exchange 2010 environments.

For me it looks that the build numbers are not updated in the server registry at "HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv14MailboxRole" or "HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv14ClientAccessRole" or "HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv14HubTransportRole".

Not applicable

@mhess_raynet, correct Exchange 2007 and 2010 RUs never update the AdminDisplayVersion of an Exchange server. Feedback from the community (and lots internally!) helped change this in Exchange 2013 so that CUs do update server versions to make reporting and version detection far easier.

Not applicable

For the AdminDisplayVersion confusion, please check the version of the file <Bin path>ExSetup.exe, which is the exact version that the server is in.

Not applicable

So why does Exchange 2010 need the sp3 files left behind on the box?  No one has stated why this requirement is in place for this update rollup and I don't remember it being that way before?

Also can you so state this in the documentation as a needed prereq for the update?

Not applicable

Hi All,

We have Windows 2008x64 sp2 running Exchange 2007 sp3, no rollups, ForeFront for Exchange. I've been putting it off, and now we're on rollup 11.

Can I just straight to RU11 and more importantly has there been any reported issues?

Thanks.

Not applicable

Hi

after install RU2 for SP3. have problem with owa:

Client Access server "mail.mydomain.com/owa", running Exchange version "14.3.158.1",  is proxying Outlook Web App traffic to Client Access server "mailserver.localdomain.com", which

runs Exchange version "14.2.347.0". To ensure reliable interoperability, the proxying Client Access server needs to be running a newer version of Exchange than the Client Access server it is proxying to. If the proxying Client Access server is running a newer

version of Exchange than the Client Access server it is proxying to, the proxying Client Access server needs to have an Outlook Web App resource folder (for example, "<Exchange Server installation path>)ClientAccessowa8.0.498.0" that contains all the same

versioned resource files as the Client Access server it is proxying to. If you will be running Outlook Web App proxying with mismatched server versions, you can manually copy this resource folder to the proxying Client Access server. After you copy this resource

folder to the proxying Client Access server, you need to restart IIS before proxying will work.

Not applicable

Tried to push rollup 2 to our Exchange 2010 SP3 server this weekend via WSUS, as expected the installation failed.

Not applicable

@sanders: We had the same problem. Some articles state you have to install it on the internet facing first, othes state the opposite. Both options didn't work (copying the files and restarting IIS was also a waste of time).

After some time we decided to uninstall and installed it worldwide on all CAS servers at the same time (less than 100, lost only 1 machine during install).

Looks like CAS proxying also hasn't been tested...

Not applicable

Hey Guys,

I need to apply Exchange 2010 SP2 RU7 to an SP2 hosted environment. Are there any gotchas to apply just an RU to a hosting environment? We do use a portal and I checked with the portal company and they said that they don't test release updates.

Specifically would any default permissions be reapplied (such as permissions on an address book) ?

Thanks,

Robert

Not applicable

Exchange 2010 SP3 UR2 + Outlook 2010 SP1 or SP2 with Outlook 2010 hotfix package august 2013 (support.microsoft.com/.../en-us) is required to solve the archive name issue (delegate archive shows the name of the primary mailbox owner).

Note: this is also an issue with Outlook 2010 and Exchange 2013 CU2. After installing the Outlook 2010 hotfix package I had to delete and create a new Outlook 2010 profile to solve the archive name issue. Outlook Repair Account did not seem to work.

I have not yet been able to test this with Outlook 2013 and Exchange 2013.

Martijn

Not applicable

When you say "as expected" I would check to see if you have the sp3 folder on the server.  Exchange 2010 needs to have access to sp3 folder.  The update should not fail if it has access to this folder location.

Not applicable

... which is not documented nor has ever been necessary.

Not applicable

Update: recreating Outlook profile is not necessary. After installing hotfix en starting Outlook, change is coming in from autodiscover but you have to restart Outlook to see the change.

Martijn

Not applicable

I upgraded 50 servers to Exch 2010 SP3 Rollup 2 and within 2 hours had queues on all MAILBOX ROLE servers (only mailbox roles installed). The MAIL SUBMISISON QUEUE peaks to over 60 and SCOM reports it as critical. Troubleshooted various aspects and could not find any performance, disk, RAM, CPU, latency issues. The PerfMon counter on the Windows Server 2008 R2 servers called "Messages Queued for submission" is growing all the time.  This issue started from SP3 RU2 and we never had queues before. Seems like another bug in RU2 or inherent to SP3 code.

Not applicable

If I wanted to install RU 2 and SP3 at the same time to a CAS Array and DAG. Is it better to install SP3 first across all servers and then go back and install the RU2. Or for each CAS server once I have installed sp3 can I proceed with installing RU2 before I go to the next CAS servers and then subsequequently follow the same process for each DAG member?

Thank you in Advance

Not applicable

@dryred167, that's the way I handle it when I have to go through multiple updates when a Service Pack is included. All servers to the same SP level first, and then install the latest acceptable RU for that SP.