Different sources of media released news stating that a larger beta of Exchange 12 is planned for mid-2006, with release planned for late 2006 or early 2007. As usual, the new version aim to cut costs, bolster security, and improve end-user messaging.

In this article series, I would like to touch base on the challenges ahead with 64 bit support and enhanced capabilities of the next version of Exchange, (code-named "E12") that could turn around your existing collaboration systems.

Introduction

Microsoft now believes that the much focused next version of Exchange, should be ready by 2006-2007 time frame. This decision came after Microsoft discarded the plan to come up with the minor version of Exchange Server that was expected this year (2005). Well, the good news is Exchange 12 will include 64 bit support, and the bad news is not the 32 bit.

The highlights from Exchange 12 are 64 bit support, database improvements & e-email/voice/fax integration according to the Microsoft officials. Exchange 12 will continue to rely on the Jet Database store which is similar to the current Exchange 2003. Microsoft had recently dropped the plan to integrate SQL database with Exchange 12, though the plan is to unifying the SQL Server and Exchange Server stores over time. In short, Microsoft is giving you as many challenges as it's solving with Exchange 12 version.

64 bit scenarios

Exchange makes heavy use of RAM to cache the database contents. A 64-bit version of Exchange allows us to build servers with more RAM, which should allow each server to support more users. 64 bit processing brings the opportunity to run on systems with ample RAM to the machine to cache an inefficient database. At the same time, customers need brand new hardware to run Exchange 12 with lots of RAM as well. Moving to 64-bit Exchange brought consolidation benefits and true scalability of the mail store.

The jump to 64-bit is particularly useful for server applications such as databases, as it allows servers to make use of much larger amounts of memory without resorting to techniques such as memory windowing. Outcome is a reduction of IOs per second, which leads to dramatic performance gains. Microsoft Exchange product team revealed, 4X increase in the number of users on the same disks or require 1/4 the disks to support the same users from a throughput perspective.

Role Based

One major improvement to Exchange 12 will be its role-based architecture, which will simplify deployment and help trim costs.

Exchange will make extensive use of server-based roles. In a small business, One Exchange server might handle all the tasks associated with receiving, organizing, distributing and storing e-mail. In large companies, may want individual servers that handle only one or two of these tasks, and Exchange 12 will allow these roles to be automatically assigned and the work separated.

The server roles include edge server, bridgehead server, unified messaging server, client access server, mailbox server, and public folder server.

• Edge Server or gateway is to manage Port 25 and hygiene functions.
• Bridgehead or hub is for policy management and transport functions.
• Unified messaging services is to incorporate PBX interface, voice mail and fax capabilities and its management.
• Client access services is basically to facilitate OWA, Active sync,OMA, RPC over HTTP, Web services etc.
• Mailbox services for mailbox and public folders.

Conclusion

While some of the features and capabilities that will be included in Exchange 12 are already available in other messaging systems, the new version of Exchange promises to be a major step forward for current users of Exchange. However, this new version might make the typical Exchange version migration slower and more complex.

Related Links

Exchange 12 - 64 bit only
http://blogs.technet.com/eileen_brown/archive/2005/11/15/e12_64bit_only.aspx

DAT316 Future Directions: Developing Custom Applications using the new Exchange 12 API’s
http://216.55.183.63/pdc2005/slides/DAT316_Batthish_Merrill.ppt

Exchange 12 will ship on DVD
http://blogs.technet.com/exchange/archive/2005/09/06/410343.aspx

Discuss this in