Released: Exchange Server 2013 Service Pack 1

Exchange Server 2013 Service Pack 1 (SP1) is now available for download! Please make sure to read the release notesbefore installing SP1. The final build number for Exchange Server 2013 SP1 is 15.00.0847.032.

SP1 has already been deployed to thousands of production mailboxes in customer environments via the Exchange Server Technology Adoption Program (TAP). In addition to including fixes, SP1 provides enhancements to improve the Exchange 2013 experience. These include enhancements in security and compliance, architecture and administration, and user experiences. These key enhancements are introduced below.

Note: Some of the documentation referenced may not be fully available at the time of publishing of this post.

Security and Compliance

SP1 provides enhancements improving security and compliance capabilities in Exchange Server 2013. This includes improvements in the Data Loss Prevention (DLP) feature and the return of S/MIME encryption for Outlook Web App users.

  • DLP Policy Tips in Outlook Web App – DLP Policy Tips are now enabled for Outlook Web App (OWA) and OWA for Devices. These are the same Policy Tips available in Outlook 2013. DLP Policy Tips appear when a user attempts to send a message containing sensitive data that matches a DLP policy. Learn more about DLP Policy Tips.
  • DLP Document Fingerprinting – DLP policies already allow you to detect sensitive information such as financial or personal data. DLP Document Fingerprinting expands this capability to detect forms used in your organization. For example, you can create a document fingerprint based on your organization’s patent request form to identify when users are sending that form, and then use DLP actions to properly control dissemination of the content. Learn more about DLP Document Fingerprinting.
  • DLP sensitive information types for new regions – SP1 provides an expanded set of standard DLP sensitive information types covering an increased set of regions. SP1 adds region support for Poland, Finland and Taiwan. Learn more about the DLP sensitive information types available.
  • S/MIME support for OWA – SP1 also reintroduces the S/MIME feature in OWA, enabling OWA users to send and receive signed and encrypted email. Signed messages allow the recipient to verify that the message came from the specified sender and contains the only the content from the sender. This capability is supported when using OWA with Internet Explorer 9 or later. Learn more about S/MIME in Exchange 2013.

Architecture & Administration

These improvements help Exchange meet our customer requirements and stay in step with the latest platforms.

  • Windows Server 2012 R2 support – Exchange 2013 SP1 adds Windows Server 2012 R2 as a supported operating system and Active Directory environment for both domain and forest functional levels. For the complete configuration support information refer to the Exchange Server Supportability Matrix. This matrix includes details regarding Windows Server 2012 R2 support information about earlier versions of Exchange.
  • Exchange Admin Center Cmdlet Logging – The Exchange 2010 Management Console includes PowerShell cmdlet logging functionality. Listening to your feedback, we’re happy to announce that this functionality is now included in the Exchange Admin Center (EAC). The logging feature enables you to capture and review the recent (up to 500) commands executed in the EAC user interface while the logging window is open. Logging is invoked from the EAC help menu and continues logging while the logging window remains open.



  • ADFS for OWA – Also new for Outlook Web App in SP1 is claims-based authentication for organizations using Active Directory Federation Services. Learn more about the scenario.
  • Edge Transport server role – SP1 also reintroduces the Edge Transport server role. If you have deployed Exchange 2013 with a supported legacy Exchange Edge Transport role, you don’t need to upgrade. That configuration is still supported. But we do recommend that future deployments use the Exchange 2013 Edge Transport role. Learn more about Edge Transport in Exchange 2013.
  • New communication method for Exchange and Outlook – SP1 introduces a new communication method for Exchange Server and Microsoft Outlook called MAPI over HTTP(MAPI/HTTP). This communication method simplifies connectivity troubleshooting and improves the user connection experience with resuming from hibernate or switching networks. MAPI/HTTP is disabled by default, allowing you to decide when to enable it for your organization. MAPI/HTTP can be used in place of RPC/HTTP (Outlook Anywhere) for your Outlook 2013 SP1 clients while Outlook 2013 RTM and older clients continue to use RPC/HTTP. Learn more about deploying MAPI/HTTP.
  • DAGs without Cluster Administrative Access Points - Windows Server 2012 R2 introduces failover clusters that can operate without an administrative access point: no IP addresses or IP address resource, no network name resource, and no cluster name object. SP1 enables you to create a DAG without an administrative access point on Windows Server 2012 R2 from EAC or PowerShell. This is an optional DAG configuration for SP1 and requires Windows Server 2012 R2. DAGs with administrative access points continue to be supported. Learn more about creating a DAG without an administrative access point here and here.
  • SSL offloading – SP1 now supports SSL offloading, allowing you to terminate incoming SSL connections in front of your CAS servers and move the SSL workload (encryption & decryption tasks) to a load balancer device. Learn how to configure SSL offloading in Exchange 2013.

User Experience

We know the user experience is crucial to running a great messaging platform. SP1 provides continued enhancements to help your users work smarter.

  • Enhanced text editor for OWA - OWA now uses the same rich text editor as SharePoint, thereby improving the user experience, and enabling several new formatting and composition capabilities that you expect from modern Web application - more pasting options, rich previews to linked content, and the ability to create and modify tables.


  • Apps for Office in Compose – Mail apps are now available for use during the creation of new mail messages. This allows developers to build and users to leverage apps that can help them while they are composing mails. The compose apps leverage the Apps for Office platform and can be added via the existing Office store or corporate catalogs. Learn more about Apps for Office.


Upgrading to SP1/Deploying SP1

As with all cumulative updates (CUs), SP1 is a full build of Exchange, and the deployment of SP1 is just like the deployment of a cumulative update.

Active Directory Preparation

Prior to or concurrent with upgrading or deploying SP1 onto a server, you must update Active Directory. These are the required actions to perform prior to installing SP1 on a server.

1. Exchange 2013 SP1 includes schema changes. Therefore, you will need to execute the following command to apply the schema changes.

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

2. Exchange 2013 SP1 includes enterprise Active Directory changes (e.g., RBAC roles have been updated to support new cmdlets and/or properties). Therefore, you will need to execute the following command.

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Server Deployment

Once the above preparatory steps are completed, you can install SP1 on your servers. Of course, as always, if you don’t separately perform the above steps, they will be performed by Setup when you install your first Exchange 2013 SP1 server. If this is your first Exchange 2013 server deployment, you will need to deploy both Client Access Server and Mailbox Server roles in your organization.

If you already deployed Exchange 2013 RTM code and want to upgrade to SP1, you will run the following command from a command line.

setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms

Alternatively you can start the installation through the GUI installer.

Hybrid deployments and EOA

Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to deploy the most current (e.g., SP1) or the prior (e.g., CU3) Cumulative Update release.

Note: We have learned some customers using 3rd party or custom transport agents may experience issues after installation of SP1.  If you experience installation issues consult KB 2938053 to resolve this issue with transport agents.

Looking Ahead

Our next update for Exchange 2013 will be released as Exchange 2013 Cumulative Update 5. This CU release will continue the Exchange Server 2013 release process.

If you want to learn more about Exchange Server 2013 SP1 and have the opportunity to ask questions to the Exchange team in person, come join us at the Microsoft Exchange Conference.

Brian Shiers
Technical Product Manager, Exchange

Comments (214)
  1. @udam1 – No, you do not need to remove the security update to install SP1.

    @AndyP – yes, you can do cross-forest mailbox moves natively in the product. See for more information (note this isn’t new to SP1).


  2. Peter Karsai says:

    Any updates to the Transport Agents issue would be much appreciated, even an acknowledgement of the issue or an expected timeline for the fix. I understand that releasing any fix requires extensive testing, but that shouldn’t prevent communication about the issue.

  3. @ADBL – The article you are looking for is KB2938292. A fix for this is being included in Cumulative Update 5.

  4. KB article with the fix for Transport service issue has been published:

  5. Anonymous says:

    After installed SP1. The Microsoft Exchange Transport Service is starting . it’s hung , what can I do?

  6. raman03 says:

    We are already running Exchange 2013 CU3 on win 2012 RTM in production. I would like to upgrade to Exhange 2013 SP1 and also Windows 2012 R2.
    Since, in-place upgrade of Win 2012 to win 2012 R2 is not supported if Exchagne 2013 is already installed.
    Do you think if we keep running win 2012RTM with Exchange 2013 Sp1 and later would there be any issues in future?

  7. Anonymous says:

    Hi Team,

    I’m installing Exchange 2013 SP1 on DAG environment. Do i have to update the Cluster Aware?


  8. @Max, the Office 2010 filter pack was never a hard requirement, and setup in 2013 RTM-CU3 would warn you if it was not installed yet allow you to click-through the warning to continue installing if you chose to. Almost all of the filters the Office 2010 filter pack are included out-of-the-box with the new search infrastructure in Exchange Server 2013. The filter pack does however offer a couple additional filters, I believe OneNote and Project, that are not available out-of-the-box. If you wish to be able to index the additional file types the filter pack offers, then I would suggest installing the filter pack and its most recent service pack.

  9. @Thomas: Click the small triangle next to the question mark in the top right corner of your screen, then Show Command Logging.

  10. @Korbyn, Office 365 is already beyond the build SP1 for on-premises is (SP1 = 15.00.0847.0032) due to the way we roll changes out in the service before they make it to on-premises. Yes, our on-premises mailboxes on 2013 have been running SP1 builds or beyond. We maintain a variety of versions in our on-premises environments to ensure coverage across releases.

  11. DavidR1 says:

    Customers in hybrid deployments where Exchange is deployed on-premises and in the cloud, or who are using Exchange Online Archiving (EOA) with their on-premises Exchange deployment are required to maintain currency on Cumulative Update/Service Pack releases.

    What does that mean? Did you mean to say ‘current’ instead of ‘currency’? We are a hybrid environment. If we are required to do this, what is the time frame that we are required to deploy to on-premises from the moment that you release? How does this affect MS supporting our environment?

  12. Peter Karsai says:

    @Brent Alinger [MSFT]: That’s great news, thank you. We are deploying the FixIt solution in our test labs.

  13. Cool.. we have scheduled coming weekend for Exchange 2010 migration to Exchange 2013… now seems need to try out SP1 on lab..hope it has fixed previous bugs. ..

  14. @First Exchange 2013 server – Yes, the first server can be an SP1 server.


  15. Korbyn says:

    @Brian, awesome, much appreciated. After CU2 and not being able to backout of an update, we’re understandably a little more cautious these days. The calendar forwarding issue was a major issue for a number of clients, both on prem and in O365. Now I’m nervous about you being beyond SP1, ie what did you find already that had to be updated… ;) Thanks Exchange Team.

  16. Anonymous says:

    Glad to have Edge Role back with Exchange 2013 SP1. what about anti spam and anti virus solution like forefront for exchange, that was working perfect with exchange 2010. Do we also expect something like forefront for exchange with edge of exchange 2013 SP1 as well? or edge role by itself is enough for anti spam?.

  17. @pam walsh, there is nothing special for VL customers with regards to Service Pack 1. The bits this article links to are the same SP1 bits you’d get from any VLC portal. These bits can be used for a fresh install or an upgrade of an existing system.

  18. Nino Bilic says:

    @Regarding the anon comments – please register with the blog; we still want to hear from you in those (and other!) situations and you will still have the ability to comment and provide feedback.

  19. Currently designing Exchange 2013. Outlook client runs in Online Mode because of terminal server environment.

    Customer requires that mail from shared mailboxes goes to sent items folder of shared mailbox. However, according to this will not work with Outlook Online Mode clients.

    Alternate option is to work with multiple Exchange accounts but this has some significant limitations:

    MS provided Set-MailboxSentItemsConfiguratio with Exchange 2010 but this is not yet available with Exchange 2013.

    Customer requires that mail from shared mailboxes goes to sent items folder of shared mailbox. When can we expect Set-MailboxSentItemsConfiguration implemented in Exchange 2013?


  20. @Brian Day: You’re right, it’s not the right place here for deeper technical discussions. I found a quick solution for myself: Deactivating the “Microsoft Front End Transport” service, because I don’t need a proxy on my system. Event log doesn’t cry. If I run into trouble later on, I will open a thread in a technical forum.

  21. Eddy1968 says:


    great product, running still fine.
    BUT: Could it be, that DPM2012 R2 did not run correctly with Exchange 2013 SP1 on Windows Server 2012 R2 ? The consistency check for the Exchange 2013 mailbox database backup failed every time!

  22. @Jørn, no. :) / @Simon, you can deploy the re-welcomed Edge Transport Role if you would like to move Antispam filtering further out towards the Internet. The CAS role still performs no filtering.

  23. is the Microsoft Office 2010 Filter Pack 64 bit and Microsoft Office 2010 Filter Pack SP1 64 not required any more?

  24. @Roger.H: Thx for the reply. But 5 Restarts don’t resolve the issue. It seems that the Services “Microsoft Exchange Transport” and “Microsoft Front End Transport” are concurrent, although both are set to start automatically.

  25. @srjohny, if you have third party transport agent use script in following KB

  26. Darkfact says:

    Upgraded both Client access server and mailbox server from 2013 CU3 to SP1 on Win Server 2012 (2 servers, separate roles.) We are currently in co-existence mode with Exchange 2007. Install went fine on both servers but now the mail flow between 2007 and 2013 mailboxes doesn’t seem to work. The Queue viewer in 2007 shows the hub transport queue (SMTP Relay in Active Directory Site) just filling up with the messages. Mail delivery for 2007 users still seems to work ok (Except to 2013 users.) Servers have been restarted post install and I haven’t noticed any errors. Anything I might be missing? Thanks.

  27. Thank you Microsoft Exchange Server Team. Good news for Exchange On-Premises customers.

  28. ADBL says:

    Hi Exchange Team: Congrats on getting SP1 out! The product tests fine in our lab apart from one issue:

    OWA Apps do not work as they have previously on Windows Server 2012 (non R2).

    With Server 2012 R2, some of the App specific URLs that are present in the OWA pages are escaped, e.g. the @ symbol is replaced by ‘%40’. The referenced resources then do not load properly. This appears to be new behaviour with IIS8.5 & .NET Framework 4.5.1 vs IIS8 &.NET Framework 4.5 on 2012. has more detail about the issue.

    A possible work around may be to edit the web.config to include (aspnet:UseLegacyRequestUrlGeneration” value=”true”) but we’d rather not mess around with these things ourselves.

    We’ve disabled app functionality for our pilot users but we’d appreciate if you could comment on this ASAP.


  29. Anonymous says:

    We applied SP1 about a week ago. Exchange 2013 SP1 had probelm stopping WMI service during the setup so we had to kill WMI service manually so it can continue installation. Installation took over an hour on each server on hardware platform. SP1 is working fine, but it had cause some issue with Cisco SSLVPN and OWA is behaving a little different. In CU3, we had set LogonPagePublicPrivateSelection to true so it gave option to use as Private or Public, but it only wants to use as “Private” after SP1. I can’t uncheck “private computer” option.

  30. Anonymous says:

    Can’t find this answer. I have an exchange 2007 going to 2013. I have my 2012R2 servers ready. Do I prep the domain with the sp1 binaries or the rtm binaries? Do I install rtm exchange then update to sp1 or is there a slipstreamed exchange 2013 that includes sp1 that I should be using.

  31. @Burak, just different ways of packaging the same bits.

  32. @JB-RI, I believe the specific external meeting forwarding issue you mention was resolved in CU3.

  33. @Eddy1968, check if you have to copy newer versions of (I think) ESE.exe and ESE.dll from the 2013 SP1 server to the DPM server. DPM always needs the latest versions to be able to checksum the same version EDB.

  34. Korbyn says:

    Has SP1 been deployed internally at Microsoft and on Office 365? I believe it was mentioned after CU2, that this particular change release management process was going to be happening, and I’m curious to let our O365 customers know where they’re at, and what confidence level we have for our On Prem clients. Thanks. K.

  35. @AmbersEd, were you in a Exchange Mangement Shell session when you ran that command? I see you were in the C:WindowsSystem32> path. If you were in EMS, then it calls the default setup installed with the last update. Please try running the SP1 setup from an elevated command prompt (not an EMS session) and browse to the directory you extracted the SP1 files into before running the command.

  36. @Korbyn, you’re welcome. Our sustained engineer team is very good about making sure important items found (in this example) in post-SP1 builds we are running are what we call back-ported to SP1 builds. This is where the .32 in the version # comes from as there are a number of revisions were additional changes are made before we finally release an update.

    @Chris, yes see this article

  37. Improvement (oh no): “Test-SmtpConnectivity” showed me that my own receive connector AND the Default Frontend use the same binding “”. After deactivating my receive connector, I could start the “Microsoft Exchange Frontend Transport” service.

  38. @Qaiser.Khan, as mentioned in a previous announcement (the URL escapes me right now) Forefront Protection for Exchange 2010 was the last major version and a 2013 version is not to be released. Edge in 2013 SP1 retains the same Antispam features Edge in 2010 SP3 had, but A/V is handled by the 2013 mailbox role’s anti-malware agent, a third-party on-box solution, or perhaps Exchange Online Protection.

    @stanthewizard (do you have a cool staff and hat?), Upgrading AD would have to be answered by the directory services team, but generally they allow in-place upgrades of DCs and it should not affect Exchange. Jetze is correct that any server with Exchange installed on it cannot have an in-place OS upgrade happen and remain in a supported state. You would have to remove Exchange, upgrade, re-install Exchange.

  39. Peter Karsai says:

    GFI_Customer: They (and other vendors) are likely experiencing the same Transport Agents issue that we do. I have posted to the Exchange Server Development TechNet forum, maybe that’ll shed some light to the issue.

  40. Anonymous says:

    @ Медведовский Алексей – yes, you can publish MAPI/HTTP using TMG, just by adding the /mapi path to your publishing rule. You cannot however currently do this with UAG, there’s an update planned for UAG to add support for MAPI/HTTP.

  41. DITSupp says:

    Installing now. Will see how it goes. As an FYI… Been running CU3 on 2012R2 with Domain Functional of 2012 R2 and it runs fine to be honest.

  42. Recep YUKSEL says:

    Thank you Mr. Brian.

  43. Is connection filtering (ip block list providers like supported on single server environments with this update? Like it was in Exchange 2010?

  44. HeloCheck says:

    Thanks have been keeping back a couple of projects waiting for this, while none of my customers use it I’m glad to have back the Edge role as it is a nice options in smaller deployments.

  45. Anonymous says:

    when will I be able to download Exchange Server 2013 with SP1 from Volume Licencing Centre so I can install it on Windows Server 2012 R2?


  46. Oren Chapo says:

    We’re also having issues with custom-developed Transport Agent built with reference to Exchange 2013 RTM public DLLs, as mentioned in other comments here. Any status on this? Maybe a workaround for customers (like editing XML files for compatibility)?

  47. Hello! MAPI over HTTP will support publishing through TMG?

  48. @Ericdukece: You need prepare domain by Ex2013 SP1 distributive. You must install SP1, no need for RTM (every Exchange 2013 CU#SP# distributive is a complete version of Exchange)

  49. raman03 says:

    We are already running Exchange 2013 CU3 on win 2012 RTM in production. I would like to upgrade to Exhange 2013 SP1 and also Windows 2012 R2.
    Since, in-place upgrade of Win 2012 to win 2012 R2 is not supported if Exchagne 2013 is already installed.
    Do you think if we keep running win 2012 would there be any issues in future?

  50. AmbersEd says:

    I suppose there is no concern, but shold this say Service Pack 1 or Cumulative Update 4 for Unattended Setup?

    C:Windowssystem32>setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup

  51. Released: Exchange Server 2013 Service Pack 1
    nice work

  52. @Stanthewizzard An in-place upgrade of the operating system of a server with Exchange installed is not supported. I’d recommend to restore from backup or roll-back with setup /m:RecoverServer. See for more information:

  53. @Tony, the download page leads you here for details if you look at the details section.

  54. @Everyone bumping into some issues, please use the Exchange TechNet forums where we can interact better. Comment sections are very hard to try to help with technical issues. Love the enthusiasm, but don’t want to miss helping if it gets lost in the other comments.

    @George & Brook, do either of you have 3rd party transport agents installed?

  55. @Tony, the Edge Transport role in 2013 SP1 is managed through Exchange Management Shell until you create an Edge Subscription with the internal servers. IIS is not a requirement for ET to operate so there is no place to render EAC on the box and you end up with a system running far fewer processes.

  56. @Stig Vidar Hovland: Unfortunately not, the Connection Filtering Agent is still not supported on Exchange 2013 CAS. You could deploy an Exchange 2013 Edge Transport server with SP1 to perform this task.

  57. sime3000 says:

    When can we expect to see the Exchange 2013 SP1 help file available for download?

  58. Does it support Office 2010 on XP workstations?

  59. Anonymous says:

    @RossSmithIV – Thank you for your answer! Today we’ll start upgrading CU3 servers to SP1.

  60. @ Chris & Jordan, the modern PF access issue from Windows XP clients is fixed in SP1

    Please check KB for major issues that are fixed in SP1

  61. @AN, you may have run setup from PowerShell session which will call the existing setup file. Please run setup from a normal command line in the path you extracted the SP1 files instead and you should have better luck. :)

  62. Before going and start upgrading, it would be beneficial to stop just for a moment, and remember back to the year 2013, and all those not so successful update and rollback stories…

  63. Anonymous says:

    One concern in upgrading to SP1: Is it necessary to remove security update for CU3 (KB2880833) before upgrading to SP1? I recall that there were serious problems at CU1->CU2 upgrade with these security updates which eventually lead to failed upgrade.

  64. @Jetze Mellema: Sorry to hear that Connection filtering is still not supported. But I have already made some other agents in C# for Exchange and I think I am going to make one which check against a block list and then set the spam confidence level or a x-header if it is listed. Shouldn’t be to much work with this ……

  65. ABCFED says:

    THANK YOU!!!!

    Although, I’m still going to wait a few weeks to hear back from other people first, so please, please, please everyone post your production experiences here if you decide to deploy it.

    If no issues and everything looks like it’s clean, then I’ll start updating everyone immediately. I feel like after waiting a year, we are hopefully looking at a good, stable update that clears up the previous CU issues. The last update where the config file was modified to timeout 480 times really caused some pain. Same with all the URL directory rebuilds due to IS going bonkers. Hopefully we won’t see any more of that and we’re back on track with a fantastic Exchange experience for both the end users and admins.

    THANK YOU for releasing this update!

  66. Anonymous says:

    when will I be able to download Exchange Server 2013 with SP1 from Volume Licencing Centre so I can install it on Windows Server 2012 R2?


  67. Upgrade servers from CU3 to SP1 broke all sounds in OWA.
    Files with sound present in correct folders (owa/prem/15.0.847.32/resources/sounds/calendar_notify.mp3 for example), but IIS don’t get it to client:
    GET /owa/prem/15.0.847.32/resources/sounds/calendar_notify.mp3?UA=0 HTTP/1.1
    Response HTTP/1.1 400 Bad Request

  68. Peter Karsai says:

    @Brent Alinger [MSFT]: Thank you. If the issue gets confirmed, can you please also confirm that removing the broken XML comment line is a proper workaround? We did comprehensive testing with the policy modified this way and tests were positive — it’s just we don’t know if the comment is of any importance and removing it will break the next Exchange update or something.

  69. Oren Chapo says:

    Regarding broken Transport Agent issues, I can confirm the CFG files in the GAC are all broken. The first line in each file contains multiple hyphens (——-) which makes the entire XML invalid. Removing the first line, or fixing it by removing the multiple hyphens and making the line end with –> fixes the problem.
    Since our agent was compiled with reference to Exchange 2013 RTM public DLLs, the following files should be edited:
    Microsoft, please note: those are not the only broken files – all other files in the same hierarchy are broken as well (C:WindowsMicrosoft.NETassemblyGAC_MSILpolicy.*.Microsoft.Exchange.Data.***.cfg).
    I hope the above information will assist in releasing a quickfix ASAP.

  70. Anonymous says:

    We have been on SP1 for about a week and a half. The system seems very stable and responsive. Previously we had an issue with RPC crashing and SP1 seems to make that much better. We do have one issue with SP1 and that had to do with Caching plain text emails. We have setup the systems to pull full items now as a work around. We have a ticket open and MS was able to reproduce the issue yesterday. Hopefully they will find the issue and can resolve.

  71. Petri X says:

    Do we have any hope to get these Public Folder limitations on the level which they should be in year 2014? Or are we all forced to keep Exchange 2010 still in organization?
    10000 folders in PF store, is not an enterprise limit :-(

    Neither I have not seen fixed for cross forest migration and Public Folders. Any plans on that?

  72. Anonymous says:

    internal Managed Availability Mails are still being copied to configured Journal Mailbox – will this ever be changed ?

  73. Anonymous says:

    Plenty of my customers at have been waiting for Exchange 2013 SP1 before starting their email migration project. Good news it has arrived, and I am looking forward to testing, and then deploying it.

  74. After upgrading to SP1 does not start the transport service. The logs error
    Microsoft Exchange could not start transport agents. “C: Program Files (x86) EAExchDomainKeys EAExchDomainKeys2007.dll” because of an error “type not found.”
    After disabling the agent transport service start successfully.

  75. sime3000 says:

    Hello Exchange Team.

    When can we expect to see the Exchange 2013 SP1 help file available for download?

  76. Darkfact says:

    Nevermind, figured it out. The upgrade broke the SMTP tie-in for Symantec Mail Security. Exchange Transport would start and then stop immediately on the 2013 mailbox server. Uninstalling Symantec Mail Security fixed it, so it probably just needs to be re-installed.

  77. ADBL says:

    @Brent Alinger [MSFT]: Great, thanks for the update!

  78. ADBL says:

    @Brent Alinger [MSFT] – Please provide a link to the guidance that you mentioned in the below response. Cheers

    @ABDL – Regarding OWA Apps on 2012 R2, yes there is a change in behavior in Windows 2012 R2 which requires a Web.Config change for many OWA Apps. We are working on a KB article for this issue and will have this guidance posted within the next week. Unfortunately the article was not ready for publishing prior to the launch of SP1. It is never our preference to force customer changes to Web.Config and we are working with the Windows team to make this seamless for those who want to deploy Windows Server 2012 R2.

  79. bill says:

    YYYYYYYYYYYEEEEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSS Exchange Server 2013 SP1………………Now everyone can start the Exchange Server 2013 SP1 project moving from Exchange Server 2010 or Exchange Server 2007……………….YYYYYYYYYYYEEEEEEEEEEEEEESSSSSSSSSSSSSSSSSSSS

  80. Jørn M. Stoveland says:

    Finally! Thanks guys, good work. Now we can retire those Exchange 2007 servers! Wanted Server 2012 R2 support. Any chance of a “Forefront Protection for Exchange 2013” ? ;) Yes, I know the product is EOL, but us on-premise folk really liked it!

  81. Simon says:

    Is connection filtering (anti-spam) finally supported on CAS? Or do I have to keep the Exchg2010 server?

  82. Roger.H says:

    Finally! Built a test.lab already for this so now off to the testing! Probably do a production install later this weekend (here I thought I was gonna be able to relax this weekend :p).

  83. John says:

    GREAT news for the Exchange On-Premises customers worldwide :-)

  84. JB-RI says:

    Is there a list of everything that was fixed in the SP? There have been several outstanding issues that haven’t been fixed and I was hoping they would be in SP1. One that stands out is the inability to forward meeting invites.

    Thanks Jim

  85. Jack says:

    We are starting the Exchange Server 2013 project today……….moving from Exchange Server 2010………………2000 users……………Thanks for SP1 :-)

  86. Chris says:

    Is anyone aware if this fixes the issues with Windows XP and public folders?

  87. Patel says:

    I got 5 Enterprise clients today that want to start the Exchange Server 2013 SP1 project next week. They are moving from Exchange 2007 & Exchange 2010. Thanks for SP1 :-)

  88. Arnor says:

    Nice to see Edge Transport again. And MAPI over HTTP looks cool. But I’d kill for Forefront Endpoint Protection for Exchange 2013. The one engine filtering is terrible. And there’s no way I’m moving my SMTP traffic to the cloud.

  89. GregT says:

    Has the OWA silent redirect issue been resolved in SP1?

  90. George says:

    Time to Start the Exchange Server 2013 Project, it is the time now :-)

  91. tony says:

    Okay, now you guys can start deploying it, please comment back how it went and maybe in few weeks time I will have the guts to install it as well, if it’s not recalled.

    Still haven’t found any “issues fixed in this update” release notes. There are many bugs in CU3, especially related to Outlook 2007 so I hope this will fix at least some of them without generating new ones…

  92. Gulab Prasad says:

    This is exciting. Will start testing in LAB this weekend.

  93. Share any issues with Exchange 2013 SP1 here.... says:

    Thanks all :-)

  94. lee says:

    Phone been ringing crazy today, Clients want to start the Exchange Server 2013 SP1 Project :-) Thanks

  95. Dave says:

    I really wish they would fix the EAC being wide open to the outside world problem. Also, not everyone wants their users to have outlook access at home. A better way to block that, without breaking active sync or Lync would be awesome.

  96. Twotony says:

    What about the OWA app for IOS? Will that work for on prem deployments with sp1? Or some point in the future?

  97. ike says:

    Hello, i am currently running 028 version of SP1, may i ask how can i upgrade to this 032 version? thanks.

  98. Robert C says:

    Thanks for this. Is it possible to subscribe a 2013 Edge sever to an AD site with Ex 2013 CU1 (customer has limitations due to backup software support and cannot upgrade immediately)?

  99. @Ike – Simply run the same upgrade procedure specified above and your server will be upgraded to the final release of SP1.

    @Robert C – Edge subscription and role deployment are only supported with 2013 SP1 and later.

  100. Frank says:

    ping of mdb ‘f0583cf2-caea-4644-8c98-0a466ce1cded’ timed out after ’00:00:00′ minutes. Last successful ping was at ‘1/30/2013 11:53:27 AM’ UTC.

    Even with SP1 this warning still shows up in the eventlog. This has been there since RTM.

  101. Jordan says:

    Same as @Chris, what about Public Folder on Windows XP ? And “DefaultPublicFolderMailboxDatabase” attribute set randomley with multiple Public Folder Mailbox ?

    Thanks !

  102. ADBL says:

    Hi there,

    We’ve installed Exchange 2013 in our staging environment on a 2012 R2 Server. Based on the testing that we’ve done so far, everything appears to be working fine apart from OWA Apps.

    This thread describes the issue:

    Please see the comments near the bottom by Arjan and steviep


  103. Stanthewizzard says:

    I have upgraded from CU3 to SP1 no issue what so ever.
    Then upgraded from WS2012 to WS2012R2 … I had issue with transport service (deleted the database to fix the issue) but the databases are unmountable now :(

  104. Anthony yekula says:

    If we can get Forefront Protection(FPE) for 2013 it will be great and fun working!!!!!!!!

  105. Max says:

    is the Microsoft Office 2010 Filter Pack 64 bit and Microsoft Office 2010 Filter Pack SP1 64 not required any more?

  106. Stanthewizzard says:

    @Jetze Mellema: It’s a VM. Revert to the last snapshot was a good move.
    Now I’m making a new WS2012R2. I’m going to install EXC2013SP1 and migrate the databases to it and then I’ll decommission the WS2012 with EXC2013SP1

  107. Andy says:

    Hey Guys, I’ve installed Exchange 2013 CU3 on 4 Windows 2012 R2 servers (because I assumed it was supported when it wasn’t)

    If I update Exchange 2013 on these boxes to Exchange 2013 SP1 do we ‘assume’ all will be well or should I remove Exchange 2013 CU3 from these boxes, blow them away, rebuild new 2012 R2 ones and then put a fresh Ex2013 SP1 on?

    Just gauging thoughts



  108. thomas says:

    How can i turn on the command log Viewer in ECP?

  109. Vanzetti44 says:

    Same as @Chris and @Jordan, what about the issue with Public Folder on Windows XP ?

  110. I upgraded from CU3 to SP1. Now the Microsoft Exchange Transport Service does not start anymore: ” M.E.ProcessManager.WorkerProcessRequestedAbnormalTerminationException, 5e2b, 15.00.0847.030″ Any ideas?

  111. blue says:

    Thank God! Our Exchange 2013 project can finally get started.

  112. Jeff25 says:

    So, what’s the big feature of SP1 everyone needed, or is this just people don’t do anything prior to SP1? I guess I’m just curious, because all the previous issues with 2013 were ‘unexpected’, and thus rollbacks ensued. What makes this any different? I remember when we did 2007, we were waiting for SP1 to have the import-mailbox cmdlet available, but I don’t see anything that grand missing from 2013 CU3, I guess.

  113. Jeff25 says:

    Ok, except for 2012R2 officially being supported. I guess that’s a biggie.

  114. Mindaugas Laucius says:

    Congratulations to anyone.

    I see many of you got some additional work new projects.. I’ve been working with Exchange 2013 for more than a year.. Did small migrations and large (9000 users), struggled with Public Folders and Reverse-Proxy (TMG). In short, I have lots of experience. If anyone needs any type of freelance help, please do not hesitate to contact me. Hit me on LinkedIn.

  115. Stefan says:

    fine, this seems to fix the rtf convert problem when using the exchange archive
    the problem:

    hopefully without any new bugs (reported a lot last year to the support) :)

  116. Stefan says:

    fine, this seems to fix the rtf convert problem when using the exchange archive
    the problem:

    hopefully without any new bugs (reported a lot last year to the support) :)

  117. stanthewizard says:

    @Jetze Mellema : is this the same mess with upgrading AD to R2 ?

  118. SteveT says:

    Downloaded the UMLanguagePack (its now a MSI) and it won’t install:
    setup /AddUmLanguagePack:en-GB /s:D:Language /IAcceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup UM Language Pack for en-GB
    The UM language pack file ‘D:LanguageUMLanguagePack.en-GB.exe’ doesn’t exist.

    The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the :ExchangeSetupLogs folder.

    Anyone know the cure???

  119. Gordon Barr says:

    Very happy to hear that the code fix to address control/visibility into CAS-to-CAS proxy for down-level mailboxes made it into SP1. Big win!
    Thanks to everyone on the Exchange Team and TAPs for all the great work.

  120. Brook says:

    +1 on GeorgeFromGermany issue, I have also (in a test environment) upgraded from CU3 to SP1, and the Microsoft Exchange Transport Service will not start ?!

  121. Roger.H says:

    @Brooks & @GeorgefromGermany

    If people actually read the Release Notes:

    Mail flow stops after Exchange 2013 SP1 is installed After you upgrade to Exchange 2013 SP1 from a previous version of Exchange 2013, mail flow might stop working on servers that have the Client Access server role installed. This happens because, even though the Microsoft Exchange Frontend Transport service starts after Setup completes, it doesn’t correctly detect that it can start sending mail again. This issue doesn’t occur on new installations of Exchange 2013 SP1.

    To work around the issue, restart the server after Setup completes.

  122. @SteveT – Thank you for reporting this. The .EXE UM Language Pack package will be on the download center shortly.

  123. Brook says:

    @Roger.H…+1 (again) on what GeorgeFromGermany said…since I (fortunately) did this in a test environment, I have restarted the server several times, so even though your somewhat “RT(F)M”-suggestion were appreciated, it’s not the solution for us…

  124. Brook says:

    @Brian Day: nope, nothing third party at all, a single non-dag multirole CAS+MBX server, installed first with CU3 media (working fine), upgraded to SP1 –> Transport Service refuses to start (after several restarts).

  125. Jeremy Redmond says:

    Does SP1 add Public Folders support to Outlook 2011? Thanks.

  126. @jack b1 – We are targeting to have SP1 on Volume Licensing Center in April. You don’t need to wait until then to download this however. The same package is available today on the Microsoft Download Center at the download link above.

  127. Cell says:

    Will be released UM language pack for Turkish ? if so when ? thanks ,

  128. SteveT says:

    @Brent Alinger [MSFT]

    Thanks for the reply, just downloaded and successfully installed the .EXE UM LanguagePacks. All good from my side now. Love the ‘Show Command Logging’ window


  129. Peter says:

    We’re experiencing issues with Transport Agents, they fail to install with "type not found" errors. Our TAs are linked against the 8.0 public Exchange assemblies. In pre-SP1 builds, the Exchange Team used an assembly redirection policy to enable this and
    thus building Exchange version-neutral agents. In SP1, the range of version redirections have been extended (which is good), but the policies are no longer well-formatted XML files (which I guess is bad). According to Fusion (Assembly Binder) logs, this causes
    the .NET framework to ignore the policy. Specifically, each redirection policy XML content is prefixed with "". It looks like a valid XML comment, but it isn’t — in fact, it breaks the XML. Once we remove the offending comment line from the policy in the
    GAC, Transport Agents install and run fine.

    Are we missing something or the redirection policies really are broken?

  130. Brook says:

    @George & Brian: problem solved (hopefully), recreating custom receive connector to use frontend instead of hub solved non starting transport service…

  131. Stanthewizzard says:

    @Brian Day and @Jetze Mellema : cool staff and hat ? no :) small enterprise with very patient staff.

    FYI … I revert to the snapshot. Worked like a charm. Then I deployed a WS2012R2 VM, installed EXC2013 SP1 on it. I migrated ALL the mailboxes (including the system one). Desinstalled the EXC2013SP1 on the the WS2012… tada I’m now unable to send and receive mail and only on my mailboxe I’m stuck with a white screen.

    Guess wat I’m reverting (thanks to veeam) the AD to monday and the WS2012 with EXC2013CU3.
    I’m so happy :(

    But I’m not giving up

  132. Burak says:

    Thanks guys! Great job!

    Will be there a image with SP1 included? I guess I have to install Exchange 2013 and after that I have to install Sp1 manually?

  133. Jeremy Redmond says:

    Every update includes the full install of Exchange 2013. You simply run the SP1 installer and install Exchange 2013 and you’re good to go.

  134. Jonas Calén says:

    Running SP1 and it seems to work just fine – 500 users.

  135. Steven BerkHolz says:

    Was hoping they would come back out with OWA Calendar viewing. ;-(

  136. Burak says:

    @Jeremy Okay, but why is the Exchange Image size from VLSC ~3,5GB and the Exchange 2013 SP1 from the link above only 1,5GB if it contains the complete Exchange installation?

  137. GFI_Customer says:

    Be aware that this update will break GFI MailEssentials. After speaking with GFI they said they are not the only 3rd party filters having issues with this update.

  138. Regarding the anon comments says:

    As much as you guys don't want anon comments… it's the bubbling up of the post release issues that are tied to a specfic release that I cannot find in the same way digging through in the forums.

    Just sayin….

  139. Patel says:

    Installed Exchange Server 2013 SP1 in the lab now, Works Great :-) Thanks, Production next.

  140. Jack says:

    Exchange Server 2013 SP1 in the lab now, No issues, Thanks….

  141. Sean says:

    Is there support for Gen 2 VMs on 2012r2?

  142. @Peter – Thanks for your detailed post on Transport Agent redirection. We are actively investigating the XML formatting error that is blocking Transport Agents from working correctly and will provide further information as it becomes available.

  143. pesospesos says:

    Sean, our 2013cu3 servers are gen2 vms running 2012. Works great.

  144. Luca says:

    Iera ora.

  145. berndk says:

    Sorry Guys, I am not convinced about that so called SP1 This is more a mix of the never released CU4 / Q4 2013 and CU1 / Q1 2014. A lot of “nice to have features”, but no “must have features”, except support of Windows Server 2012 R2. For example, ExBPA for Exchange 2013 on premises installation is still missing!

  146. Leo Jacob says:

    Yes excellent love the service pack

  147. BuenoFlex says:

    if you need step by step instruction to migrate to this new version you can get info here :

  148. Avin says:

    Great job Microsoft..!!! :) It was very much awaited.
    Finally upgraded to Windows 2012 R2 + Exchange 2013 SP1.
    Requesting more elaborated documentation on Edge Transport 2013.
    What about the Edge transport 2013 Licensing model ?

  149. Question: I have Exchange 2013 RTM running on Windows Server 2012. Is it supported/recommended to first upgrade Exchange 2013 to Exchange 2013 SP1 and then do an inplace update of Windows Server 2012 to Windows Server 2012 R2?

  150. AN says:

    setup /prparead output shows
    Welcome to MS Exchange 2013 CU3 Unattended Setup

    I got to run setup to check if it is what it is, MS as MS.

  151. Dan_IT says:

    Does your OWA play the new email sound with SP1?
    The email_notify.mp3 call seems to throw HTTP 400.

  152. JJ says:

    I have Exchange Server 2013 SP 1 in lab now, Working great :-) Thanks, Production is next.

  153. @ABDL – Regarding OWA Apps on 2012 R2, yes there is a change in behavior in Windows 2012 R2 which requires a Web.Config change for many OWA Apps. We are working on a KB article for this issue and will have this guidance posted within the next week. Unfortunately the article was not ready for publishing prior to the launch of SP1. It is never our preference to force customer changes to Web.Config and we are working with the Windows team to make this seamless for those who want to deploy Windows Server 2012 R2.

  154. John B says:

    I just updated 5 of my 6 servers to SP1. We also had the issue with the transport service not starting. It was due to us having Recieve connectors with the hub transport role as noted in an above post. Once I removed these and added them as frontend transport role then everything works as normal. Just wanted to share.

  155. Diego says:

    Where is the user experience? I’m still unable to paste images in message body and the format preview doesn’t work. It’s still a pain to add an hyperlink to an network share, an ftp and so on.

  156. Max says:

    In fact it’s an advanced e-mail application and no more. I don’t see distinct features of Exchange Server. Perhaps it’s convenient for business, but sharing instant messaging isn’t very necessary if alternative applications for mobile phones and computers too…

  157. lee says:

    Just installed Exchange Server 2013 SP 1 in our lab and it is Coexisting with Exchange Server 2013 SP3, No issues & working great :-) Thanks, next we going Production :-)

  158. lee says:

    I meant coexist with Exchange Server 2010 SP3.

  159. Jose says:

    We have Exchange Server 2013 SP1 in the lab now, No issues, Thanks

  160. grant says:

    Sp1 of exchange 2013 breaks substandard ports

    If I goto https://fqdn:9443/owa
    It redirects me to https://fqdn/owa/auth/login.aspx

    Once I login successfully it returns me to my mailbox on port 9443

    The issue is the login page is on 443 and my isp blocks it, pre-sp1 worked fine.

  161. pam walsh says:

    When will Exchange 2013 SP1 be available to volume license holders?
    I just telephoned MS volume licensing and they know nothing about the release.

  162. John B says:

    We are seeing a weird issue where emails are being trunkated within Outlook once we update to SP1. Just a heads up. We will post any update once we know more.

  163. dani says:

    Production Servers (2), works great generally.
    1. i had some issues with the new frontend transport, fixed by configuring a new connector, nothing to fancy
    2. OpenText RightFax Connector not working as it should, i made a workaround for the meanwhile untill OpenText will address that issue.

  164. tony says:

    Have installed exchange 2013 sp1 edge .. The big question is how do you get into ecp as it dosnt appear to have installed it .

  165. ExchangingTech says:

    Nice to see SP1 has arrived…now we can avidly market this new stable platform to our customers!

  166. Antonio Saraca says:

    Me too after installing SP1 on my 3 servers in DAG configuration, the Microsoft Exchange Transport would not start. I had to delete some custom Receive connectors I had created. After that the Microsoft Exchange Transport was able to start, but now my Event Log is flooded by events “A forced configuration update for … has successfully completed. Object details from last notification …” from 4 sources: MsExchangeTransport, MsExchangeTransportSubmission, MsExchangeFrontEndTransport and MsExchangeTransportDelivery. Is that normal ?

  167. JamieAkers says:

    Raised a support incident with Microsoft to find out when a fix will be available for the Transport Agent problems. Hopefully will get an update soon, plenty of customers have been calling us having this problem – both with our software and numerous other anti-virus/anti-spam solutions out there.

  168. @Peter – We have been working behind the scenes to investigate and publish a proper response on the transport agents issue. I am pleased to report that just a couple of hours ago we published a KB and a FixIt solution that customers who are having problems with transport extensibility via agents can use to correct this condition on their servers. The FixIt provides a script that customers can run directly or add to their deployment steps to resolve this issue. Details can be found in

    To address your question on what impact modifications by customers who may have removed or modified the comment already on their server will encounter, the answer is there is no ill effect from doing this. These customers will have no problems using SP1 or moving to other later versions. The comment is there simply to identify the version of the file, typical action in software, and its absence will have no detrimental effect.

  169. Bas says:

    Is Windows 2012 R2 is now officially supported by Exchange 2013 sp1?

  170. @DavidR1 – The intent of the statement is to remind Admins that if they are utilizing Exchange services which span the service and their in-house deployment that the servers they maintain need to be updated regularly to our latest releases. This is necessary to avoid unintended inter-op issues between the servers they maintain and the ones deployed in O365. We don't expect this to occur on day one of our release, obviously. We do however expect that the customer will validate and proceed with deployment such that they are never more than 2 CU's behind the most recent release. That means today customers should be running CU2 or later and testing or deploying CU3 or later.

  171. Thomas P says:

    the transport agent fix doesn't work for me (McAfee Security for Exchange 8.0 with Patch 1 and Roll-up 1 for Patch 1 :-(

  172. gerard says:

    My upgrade experienced wasn’t particularly smooth.

    Preparing Files FAILED with “A reboot is required to complete file operations on ‘{4934D1EA-BE46-48B1-8847-F1AF20E892C1}’. Reboot the machine, and then run setup again.”. Fortunately it did continue when I ran setup again.

    Then I had the “Cannot determine the product name registry subkey, neither the ‘RegistryProductName’ application setting nor the ‘CERES_REGISTRY_PRODUCT_NAME’ environment variable was set
    I had to set the CERES_REGISTRY_PRODUCT_NAME environment variable to “Search Foundation for Exchange” to fix this.

    Finally setup waited a very long time for the service ‘MSExchangeFrontEndTransport’ to reach status ‘Running’. This never happened, so I restarted the server, then the FrontEnd Transport started, but then the Transport service would stop shortly after starting. It turned out that the default receive connectors had been modified in such a way that these two services tried to listen on the same IP-address on port 25. I modified the default rule to listen only on a particular IP-address and then both services would start correctly.

  173. John B says:

    @Thomas P we removed MSME but there are two HF after patch 1 for sp1. hf926534 & hf939908 don’t know if those would help.

  174. azylis says:


    I have only one issue after SP1 in my French exchange infrastructure.

    Now, Mailbox Warning Quota messages are in english ?

    How to put warning messages in french ?


  175. Anthony says:

    We have now Exchange Server 2013 SP1 in the lab coexist with Exchange Server 2007 SP 3, everything working Great, Thanks

  176. Matt says:

    Any support for removing single roles from a server like removing CAS role from a combined CAS/MBX server?

  177. jim says:

    YYYYYYEEEEEEEE we have now Exchange Server 2013 SP1 in the lab. In our producation we have Exchange Server 2010 SP3, we are looking to start the Exchange Server 2013 SP1 project very soon.

  178. moe says:

    Ok Guys we got Exchange Server 2013 SP1 now in the lab, Thanks, everything ok so far.

  179. Husk says:

    I'm looking at a cross-forest migration from Exchange 2003 preferably without 3rd party toolsets and heard that there was some functionality in 2013 SP1 that could facilitate this – is that the case?

  180. sam says:

    When can we expect to see the Exchange 2013 SP1 help file available for download? i.e. "Exch2013OnPremHelp.exe"

  181. Frank says:

    Congratulations for SP1, it seems quite stable, scalable and ready for production.

    But the whole thing looks a litte bit "loveless" with the new CU model. Many little and bigger things are not well tested:

    RTM – Windows backup didn't work
    CU1 – Problem with delegation sending
    CU2 – Mailbox permission problem on move
    CU3 – Outlook on XP didn't work properly
    SP1 – OWA notification sounds broken

    A lot of event log "spamming" entries (DatabaseDriveSpaceTrigger, MDP Ping timeouts) since early CUs, we can still send read-receipts in OWA only out of the preview window, no interim updates for bigger issues like the broken XP…

    But using it for a year in production I must admit that the core system seems running well und stable, so I think the most new installations can start with 2013.

  182. Bill2 says:

    Has it been reported that the spacing is broken in Firefox? You cannot start a new line with a space or double space. Also there needs to be instructions posted on the new customization procedure for OWA. Also there is issue with Outlook on Windows XP were it will not connect and create a new Exchange profile unless you manually trust the cert at least in our case of using komodo certs. I know XP will soon not be supported but we were hoping this would end up the version that works the best with Windows XP.

  183. First Exchange 2013 server says:

    If I'm doing an exchange 2010 to 2013 migration can I just use this SP1 download to install my first exchange 2013 sever?

  184. Bill2 says:

    I posted a comment yesterday about some true facts like the incompatibilities with Firefox and line spacing and issues with XP. I find it funny you did not approve them,

  185. ADBL says:

    @Brent Alinger [MSFT]: Hi, has the KB article regarding OWA apps on Server 2012 R2 been released?

  186. David says:

    That’s much appreciate for release of Exchange 2013 SP1!! Now it’s time to testing in lab, before will doing upgrade or deploy in production environment.

    As you known modern PF in Exchange 2013 CU3 didn’t appear in OWA, although new release supports PF in Windows XP. What’s happens with modern PF in OWA with this new version? In the release notes didn’t mention about it, so this feature was requested for more customers.

    Thanks for your help!

  187. Sheri says:

    Hi, I have 2 exchange 2013 mailbox servers in DAG and 2 exchange 2013 CAS servers in windows NLB, all exchange servers are running CU2. I want to ask about SP1 installation sequence, on which node (Mailbox or CAS) should I start to install SP1 first. From which server of exchange should I install SP1 first.
    Any useful comments on this.

  188. Rubarb says:

    Broke my transport service, had to install the fixit and then was able to start the transport service. Was running Kaspersky security in transport agents. Also, SP1 breaks the HTTPS redirect in IIS. I had good luck with the 403.4 error redirect fix out lined here: Anyone else have issues with the https redirect breaking?

  189. Sheri says:

    As per above article, where is the Edge transport role in exchange 2013, how we can use it after installing SP1 of exchange 2013

  190. Craig says:

    After applying Service pack 1 we have users on Outlook 2013 getting the message “The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”. Happens every 15-60 minutes.

    Is anyone else seeing this issue?

  191. hany says:

    We have Exchange 2013 CU2 on Windows Server 2012 in place.
    If we perform in place upgrade to Exchange 2013 SP1, will we get use of Dynamic Quorum feature?

  192. Dan_IT says:

    @Ericdukece, use the SP1 package and you’re fine! Every CU / SP is a slipstreamed installation source.

  193. sam says:

    When can we expect to see the Exchange 2013 SP1 help file available for download?

  194. angryman says:

    Install the sp1 then all outlook 2011 14.x clients sending email problem and no answer in this case.
    “The user account which was used to submit this request does not have the right to send on behalf of the specified sending account”

  195. Joe says:

    Did the new update change the way email groups are created? I used to be able to enter an email address to a group without creating a contact for it. Now I have to go through the tedious process of creating a contact, and then assigning it to a group. Is there a way around this?

  196. Todd says:

    running setup /prepareAD for Exchange 2013 sp1 gives me “object not set to an instance of an object” once the organization checks hit 30 pct. I am not able to find any more information on this error anywhere.

  197. Matthew S says:

    I had an issue with transport service not starting after applying SP1. What John B suggested fixed my issue. Before SP1 I had to have a hub transport receive connector in place, so that mail would flow between our exchange 2007 server and exchange 2013 server. Now that SP1 has been installed it actually works like it is suppose to and I do not need the receive connector for the exchange servers.

  198. jlowery says:

    Two notes from our initial testing of SP1:

    1. NET 4.5.1 System.Web.HttpModule based extensions do not work in the /mapi/emsmdb page, either failing or causing the MapiHttpHandler to fail, depending on the extension implementation. It appears to be the same bug that was corrected in the WCF server framework described in Would definitely like to see this one fixed.

    2. IIS Advanced Logging does not work on the Exchange Backend/mapi/emsmdb page. It does work properly on the ews, owa and rpcProxy.


  199. Ash747 says:

    We just upgraded to Exchange Server SP1, but now we are having mailbox connectivity issue with Outlook 2010 and Outlook 2013. OWA is working fine though. Are we missing out something?

  200. jeremy says:

    We deployed Exchange Server 2013 SP1 and we have one user that keeps getting error message that says “The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook”. The user has quit Outlook and reboot her machine and the message still pops up. Can’t figure out why. Any ideas????

  201. you jizz says:

    Lastly! Thanks guys, useful operate. Now we can“>youjizz withdraw from circulation those Trade 2007 servers! Wanted Server 2012 R2 prop. Any accident of a “Forefront Preservation for Trade 2013” ? ;) Yes, I know the production is EOL, but us on-lay down beforehand folk really liked it!

  202. Stephen Lembert says:

    Finally a better and more advanced Exchange is here.

  203. Leon says:

    small update:
    this weekend updated a exchange 2013 update 3 to sp1. (dag configuration with two nodes).

    first one went flawless, no errors, no problems.
    second node during the setup crashed 5 times with all kind of “sir” watson errors. reboot, started the update again,….and after 5 times it was succesfull. rebooted it. and works.

    i can confirm that the sound notification is not playing in webmail (appointments).

    if i can notice i think this is a stable update with a lot of fixes and the small issues i had in update 3 are now gone. thnx guys.:)

  204. James Barbone says:


    Can MS Exchange or Outlook API open 500 or more simultanious
    connections per second and can be installed & configured on a
    Google App Engine server or a MS Azure server to send several
    million newsletters daily ? We do not know how to use JavaMail.
    Google has gave us permission to send 5 million messages daily.
    Sincerely, +

    Quota Increase Request + Approved + Billing Enabled

    App Engine’s quota system allows for efficient applications with billing enabled to scale to around 500 queries per second (qps) or more than 40 million queries per day. This is a substantial amount of traffic and should easily suffice for even the heaviest
    of Slashdottings. But if you expect your application will need to handle even higher qps, please complete this form so we can assist you.

    First name * James

    Last name * Barbone

    Admin Email: *

    Your application ID ( *

    Application description * Newsletter

    Traffic estimate (qps) * 5 Million Daily

    Cause of traffic spike (e.g. new launch, Dugg, etc.) * New Launch

  205. Hasan Rahman says:

    Nice, now if you could just add sent items configuration that would make my day… It was there in 2010 and in 2013 it is gone…

  206. Chris says:


    Big mistake by not including a note about KB2874216 being installed. Apparently this update breaks other CUs and SP1. Now I’m having a problem uninstalling it. The installer should check for this update and fail gracefully rather than making it part of the way through then refusing to go further. Sheesh.

  207. Clemens says:

    I have seen issues with GAL segmentation after applying SP1. Users in GAL A are not able to respond on meeting invitations from users in GAL B only from their mobile devices (I’ve tested it with iOS). Mailaddresses are not resolved correctly. Does anyone else has this issue?

  208. Luis Afonso says:

    Still not compatible with Microsoft Software Key Storage Provider … Windows 20082012 CA…. Unable to understand this issue…

Comments are closed.

Skip to main content