Released: Update Rollups for Exchange 2007 & Exchange 2010 and Security Updates for Exchange 2013

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

Comments (88)
  1. Does this include the GetRoomLists fix that utilized NSPI when no Room Lists were defined?

  2. Juergen says:

    Once again, please stop Security Updates for Exchange 2010 through URs!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  3. @juergen, the established servicing model will continue for the remainder of Exchange 2007 and Exchange 2010's product support lifecycle. We heard the feedback and were able to update Exchange 2013's servicing model to allow us to ship individual security updates, as we have just done here for the first time.

  4. Tracy Ratz says:

    does this correct the signature bug from RU1?


  5. @Casey Tomlinson – We did address an issue with GetRoomList to scope the recipient session using the user's Address list as opposed to the global scope which resulted in high CPU load on AD servers.


  6. @Tracy, yes please refer to the whole list for 2010 SP3 RU2 referred above, . That should then link to KB2859596 which I believe is the item you are asking about.

  7. Steve Mossberg says:

    Brian, are these CU's/RU's getting tested? It appears that new bugs are created with each new fix. We are almost better off not apply the fixes. Any comments?

  8. @Steve, no we blindly release code and let you test it for us. ;) j/k I will defer to the last few Q&A bullets in Ross' previous article here for commentary on testing. Short answer is, absolutely we do.…/e2013-rtm-cu2-issue-public-folder-permissions-loss-after-pf-mailbox-move.aspx

  9. says:

    @Ross / Brian,

    Is this Update Rollup 2 for Exchange 2010 SP3 fixes an issue with Archive mailbox appearance in Outlook (where both Online Archive and Regular mailbox names appear as same)?


  10. @Sadda – yes we did introduce a fix for E2010 SP3 RU2 that addresses the issue where delegate archive show the name of the primary mailbox owner.  However, a client side fix is also required, but I don't have information on when that is shipping.  

  11. says:


    Thanks for your confirmation.

  12. Ziv Rivkis says:

    When attempting to install this update I receive "The feature you are trying to use is on a network resource that is unavailable." When I browse for the resource it is looking for exchangeserver.msi. Ideas? Exchange 2010 SP31RU1 upgrade.

  13. Tim says:

    Exchange 2010 SP3 has ActiveSync redirection issue.  Looks like SP3 RU2 doesn't fix it.  When will it be fixed?

  14. @Tim – yes we did address the issue where EAS devices would get a 403 response instead of being proxied.   However, not all EAS devices will get a redirect.  We are now targeting a known list of supported devices for redirection.  All other devices will be proxied.

  15. Chris says:

    there should be a fix in Ru2 for Exch2010 Sp3 that addresses a problem with granting folder permissions to mail-enabled security groups in a ressource forrest deployment that is not working. What's about that?

  16. @Chris, you'll have to provide additional information. Perhaps a case # for us to refer back to.

  17. Frank says:

    In our environment installing the rollup hangs at the 'copying files' stage. It continues to about 50% and then stalls. I left it there for an hour, but it doesn't continue. Taskmanager also doesn't show any processes using CPU. No virusscanner is installed on the server.

  18. Frank says:

    Addition: it appears no files have been actually copied yet in the 'copying new files' stage. Most recent files in the V14bin folder have a date of 17-4-2013.

  19. Frank says:

    Forgot to mention in previous posts:  Exchange 2010 SP3 RU2

  20. You can contact me at the -at- to @) if you need to

    Fellow SBS mvp Tero Leskinen patching a SBS 2011 (Exchange 2010 sp3 ur2) also reports that he got a prompt for exchangeserver.msi during the install as well.

  21. Small question – Why are the file names of the security update for Exchange 2013 CU1 and CU2 identical? People may be under the assumption they're identical (they aren't)

  22. Frank says:

    @Susan: I didn't get that prompt, it just sits there (I didn't use the windows update setup, but downloaded the standalone setup).

    However, I've my server up and running again. I took the plunge and killed the MSIEXEC process (cancel in the setup window didn't work). I reverted the services that were set to disabled back to their original value and Exchange started fine again and outlook is able to connect. Fingers crossed and I will open a support case tomorrow on why this is happening.

  23. Mike DiVergilio says:

    Installed this updated on 2 servers running Exchange 2013 CU1 and in both instances the updated remove the Microsoft Exchange Search Host Controller and replaced it with a service called Host Controller for Exchange which does not start. I removed the server from the DAG, removed the MBX role and then reinstalled Exchange CU1. I then reapplied the update to confirm and in this instance as well, the service was removed.

  24. Mike DiVergilio says:


    Installed this updated on 2 servers running Exchange 2013 CU1 and in both instances the update removed the Microsoft Exchange Search Host Controller and replaced it with a service called Host Controller for Exchange which does not start. I removed the server from the DAG, removed the MBX role and then reinstalled Exchange CU1. I then reapplied the update to confirm and in this instance as well, the service was removed.

  25. Tim says:

    After updating Exchange 2010 SP3 RU2 from Exchange 2010 SP3 on Windows 2008 R2, the MS Exchange information store service is not started and the following event log error occurs.  Is it a known issue?  When I restarts MS Exchange AD topology services, all Exchange services are back to normal. Thanks!

    Log Name:      Application

    Source:        MSExchangeIS

    Date:          13/08/2013 10:45:22 PM

    Event ID:      5003

    Task Category: General

    Level:         Error

    Keywords:      Classic

    User:          N/A



    Unable to initialize the Information Store service because the clocks on the client and server are skewed. This may be caused by a time change either on the client or on the server, and may require a restart of that computer. Verify that your domain is correctly configured and  is currently online.

    Event Xml:

    <Event xmlns="…/event">


       <Provider Name="MSExchangeIS" />

       <EventID Qualifiers="49158">5003</EventID>




       <TimeCreated SystemTime="2013-08-14T02:45:22.000000000Z" />




       <Security />






  26. John S2 says:

    Will there be any upgrade issues going to Exchange 2013 CU3, when released if we install the security fix, ala traditional interim updates?

  27. Tim says:

    It looks like VM and ESXi time different issue. All services are back to normal after adjusting the time.

  28. wwwojtek says:

    I was planning to implement RU2 for Exchange 2010SP3 after the holiday, but the presence of security update in RU2 cause I do not know what to do…

  29. Hans says:

    Why isn't there a seperation between fixpacks and security updates? This doesn't make sense, especially when you know that a lot of this fixpacks cause only trouble.

  30. RM says:

    Having the same problem Mike DiVergilio mentioned above in CU2v2…

    Removing the update did not fix it … now i'm at loss … any tips on how to fix this without reinstalling exchange on the server?

  31. Security Update for Exchange Server 2013 RTM CU2 (v2) says:


    I had build 712.24 on 3 servers and deployed the patch. On all 3 servers I cannot do searches anymore. Not 100 % sure its the exchange update causing this because i installed the Aug 2013 security updates at once, after that the service "host controller service for Exchange" doesn't start anymore. Is there already a fix available?

    Uninstall of the exchange hotfix doesn't solve the issue.


  32. Daniel Be says:

    Host Controller Service won't start after Exchange 2013 security update:

    I noticed that the key HKLMSOFTWAREMicrosoftSearch Foundation for ExchangeDataDirectory is empty.

    If I fill it with "C:Program FilesMicrosoftExchange ServerV15BinSearchCeresHostControllerData" the service starts.

    But this is only a dirty trial & error fix found by me, so take care!

  33. Regarding KB, for your convenience I've created a small script which performs the workaround…/fix-for-ms13-061-breaking-exchange-2013

  34. The search host controller issue has been addressed in…/2879739

  35. Garry Trinder says:

    Is the disclaimer(transport rule) handeled in the Exchange 2010 SP3 RU2 that was a problem with Exchange 2010 SP3 RU1?

  36. princessid says:

    Having also the issue with the prompt, reffering to "exchangeserver.msi". We are running Exchange 2010 SP3, RU1. Any comment on this?

  37. If you're getting a prompt for the Exchange 2010 source files you only need to extract the original setup files for that service pack (eg Exchange 2010 SP3) back to the location its prompting you for, or point the installer to another location where those files exist.

  38. Rob D. says:

    The links to the Exchange 2013 updates (CU1 and CU2) are dead.  I guess this update has been pulled?  From this blog post as well as here:…/ms13-061  


  39. zumarek says:


    Your statement about testing on general public seems the best information so far.

    Unfortunately since certain person left MS quality of updates has been less than

    desired. And please spare us comments about how complicated Exchange is.

    Bring back SS (at least he was able to get Windows 7 program running).

  40. Uellington says:

    Off topic: There are plan to support SRS (Sender Rewriting Scheme), in Exchange?

  41. Uellington says:

    Are there plans to support SRS (Sender Rewriting Scheme) , on Microsoft Exchange?

  42. zumarek says:

    Brian so after you apply hotfix in your test enviro you do not use Get-MailboxDatabaseCopyStatus … to see ?

    Can you confirm/deny or otherwise ?

  43. Scott says:

    We are on 2007 SP3 .. windows updates show RU11 and RU8v2 available. Does RU11 include the updates from RU8v2 or do I need to install RU8v2 first and then RU11?

  44. Mike White says:

    For the Exchange 2007 sp3 update rollup 11, the download center (…/details.aspx) does not list Windows 2003 R2 as a supported operating system:

    "Supported Operating System

    Windows 7 Professional 64-bit, Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows Server 2008 Standard, Windows Server 2012"

    Was this an oversight?

  45. SteveD says:

    I have the same question as Anna – the issue with Ex 2010 SP3 UR1 where messages get sent to the poison queue – has this been fixed? We have an interim update in place for a soft-delete issue with voicemail messages (from SP3) and have been unable to apply UR1 because of the disclaimer/poison message problem. At the time we were offered an interim update for this issue that we could apply after installing UR1, but the business was not prepared to accept the risk.

  46. Phil says:

    @Anna and SteveD

    From the blog post:

    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

    Yes, it's fixed.

  47. Korbyn says:

    Future request, can you post the updates for the various Exchange versions separately, so the issues with Exchange 2013 aren't mixed up with 2010's.  And perhaps you can update the posting to mention that you've pulled the E2013 security patches and "If" you've installed them, here's the KB to go fix the issue instead of having to find it buried in the middle of all the other minutia. Thanks.

  48. Korbyn says:

    I see you were updating the page as I was typing, awesome.

  49. Harcuvar says:

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

  50. says:

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

  51. says:

    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?

  52. Graham says:

    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".…/update-rollup-2-for-exchange-2010-sp3-prompts-for-install-files

  53. tork247 says:

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

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

  54. @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.

  55. Chris says:

    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!

  56. says:

    @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?

  57. @elrebib, Exchange 2010 SP2 is supported until April 8th 2014 (See:…/default.aspx
    ) and customers will continue to receive normal support efforts from Microsoft as defined by the support lifecycle policy (Here:…/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:…/ms13-061
    ) is for.

  58. james says:

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

  59. @James, that particular issue was first fixed in SP3 RU1 (Here:…/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.

  60. Matt McLaughlin says:

    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.

  61. says:

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

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

  63. mhess_raynet says:


    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…/en-us and Exchange 2010 SP2 RU1…/2599663

    Are these problems back with SP3 RU2 ?

  64. says:

    @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…/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 :)

  65. ketan says:

    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?

  66. @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.

  67. Chris_TX says:

    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.

  68. ketan says:

    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.

  69. PissedOffAdmin says:

    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…

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

  71. bala says:

    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?…/

  72. mhess_raynet says:

    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 "" (SP3)  instead of the correct one "" (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".

  73. @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.

  74. says:

    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.

  75. So why does? says:

    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?

  76. roks says:

    Hi All,

    We have Windows 2008×64 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?


  77. Sanders says:


    after install RU2 for SP3. have problem with owa:

    Client Access server "", running Exchange version "",  is proxying Outlook Web App traffic to Client Access server "", 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.

  78. Christian Wimmer says:

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

  79. POA says:

    @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…

  80. 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) ?



  81. Exchange 2010 SP3 UR2 + Outlook 2010 SP1 or SP2 with Outlook 2010 hotfix package august 2013 (…/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.


  82. To Christian says:

    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.

  83. To To Christian says:

    … which is not documented nor has ever been necessary.

  84. 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.


  85. Peter Watson says:

    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.

  86. says:

    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

  87. reprac says:

    @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.

Comments are closed.

Skip to main content