What’s new in Exchange 2013 SP1


You might have heard the news that Exchange 2013 Service Pack 1 (SP1) and the EWS Managed API 2.1 are now available. And you might be asking, what does that mean for me – and more importantly, what does that mean for my applications? Here’s the low down.

For the Exchange 2013 SP1 release:

  • The messages.xsd and types.xsd schema files have been updated. Remember, the types.xsd and messages.xsd files always contain the latest versions of the
    schema. The Exchange 2013 schema files now have the following names: messages-e15.xsd and types-e15.xsd.
  • To target Exchange2013 SP1 in your Autodiscover requests, set the SOAP Autodiscover RequestedServerVersion element to Exchange2013_SP1. If you’re using EWS, set the RequestServerVersion element value to Exchange2013_SP1 in your requests. 
  • Edge Transport servers are back! Edge Transport servers minimize the attack surface by handling all Internet-facing mail flow, which provides SMTP relay and smart host services for your Exchange organization, including connection filtering, attachment filtering, and address rewriting. If you’d like to read more about this, see Edge Transport Servers.

For the EWS Managed API 2.1 release:

  • The EWS Managed API installer now automatically adds the EWS Managed API DLL to the GAC and makes it available to all users of the computer.

The following functionality has been added to either the EWS Managed API, EWS, or both:

Functionality In EWS Managed API?  In EWS?
Read receipts can now be suspended for updates and deletions. Yes Yes
You can get moderated transport approval information. Yes Yes
Voting responses can be viewed. Yes Yes
The SetHoldOnMailboxes method and SetHoldOnMailboxes operation accept all the parameters in a
single object.
Yes Yes
eDiscovery searches can specify a language for search queries and a culture-specific format for date ranges. Yes Yes
The StreamingSubscriptionConnection object can now access the StreamingSubscription objects. Yes No
Conversations have a setting to indicate whether they contain email messages that are protected by IRM. Yes Yes
Meeting attendees can propose new start and end times for meetings and include them in their meeting response. No Yes
The SOAP Autodiscover GetUserSettings method now returns the GroupingInformation setting that is used maintain affinity for a
multiple mailbox event subscription.
Yes N/A

 

We’re in the process of updating the Exchange MSDN documentation for Exchange 2013 SP1, so stay tuned! You can also view these changes in the EWS schema files published with Exchange 2013 SP1 and Exchange Online, and by looking at the EWS Managed API.

Comments (9)

  1. Thieum22 says:

    You should publish an official nuget package. That would be nice.

  2. Mimi Gentz says:

    @Thieum22 – I will pass along your suggestion.

  3. Mimi Gentz says:

    Just wanted to let everyone know that the Exchange documentation on MSDN has been updated for SP1. For your convenience, I updated the original post to include links to the referenced APIs. Happy coding!

  4. Maugrim says:

    Any plans for a new EWS Java API release?

  5. Mimi Gentz says:

    No, no plans for an updated EWS Java API release.

  6. bretep says:

    Mimi, sorry for the email. I see that you answered the EWS Java API question I had. Sure would be great to have the EWS Java API updated.

  7. Rahul says:

    Instead of EWS Java API you can use "JWebServices for Exchange". Appears to be very current in its support of EWS up through Exchange 2013 and Exchange Online. API description contains a very detailed list of features and includes some features that are not implemented in the EWS Java API.

    http://www.independentsoft.de

  8. sky says:

    It seems like EWS Managed API 2.2 is out:

    http://www.microsoft.com/…/details.aspx

    Is there any information on what's new in EWS Managed API 2.2?

  9. The 2.2 update is a very small update. It adds an Attachment property to the GetAttachmentResponse class, enabling you to actually retrieve attachments given only the attachment ID. The updated reference documentation should publish to MSDN on Tuesday, and we'll post a message here as well.