Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


Return to article

Microsoft Plots the Next Exchange Server Version
 

The next version of Microsoft Exchange Server, known internally as Exchange 12 (E12), will build on the many improvements Microsoft has made to Exchange Server 2003 since the company first released the product in late 2003. E12 will synchronize with a major update of Microsoft Office Outlook and Windows Mobile, both of which will be optimized for E12.
  
"With E12, we're making major investments in IT professionals, security, and information workers," David Thompson, corporate vice president in charge of the Exchange Server Group, told me this week. "Email is mission critical, and we want to manage the cost and complexity out of the system, provide a secure environment in which administrators can protect corporate assets and comply with regulations and policy, and enable end users to get more from email both at work and away from the office."
  
E12 will boast several major improvements over Exchange 2003. Taking a cue from Windows Server 2003, E12 will use a roles-based architecture that will let you easily configure Exchange machines as edge servers, bridgehead servers, unified messaging servers, client access servers, mailbox servers, or public folder servers. This simplified approach will also consolidate new messaging types--fax, Voice over IP (VOIP), and voicemail--into Exchange. E12 will also include an improved and simplified management console, provide for continuous backups, and expose functionality via Web services interfaces. Each E12 edition will be available in both 32-bit and x64-based 64-bit versions, Thompson said.
  
From a security standpoint, E12 will build on the Intelligent Message Filter (IMF) and antivirus functionality in Exchange 2003 and the Sender ID framework that will first appear in Exchange 2003 Service Pack 2 (SP2) in late 2005. The product will also add perimeter message hygiene functionality through its edge server features and will provide a secure messaging feature that will essentially establish a secure pipe across the Internet between E12 edge servers. 
  
For end users, Microsoft will develop E12 in tandem with the next version of Microsoft Office Outlook, codenamed Outlook 12, and an upcoming version of the Windows Mobile platform, which powers Pocket PC and smart phone devices. These products will be released simultaneously, or nearly simultaneously, in 2006, providing a much better experience with each product. Microsoft Outlook Web Access (OWA), which was significantly improved in Exchange 2003, will also be broadly updated, and E12's unified messaging capabilities will make it more of a one-stop shop for messaging needs.
  
From a technical standpoint, E12 will continue to use the Jet database engine and won't use new database technology, as had been previously expected with Kodiak, a set of Exchange technologies that were originally to have been rolled into the next major release of Exchange. Although Thompson didn't get into the details of this decision, the near-constant delays in Windows Future Storage (WinFS) were likely at the heart of the decision. E12 does appear to hit at the core needs of users, however, and answer many of the complaints and problems customers have with the current product.
  
Before E12 ships next year, Microsoft will ship various mobility and antispam enhancements and an improved management interface for public folders in Exchange 2003 SP2. In addition, Exchange customers are advised to check out the many post-release to manufacturing (RTM) Exchange 2003 Web release tools that Microsoft has shipped, including the excellent Exchange Server Best Practices Analyzer. Functionality from that product will be rolled into E12 as well, I'm told.







Reader Comments

Exchange 12 ... so it looks like they're upping the Exchange version number up to 12 to sync it up with the Office version numbers ... Exchange 2003 is only version 6.5.

Anonymous User -January 20, 2005

Exchange 2003 + 2 new features people will use + 10 features no one will use = Exchange 12.

Anonymous User -January 20, 2005

Its just a code name you fool geez...

Anonymous User -January 20, 2005

Its getting more and more difficult to avoid installing Exchange.....

Anonymous User -January 21, 2005

ah 64 bit at last! Good, because larger Exchange installs really need more than the max 3GB RAM it can address at the moment. But a real shame that they are sticking with JET. Why wait for WinFS which was in turn held up by Yukon (SQL 2005). JET is a relational database that supports the SQL language. So is SQL Server 7/2000/2005. I don't understand why they are taking so long to move away from JET and to a proper database that doesn't need to be taken offline to do a defrag! Any more detail on the VOIP features? Will exchange be able to do PBX stuff?

Anonymous User -January 21, 2005

I have met David Thompson and he is definitely more of a software engineer-type and less of a marketing-type [i.e. Gord Mangione]. I believe that he worked with David Cutler over at Digital and came over to MS when they brought Cutler to start work on the NT kernel. I think that he did a lot of work on VMS clustering. A very nice person and a brilliant engineer. Paul, you should try to get an interview with this guy. He really has been part of a lot of Digital and MS history and has been involved in a lot of development activities at Microsoft.

Anonymous User -January 21, 2005

Yes, I find it strange they are sticking with a JET database. Still, any admin with any idea about anything will have the mail store in a SQL server database.

Anonymous User -January 22, 2005

>why they are taking so long to move away from >JET and to a proper database that doesn't need >to be taken offline to do a defrag The database is automaticly defraged daily (take a look in your Event Viewer) however, if you would like to compact the database it must be taken off-line.

Anonymous User -January 22, 2005

The anonymous poster who posted "any admin with any idea about anything will have the mail store in a SQL server database" must be smoking something. It is not possible to have your mail store in SQL, way to many other Exchange components would cease functioning including mail delivery.

Anonymous User -January 25, 2005

I don't know if Exchange 2003 can take advantage of Physical Address Extension (PAE), but if it can, then using the /PAE switch, in combination with the /3GB switch in your boot.ini file should allow you to use memory above the 4GB limit. See article here: http://support.microsoft.com/default.aspx?scid=kb;en-us;328882

Anonymous User -January 27, 2005

it makes me sick at how long its taking to move to the sql backend. So much for distributed replication and onlne remote dr. When your server room is on fire you still have to do an exchange setup /disaster recovery at the remote site!!!!? unless of course you own a stretched cluster.. hows that for tco for a mailserver - ffs

Anonymous User -April 11, 2005

it makes me sick at how long its taking to move to the sql backend. So much for distributed replication and onlne remote dr. When your server room is on fire you still have to do an exchange setup /disaster recovery at the remote site!!!!? unless of course you own a stretched cluster.. hows that for tco for a mailserver - ffs

Anonymous User -April 11, 2005
Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement