Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
   

What's New and Cool in Exchange 2007

Page 1 | Page 2 | Page 3 | Page 4 | Page 5

Reliability and Availability Improvements:

        Continuous database replication support (aka Continuous Backup)

o       Using Local Continuous Replication (LCR) a 2nd copy of the Exchange database can be kept and failed over to if the primary ones gets corrupted or lost. Clustered Continuous Replication (CCR) provides similar support to LCR but for a clustered Exchange server without the need for expensive shared storage.

        Log files decreased from 5MB to 1MB in size

o       This allows for better support for log file shipping, which is used in LCR and CCR.

Management Improvements:

        E-mail life cycle (ELC) management

o       Provides support to control how long certain messages are kept until they are archived or deleted.

        Managed Folders

o       These allow administrators to setup folders, which show up in Outlook, that have policies applied to them. These policies can control how long messages will be kept, if they will be archived, sent to another mailbox and more. This is part of the ELC solution.

        Policy Support

o       Allows for rules, similar to Outlook Rules, that can be used to control what messages will be transmitted, copied, deleted, etc by Exchange. Transport and ELC rules use this infrastructure.

        Administrative control over Out-of-Office message generation

        True resource mailbox support

o       Allows rules and permissions to be setup to control who can book resources, workflow support for approval, reporting, and more.

        Active Directory leveraged for Exchange routing

        Message classification and policies

o       Can be used to control if a message can be forwarded, sent outside the company, always encrypted and more.

        Command line interface for all commands

o       Using the new PowerShell CLI, all Exchange functions can be automated.

        Support for 50 storage groups and 50 databases per server

o       Allow for more granular database allocation.

Security Improvements:

        Policy Support

o       Rules can be created that prevent certain messages from being delivered, copy messages to a shared mailbox, and more.

        Greater control over OWA

o       Can control what type of attachments can be viewed or accessed, if secondary factor authentication is required, and more

        Secured communication used by default

o       Servers within the same organization will always encrypt traffic between each other.

        Support for secured communications between business partners

o       Allows two organizations to encrypt e-mail between each other with minimum setup.

Discontinued Features: (See MS TechNet for the latest info)

        Support for migrating from Exchange 5.5

o       Must be running Exchange 2000 or higher to migrate to Exchange 2007

o       Active Directory Connector (ADC)

o       Site Replication Services (SRS)

       Public folder access using IMAP4, NNTP, and OWA (Added back in SP1 for OWA)

o       The big change, for some organizations, is you will NOT be able to get to Public Folders with Outlook Web Access in Exchange 2007.

        Active-Active clustering

o       Can no longer have a two node A-A cluster, must have at least one passive node.

        Routing groups

o       Replaced by AD Sites

        Administrative groups

o       Active Directory is used for all delegation purposes.

        Outlook Mobile Access

o       This was the very lightweight HTML client available at http://<server>/OMA in Exchange 2003.

OWA support for mailbox rule creation and editing (Added back in SP1)

        OWA support for S/MIME (Added back in SP1)

        Network News Transfer Protocol (NNTP)

        Non-MAPI top-level hierarchies in a public folder store

        X.400 Message transfer Agent (MTA)

        Connectors and migration tools for Novell GroupWise and Lotus Notes

        Exchange Web forms

o       InfoPath and SharePoint is Microsofts replacement for this.

        Exchange 2003 SDK workflow designer

        Protocol support for named pipes, SPX, AppleTalk, VINES, UDP, and NetBIOS

        Event Services and Event Sinks

o       They were first de-emphasized in Exchange 2003 and will no longer be in Exchange 2007

        Installable File System (M: drive)

o       They were de-emphasized in Exchange 2003 and will no longer be in Exchange 2007

        WMI classes

        Workflow Designer

        Transport event sinks

       

De-emphasized Functionality: (See MS TechNet for the latest info)

        Legacy API functionality

o       Many APIs are being dropped from Exchange 2007.

        Store Events

o       Exchange 2007 will be the last version to support these.

        Public folders

o       Still supported but are not required for Exchange 2007. Public folders will probably not be supported in the next major version of Exchange.

o       SharePoint 2007 will be utilized to provide collaboration support.

        Legacy APIs

o       WebDAV, CDO, and ExOLEDB will not be supported past Exchange 2007


For more information on other features missing from Exchange 2007 see these Microsoft TechEd and searchexchange.techtarget.com articles.

What's New and Cool in Exchange 2007

Page 1 | Page 2 | Page 3 | Page 4 | Page 5

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008