Exchange Server 2010 SP1 Beta Now Available for Download

We are pleased to announce the availability of Exchange Server 2010 SP1 Beta.

As we shared in Yes Virginia, there is an Exchange Server 2010 SP1 in April, Exchange Server 2010 SP1 Beta incorporates a number of feature updates including: archiving and discovery enhancements, a faster Outlook Web App (OWA), upgraded mobility features, and several improvements in the management UI. The SP1 beta is available to the public and can be downloaded here.

We also wanted to let you know that Exchange Server 2007 SP3 is still on track and will be available soon, so stay tuned to the Exchange Team Blog.

The Exchange team wants to thank each one of you who has taken the time to provide us with your thoughts on the products: what works great, what doesn't, and everything in between. Neither of these important service packs would have been possible without your rich and direct feedback. The Exchange Server 2010 SP1 Beta includes features that you wanted us to prioritize. And your feedback on the need for Exchange 2007 support on Windows Server 2008 R2 is helping us develop Exchange Server 2007 SP3.

We leverage multiple channels to gather your feedback, from the customer deployments in the Technology Adoption Program (TAP) and on-site visits to social media channels such as this blog and our technical forums. Please continue to share your feedback and follow us on Twitter, @msftexchange. We promise we'll continue to listen.

The Microsoft Communications Server "14" team also has feature announcements today. Check out their new blog post.

Kevin Allison
GM - Exchange Customer Experience

Comments (46)
  1. Salim says:

    Great news, can’t wait the RTM.

  2. Mike Crowley says:

    Are the release notes within the download?  Can I see an itemized list of changes and enhancements?

  3. Frank T says:

    Good to see that feedback is leading to new features.

    "My name is Frank.  I’m an Exchange server… and SP1 was *my* idea"

    (sorry) :)

  4. GoodThings2Life says:

    If I can add/remove users from distribution groups without having to go into groups separately, I’ll be a happy camper…

  5. Tim says:

    Full OWA for all browsers would be a great update for 2007 SP3.

  6. Mike Crowley says:!C23CB95E1200929!454.entry

    -Installation Tips


    -New Features (that I noticed)

  7. Jason HT says:

    I don’t have the luxury of a lab environment these days, but if anyone else is using OCS 2007 R2 and has it integrated into the OWA page, does it continue to function after the SP1 install?  With the changes to OWA, I’d like to know if it does or doesn’t OOTB (so to speak) or if there’s going to be some sort of document for those of us that will need to make some changes.

  8. bday says:

    Jason, it’ll keep functioning but you will have to make a couple slight modification. The web.config file is no longer used and the IM settings for the OWA virtual directory are now stored in Active Directory (yay!) through some new Set-OwaVirtualDirectory options. :)

  9. Mahmoud Magdy says:

    Guys did anyone managed to download the SP1, I downloaded it twice and when installing it says the file is corrupted, is it only me that having this issue

  10. Sundis says:

    I have tested Service Pack 1 for a couple of days and I have some questions. First, does this build include features that enables you to Provision and configure the Personal Archive in ECP? I have looked for it but can’t find it…

    Second, I have tried running the installation using the /hosting switch but receive an error stating that the parameter is incorrect. Is that supposed to work or am I doing it wrong? :)

    And finally, thanks for the update and all the great new features!

  11. Bharat Suneja [MSFT] says:

    @Sundis: 1. Personal Archive can’t be provisioned using ECP. You can use EMC or the Shell.

  12. Sundis says:

    Mike, thanks for the link even though that didn’t really answer my question. I have got those features covered on my blog as well:

    Bharat, Thanks for clearing this up, I guess the initial statement in the post, Yes Virginia, there is an Exchange Server 2010 SP1,  was not entirely correct then?

    Any thoughts on my second question?

  13. Irrwitz says:

    Great! After the installation my OWA did not work anymore! ISAPI runtime error!?

  14. Scott says:

    Perhaps I’m mistaken, but I thought perhaps the export/import-mailbox commands would be fixed ( Or maybe will it just be fixed in rollup 5 (another internet rumour perhaps).

    Other than that.. I enjoy the new archive features. Although I wouldn’t mind a "move archive back to online mailbox and disable archive" command for a person.

  15. Korbyn says:

    Seems good enough to put into production, very impressed so far in the lab, question remains, when it releases, do we need to remove the Beta and install the releases SP1, or will we be able to go from Beta to released-SP1?

  16. Scott –

    Import-Mailbox and Export-Mailbox have been replaced in SP1 with New-MailboxImportRequest and New-MailboxExportRequest. Outlook is no longer required on the server to run these cmdlets, either.  These cmdlets work asynchronously utilizing the same infrastructure as New-MoveRequest.


  17. SvenC says:

    Great stuff coming with SP1. Thanks!

    Where can I submit bug reports?

    1) german translation for "To" should be "An" but is "Bis"

    2) When I register an ascx file in my registry.xml for a custom message class then this ascx file is searched in formspremium and not in my formsmyapp directory. I am not sure if this counts as bug or by design as ascx files are loaded by SubpageContainer.aspx which lives in formspremium.

  18. Bastiano says:

    Wonderful features!

    But I cannot install it with UM Role:

    Error in checking Microsoft UC Managed

    API 64bit also they’re installed.

    Had someone took same error?



  19. Stuart Cowen says:

    I am also having the same trouble getting past the Unified Messaging Role Prerequisite checks due to the Microsoft UC Managed API 2.0 64-bit. I have installed it multiple times and rebooted, but the SP1 Beta installer fails to see that it’s installed.

    Any solutions or workarounds? Thank you.

  20. Dianne G. says:

    I ran into the same issue with the UC Managed API 2.0 64-bit installer. Turns out, after you run the MSI, you have to go to the directory where it was "installed," for me it was C:Microsoft UCMA 2.0 Runtime Installer Packageamd64, and run the setup. It should go through another install, and you should be good to go. It looks like the downloaded MSI is more of an extractor than an installer.

  21. A Lewis says:

    I appriciate if this Sp3 would include some brick level recovery tools, As using RSG is less painful than rebuilding and recovering, which i used to do in 2003 exchange, As there is a SLA for recovery of mailbox. Comments from other Exchange admins appriciated.

    Thanks in advance


  22. CR says:


    I have same problems try install a UM Languague Pack:

    Any one give same help?

  23. Doug says:

    Does SP1 enable Outlook 2007 support for the online archive?

  24. Sundis says:

    As I understand it, Outlook 2007 will need and update to be able to support online archives. I might be wrong though…

  25. A. Gotink says:

    Has anyone tested the Move-TransportDatabase.ps1 script?

    I does not work when not all arguments are given. The RTM script worked OK with 1 or 2 parameters.

    I think the "param" section in the script should not containt "[String]"

    Can anyone confirm this?

  26. Jamie Schwinn says:

    I installed SP1 in my lab environment and it broke UM. Service will not start with Event ID 1057, MSExchange Unified Messaging. Anyone else seeing this?

    An unhandled exception occurred in a UM worker process: "System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.TypeInitializationException: The type initializer for ‘Microsoft.Exchange.UM.UcmaPlatform.UcmaPlatform’ threw an exception. —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.Speech, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.

    File name: ‘Microsoft.Speech, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35’

      at Microsoft.Exchange.UM.UcmaPlatform.UcmaPlatform..cctor()

  27. Jamie Schwinn says:

    Fixed UM!

    Needed to install Microsoft Server Speech Platform Runtime (x64).

    The installer did not warn me about this prereq…

  28. Robert says:

    I find the Public Folder Management Console a little odd in regards to permissions – you can ADD or REMOVE from the permissions but you can’t merely VIEW what is currently the settings for a given Public Folder.  So are you supposed to be flipping between Outlook and the tool to see what is going on?  

  29. Nuno Luz1 says:

    Hi, I am getting an error when running the installation when it reaches the mailbox role:

    I dont have AV nor Forefront, and before I started the update I stopped all Exchange services.

  30. Steve Carnes says:

    While I have been very impressed with the enhancements in managing ActiveSync devices in SP1, one thing I was particularly disappointed in is that it appears you only have the ability to create device access rules based on only the ‘Device family’ and the ‘Model.’ It would be extremely valuable to Exchange Admins in a corporate environment to be able to use other ActiveSync data that is collected to more granularly control device access such as ‘DeviceUserAgent’ and ‘DeviceOS.’ This would allow for the ability to allow/disallow not only particular devices and models but devices with OS versions that you may not have yet tested or don’t support features required in your environment.

  31. Steve Carnes says:

    The most recent post ‘iOS 4 and Exchange ActiveSync’ is exactly the type of scenario that makes the functionality I describe in my previous post critical in ensuring you can granularly control ActiveSync device by OS version – new or old!

  32. A. Gotink says:

    The lack of UDP notifications is a real pain-in-the-as for Outlook 2003 users. I tried this SP1 beta. It seems to me that the Outlook 2003 problem is solved!! Great !!

    I tried it whith 1 CAS server with and 1 CAS server without sp1.

    Is UDP back?

    Can someone confirm this?

  33. usftork says:

    How does one submit a bug report?  I believe the ExchangeAB SPN gets registered everytime at reboot and am unable to unregister it using setspn -D.

  34. pascal.horner says:

    Can anyone tell me where I can found the release date of the SP1 and where I can found the complete release notes.

  35. andreas says:

    Hi! Are the schema changes of SP1 RTM or beta-state? I didn’t want to update my productive AD-schema bevor being sure there are no further changes with RTM (replication-traffic, risk because of attributes which couldn’t be removed, …)

  36. Bharat Suneja [MSFT] says:

    @Andreas: We recommend not using beta products (including using them for schema extensions) in a production environment unless you’re a participant in our TAP/RDP programs.

  37. Bharat Suneja [MSFT] says:

    @pascal.horner: Exchange 2010 SP1 has not been released yet. You can download the public beta from

    Microsoft Exchange Server 2010 SP1 Beta

  38. LilWashu says:

    I’ll repeat a question from above – have UDP notifications been reinstated in Exchange 2010 SP1 beta, and if so, will they remain in RTM?

  39. jam365 says:

    I am currently in the process in getting everything ready to migrate to EX2010 SP1 (from EX2003) and trying to figure out an "easier" way to import circa 11,000 PST files other than the complicated cmdlet/shell processes that I keep finding on various blogs. Anyone know?

  40. Rob says:

    I have install Exchange 2010 Beta sp1 over my existing exchange2010 and it totally messed up my EMC, it will not connect to any servers anymore? The Powershell does not have and commands available now to work in the Exchange it looks for a FQDN but when giving one, nothing. When EMC was loaded on a different server without Exchange its EMC and Powershell ran the same asking for FQDN. I need to remove of this and start over, how is this done? Please shed some light on this. When uninstalling from the Applet ADDRemove it stops because there are mailboxes still on the server they have to be removed first? I am very disappointed with this Beta SP1 product.

  41. Jon Stanton says:

    Is there any indication when Exchange 2010 SP1 will go on public release?

    The Beta has now been out over two months but we don’t want to put this onto our live system!

  42. Chips O'Toole says:

    @Albert Gotink, @LilWashu

    I’ve done some testing, and I can say definitively that, no, UDP push notifications for Outlook 2003 have *not* been reimplemented in Exchange 2010 SP1 Beta, and I’m sorely disappointed by it.  In my lab at this very moment, I have Outlook 2003 SP3 accessing a mailbox on an Exchange 2010 SP1 Beta CAS/Mailbox server in Online mode and folder updates are as sluggish as ever.  A packet sniff with RPC encryption turned off confirms that Outlook 2003 makes a MAPI request to receive UDP push notifications from the SP1 Beta CAS when Outlook starts up (EcRegisterPushNotification), and the CAS rejects the request with a "MAPI_E_NO_SUPPORT" response, and, indeed, I don’t see any UDP push notification packets in the sniff after this.  As an experimental control, when I point the same Outlook client at an Exchange 2003 mailbox, it works as expected (push notifications in the packet trace, instant display updates on the screen).

    I’m very, very cranky about this. It’d be one thing if I could back off to Exchange 2007, but of course, I can’t, because Microsoft has inexplicably cut off that escape route for greenfield Exchange 2010 installs.

  43. Albert Gotink says:

    I am very sad about the lack of UDP notifications for Outlook 2003 too.

    Now our Exchange 2010 implementation gets delayed because other departments have to gather time and money for an Outlook upgrade. Cached mode is no option on terminal servers (citrix).

    Still I am puzzled why deleting a mail in SP1 does update the folder fast in SP1. I does not update the folder in SP0.

  44. Chips O'Toole says:

    Under most circumstances, deletions with Outlook 2003 do seem to be faster against an Exchange 2010 SP1 Beta CAS than an RTM CAS; they take about three seconds, even without reducing the Maximum Polling Frequency a la KB2009942.  I’ve also noticed that when deleting messages from the folder view, you get the hourglass right away until the message disappears three seconds later, so you can’t hit the delete key twice on the same message and trigger the "Unknown Error" by double-deleting the same message. Unfortunately, you can’t do anything else during those three seconds, either.  The display also seems to update when single clicking on any other message in the same folder, which is also an improvement (with RTM, you’d have to click into a different folder, then click back to the original folder).  However, you can still trigger the double-deletion "Unknown Error" under at least one specific circumstance: if you open a previously read message by double-clicking it and delete the message by clicking on the delete button in the message window, when the message window disappears, the message is still listed and highlighted in the inbox folder view.  If you click anywhere else in the inbox, the message disappears instantly, but if you hit the delete key while the message is still highlighted, you get the dreaded "Unknown error" pop-up.  This doesn’t happen if the message you open is unread; in that case, following the same procedure, the message disappears from the inbox immediately.

    Microsoft clearly did something to change the way Outlook 2003 interoperates with a CAS, but I just don’t understand why they didn’t simply restore the UDP notifications and be done with it.  Three seconds to delete a message in the folder view is still an eternity for most users, especially when deleted messages disappeared from the inbox instantly the previous day, before their mailbox was migrated from the Exchange 2003 server to the Exchange 2010 server.  If Outlook 2003 is supported, then Microsoft shuld fully support it, not just "kinda" support it.  Removing UDP notifications has completely screwed us up here.

Comments are closed.

Skip to main content