On March 1, Microsoft announced that it was making Exchange 12 beta 1 available to TechNet and MSDN subscribers as a community technology preview (CTP). When beta 1 first began, late last year, it was a private beta restricted to about 1400 Microsoft customers, all of whom had to be nominated by Microsoft employees. MVPs and a few third-party developers were also nominated, but—even including participants in the Technology Adoption Program (TAP)—only a relative handful of the tens of thousands of Exchange-using sites were in on the beta. That’s about to change dramatically, since there are more than 200,000 TechNet and MSDN subscribers, all of whom will have access to beta 1.
This isn’t the first time Microsoft’s offered a CTP; you may remember that Exchange 2003 SP2 was released as a CTP in August 2005. As with the SP2 CTP, the Exchange 12 CTP is being released so customers can get familiar with it in their own environments. It’s not supported for production use (obviously), and Microsoft has already told beta 1 customers that they won’t be able to upgrade from beta 1 directly to the released version.
As part of the CTP announcement, the product team also announced that beta 2, coming later this year, will be a public beta, so we’ll all be able to discuss it to our hearts’ content. Until then, both reviewers (which technically means me) and CTP participants are bound by the relevant NDAs and EULAs.
One thing that’s no longer under NDA: Microsoft’s finally starting to talk publicly about the new continuous replication features in Exchange 12. There are two flavors of continuous replication: local continuous replication (LCR) copies transaction log data to a second local volume, essentially giving you a protected local copy of your data. Clustered continuous replication (CCR) is cooler; with CCR, cluster nodes don’t have to share disk resources, meaning that geographically dispersed clusters get much, much easier to design and deploy. Look for more on LCR and CCR in future columns.
Interestingly, the CTP builds will be made available in both 32- and 64-bit versions. This is a smart move on Microsoft’s part, because customers that haven’t decided on their forward path from Exchange 2000 (or even Exchange 5.5) will be able to evaluate Exchange 12 features (if only in an early state) on the hardware they already have. I don’t expect any changes in their previous commitment to release the production version of Exchange 12 as a 64-bit-only product, though.
MSDN subscribers can download the Exchange 12 CTP starting today, while TechNet subscribers will get the bits as part of their March delivery. If you’re not already a subscriber to one of these two programs, you can subscribe through Microsoft’s web site.

CCR certainly resembles the Domino clustering model since 1996…wonder if this means MS will stop criticizing the Domino model’s storage of redundant copy of user’s mail? Imitation is the sincerest form of flattery. 🙂
There’s a lot more to CCR than my simplistic description above, but I don’t have time to write a longer explanation– I’ll post one here when I can, then we can duke it out.
Thanks Paul! That is very good news. IMHO, Beta 1 is somewhat “feature incomplete”, but it will be nice to see it out in the hands of folks that are planning on adopting Exchange 12 fairly soon after it releases.
Paul,
I’m looking for a little direction on this new CTP. Basically, I just downloaded it through my MSDN subscription. I completely understand that it is BETA1 and not a finished product. However, I’ve had several odd problems after installing it in VMWare w/Windows 2003 SP1 x86.
1. The unified messaging piece fails to install.
2. After installing and restarting, the main System Managmenet snap-in will not open. It gives me an error saying that I don’t have rights. I was able to work around this by simply opening a blank MMC session and adding the snap-in into it.
3. Outlook WebAccess does not work. After typing in my username and password I get an ASP.net (that is after I modified the web.config) to show the error. Basically the error says it find the ‘Microsoft.Exchange.ClientAccess.OWA.something.something.dll’ (I can’t remember the whole name’. However, a dll similar to this one seems to be in the ‘bin’ folder of the owa website.
Anyway, is there any help out there to get this thing going? Is there anyway to get into the beta program? I’m working on a .NET 2.0 Line-of-business application that I like to integrate with outlook’s calendar via the new webservice APIs. Anyway thanks again for a great product. From what I’ve seen E12 is going to rock!
I haven’t had any of those three problems; without more diagnostic information (like the specific errors, et al) I can’t really offer any suggestions. You might try posting your queries on the public microsoft.exchange.* newsgroups.
As for getting on to the beta, anyone at MS can nominate you. Do you have a local account rep, developer support contact, or anything like that at MS?