Exchange 2010 SP3 and Exchange 2013

Wednesday, February 13, 2013

Yesterday Microsoft released Service Pack 3 for Exchange 2010.  You can download Exchange 2010 SP3 here.

We had been told at MEC 2012 that Exchange 2010 SP3 would be required for Exchange 2013 interoperability, and it is. Unfortunately, we learned yesterday that we now need to wait for Exchange 2013 Cumulative Update 1 to complete the coexistence story.  Exchange 2013 CU1 is due Q1 2013 -- in other words, within 90 days or so.  I expect that it might be sooner.

Exchange 2013 CU1 includes a number of fixes that will make the coexistence story much better and smoother.  It will be worth the wait.  This will be the first update for Exchange 2013 using the new service strategy and we can expect new CUs every quarter.

The good news is that this gives us time to install Exchange 2010 SP3 in our environments prior to introducing Exchange 2013 to production.  It also gives us time to test coexistence in a test lab, or as stated on the EHLO Blog, "Customers can test and validate this update in a representative lab environment prior to rolling out in their production environments as an important coexistence preparatory step before introducing Exchange Server 2013 CU1."

Exchange 2010 SP3 updates the schema version to 14734.  The Exchange 2013 schema version is 15137.  You can run the following command from a CMD prompt to determine your current Exchange schema version:

dsquery * CN=ms-Exch-Schema-Version-Pt,cn=schema,cn=configuration,dc=domain,dc=local -scope base -attr rangeUpper
You can refer to the Exchange table in the TechNet article, "How to determine the current Active Directory or Exchange Server schema version", to determine your current schema version.

Even if you have no plans to migrate to Exchange 2013 yet, Exchange 2010 SP3 includes several important updates and fixes, as well as allowing you to install Exchange 2010 on Windows Server 2012.  This is really huge, since Windows Server 2012 is an amazing platform and Exchange can really benefit from SMB3.  And since Windows 2012 includes PowerShell v3, this means that Exchange 2010 should be compatible with that version and the Management Framework 3.0.

SP3 also includes a new Sent Items Management feature for Outlook Web Access. This provides control over whether an item that is "sent as" you, or "on behalf of" you, is copied to your Sent Items folder and to the sender’s Sent Items folder. Before Exchange 2010 SP3, messages that are "sent as" you or "on behalf of" you are copied only to the sender's Sent Items folder.

You can configure the Sent Items Management feature in OWA on the Options page.

Note that RU6 for Exchange 2010 SP2 was also released yesterday.  Exchange 2010 SP3 includes all those fixes, plus additional ones.  Refer to the EHLO Blog article and TechNet for details.


  1. Hi Jeff,

    Actually Exchange 2010 SP3's schema version is 14734 which isn't the same as Exchange 2013 RTM (15137).

  2. not a good idea. I am not going to bash Microsoft for this one. I agree that Windows Server 2012 is great but these requirement changes make it hard for early adopters to get all the needed information when planning a 2013 deployment.

  3. Hi Jeff,

    do you know the "Sent Items" feature in Exchange 2013 OWA?
    There is no option like in Exchange2010 RU4/SP3 OWA.

    thank you
    Andreas H

  4. Is it confrmed that ex2010 will be wmf 3.0 compliant on server 2012? I'd be *very* surprised if all the PS 1.0 cmdlets would have all been updated and tested.

  5. Hi Jeff, there are few corrections to make:

    1) Sent Items Management feature is available in E2010 SP2 since Rollup 5(v2) I think, it is funny because it was not localized - a least SP3 added the full language pack;
    2) E2010, just like E2013 won't support SMBv3 - eg: this is even not supported for the FSW :/ - I doubt it will be supported for DBs, but we never know =°)
    3) E2010 is not compatible with PSv3, you need to install PSv2 in Windows 2012 - not funny, because this blocks the ability to use System Modules (PSv3) in the EMS (eg: FailoverClusters) :(

  6. Hi Jeff,

    regarding the schema update :
    Is a schema update for Exchange 2013 CU1 also necessary or is the schema upate for Exchange 2010 SP3 the only one, that need to install ?



Thank you for your comment! It is my hope that you find the information here useful. Let others know if this post helped you out, or if you have a comment or further information.