Microsoft has released updates for Exchange Server 2013, 2010, and 2007 as part of their quarterly release cadence. The 2007 and 2010 RUs are bug fixes to the product and not introducing new features (well techincally 2007 a few) while the Service Pack for 2013 adds a load of function and features. Like all past updates and future updates the download is huge as it is the entire bit-set rolled up into the distributable so don’t be alarmed to see a 1.53GB file coming down the pipe.
Information regarding the releases and new features may be found on the TechNet Exchange blogs and the links to the downloads may be found below. The TAP program these past few go-arounds have included the Exchange MVPs as well as external client which means the most critical set of eyes were looking at this 2013 release.
Released: Exchange Server 2013 Service Pack 1
Released: Update Rollup 5 for Exchange 2010 Service Pack 3 and Update Rollup 13 for Exchange 2007 Service Pack 3
Windows Server 2012 R2 and Database Availability Groups
Microsoft releases patches and upgrades to Exchange Server 2007 and 2010
Yesterday Microsoft release the long-awaited service pack 3 for Exchange Server 2010. Service pack 3 is a requirement for interoperability and migrations to Exchange Server 2013 – a roadblock that has now been removed. In addition to Exchange 2013 co-existence service pack 3 introduces support for Windows Server 2012, Internet Explorer 10, and as always, includes current and previous bug fixes.
In addition to service pack 3, Microsoft release RU 6 for Exchange Server 2010 sp2 and RU 10 for Exchange Server 2007 sp3. Interestingly RU 10 for Exchange Server 2007 introduces co-existence with Exchange Server 2013 as well removing the migration roadblock for 2007. RU6 for Exchange Server 2010 sp2 simply introduced bug fixes with no significant new features (that is what sp3 s for).
Below are the links and version numbers of the three patches. CU1 for Exchange Server 2013 is coming soon as well (and listed as a recommendation prior to co-existence but not required).