Exchange 2010 Service Pack 3 and Exchange 2007 SP3 UR10 released with Exchange 2013 Co-existence support
This service pack is pretty important, as it enables the following:
- Coexistence with Exchange Server 2013, once Cumulative Update 1 for Exchange 2013 is released.
- Support for installation of Exchange Server 2010 on Windows Server 2012
- Support for Internet Explorer 10
- For Hybrid Exchange deployments, future coexistence with Wave 15 of Office 365 and Exchange 2010.
As usual check out the release notes for Exchange 2010 SP3 and ensure if you’re using any third party software that the vendor supports SP3 also. Naturally, the same goes for Exchange 2013 if you’re considering it, and always make sure you’ve got backups that you’re confident you can restore to.
For Exchange 2007 organizations hoping to upgrade, Update Rollup 10 for Exchange 2007 Service Pack 3 has also been released. Just like Exchange 2010 SP3, the missing link is now only Exchange 2013 CU1.
My advice would be to try things out in your lab environment before considering implementing in production and consider giving the community a few weeks to discover anything unusual.
Downloads and more information
Relevant KB Articles at Launch
It’s been a little while since the last update to the Exchange Environment Report, and it’s a workhorse I use regularly in my work to (reasonably) quickly get a snapshot of important information about an Exchange org that’s easy to read.
I’ve got a list as long of my arm of updates to include, but I’ve been holding off partly because I’ve been busy, and also because Exchange 2013 and co-existence updates for 2007 & 2010 are nearly upon us (and no, I don’t know dates!)
However Neil Johnson has done a great job of adding in the necessary updates to allow the script to function correctly for Exchange 2013, including when it’s co-existing with previous versions. I’ve added a few minor changes myself and we’ve both tested it in our respective 2013 and 2010 environments (mine without co-existence). A big thank you to Neil for his efforts – especially as it’s re-ignited my interest in implementing additional features.
Who likes having to add tons of domains to their SAN certificate? The answer.. Nobody!! If you've got 100 domains in your Exchange org, hell - even 15 - and want to use AutoDiscover, then you've got a task on your hands.
Unless you take a look at my two part article series on MSExchange.org! This article shows off an easy technique (and multiple ways to achieve it) to use AutoDiscover Redirection to allow you to have a simple SAN certificate (e.g. one with just mail.domain.com and AutoDiscover.primarydomain.com) and have as many domains work properly with AutoDiscover as you like.
I love PinPoint DNS zones. They're a quick and easy replacement for Split DNS and make single namespace deployments quick and easy. With the ability to use .local names on public certificates now a dying prospect, using a technique like this is pretty essential.
In my article on MSExchange.org I explain more on why, when and how to implement DNS Pinpoint zones. Check it out now!
The latest update rollups for Exchange 2010 SP1 (Update Rollup 7), Exchange 2010 SP2 (Update Rollup 4) and Exchange 2007 SP3 (Update Rollup 8) have been re-released.
The reason for the re-release is due to a premature expiry of the certificate used to sign the binaries. You should update as soon as possible, otherwise it might not be possible to install future update rollups or service packs.
I’ve contributed to a piece over on SearchExchange where we discuss this in more detail, read it here