Both the Release Candidate (RC) for Exchange 2010 and the Service Pack 2 for Microsoft Exchange 2007 were just released, and if you're at all considering migrating to Exchange 2010, get both of them now. Exchange 2007 SP2 lets you install the release candidate for Exchange 2010 within the same environment as Exchange 2007, so you can have the two versions of Exchange coexist for better testing and transitioning.
And the Exchange 2010 RC allows an in-place upgrade to the forthcoming RTM version, so you can use this co-existence strategy to smooth your eventual migration to Exchange 2010. In fact, that's the best way to migrate, as you cannot perform an in-place upgrade from Exchange 2007 to Exchange 2010; instead, you have to move your mailboxes and such over.
A final installation note: You do need to have Windows Server 2008 to run the Exchange 2010 RC.
And why bother with Exchange 2010? In previous blogs, I've outlined what's new. But two capabilities I'm excited about are worth repeating here:
- New high-availability functionality: After working with CCR and Cluster Services in Exchange 2007, it's a joy in Exchange 2010 to move to Database Availability Groups (DAG) that use failover clustering features without actually having to configure a cluster. (Note that you have to be working with the Enterprise version of Server 2008 to see this feature in action.) I took the time last week to set this up myself, and it was so much easier than the high-availability tools in Exchange 2007: Just configure the DAG and create the database replicas -- you're all set. Scott Schnoll, a principal technical writer at Microsoft's Exchange team, has posted a few videos on the process.
- Voicemail preview: Aren't voicemails annoying? We are just so impatient these days (at least I am), and voicemails demand time to listen to before you can figure out if they're worth the listen. Well, the Unified Messaging role in Exchange 2010 can take the voicemail and transcribe it to text (speech-to-text) so that you see the transcribed version. Is it 100 percent accurate? No, but accents and quirks in the way we speak make that impossible. From what I've seen, it's pretty close.
In addition to the RC being released, the Exchange team has provided a host of complementary tools worth investigating. They include the following:
- Exchange Web Services Managed API (EwsAPI): This provides a managed interface for developing client applications that use Exchange Web Services, so this will help you develop or migrate your Exchange applications over to 2010.
- Management Pack for Exchange Server 2010 (SCOM MP): Remembering that Microsoft Operations Manager (MOM) is now System Center Operations Manager (SCOM), there is a new 2010 management pack that lets you monitor Exchange 2010. Note: This pack works only on SCOM 2007 SP1 or SCOM 2007 R2.
- Exchange Server Remote Connectivity Analyzer: This online tool lets you test client connectivity and inbound e-mail scenarios. Note: You can use this tool to test your Exchange 2007 connectivity as well.
- Microsoft Exchange Server JetStress Tool for Exchange Server 2010: This helps Exchange administrators confirm the performance and stability of the disk subsystem before releasing Exchange 2010 into the production environment.
- Microsoft Exchange Load Generator (LoadGen) for Exchange Server 2010: This simulation tool measures the impact of MAPI, OWA, IMAP, POP, and SMTP clients.
Microsoft has gone to great lengths to take Exchange from humble beginnings all the way to the powerful position it holds (about two-thirds of the mail server market). Exchange 2010 will continue that trend as more and more organizations switch to Exchange each year. If you're new to Exchange, be sure to check out Microsoft's free e-learning tools. Even if you're not about to switch to Exchange 2010, having Exchange skills can be helpful in this volatile job market.
I'd like to hear from readers regarding what messaging platform you currently use, Microsoft or otherwise. In addition, if you have any requests for the Microsoft Exchange team to consider as it develops future versions of Exchange, please comment on those; I'll be sure to share them with the team.
[Feel free to follow me on Twitter: http://twitter.com/JPBruzzese ]