Datasheet

NOW, WHERE DID THAT GO? 35
Exchange Server 2003 Features Removed from Exchange Server 2010
Since t he release o f Exchange Server 2003, a number of Exchange Server 2003 (and Exchange
2000) features have been removed. Although most of these features will not affect the majority
of the Exchange deployments out there, you should keep them in mind and thoroughly evalu-
ate your existing messaging environment to make sure you are not dependent on a feature that
has no equivalent in Exchange Server 2010. Here are some of the Exchange Server 2003 features
and functionality that have b een removed from t he product:
Exchange 5.5 and Exchange Server 2000 interoperability is no longer available and there
is no transition path between these legacy versions and Exchange Server 2010. You cannot
install an Exchange 2010 server until your Exchange organization is in native Exchange
mode.
Outlook Mobile Access, the lightweight browser-based access for WAP-based mobile
phones, is not available. Nor are Exchange ActiveSync Always Up-to-Date notifications.
Non-MAPI public folder hierarchies are no longer available.
Public folder access via NNTP and IMAP4 is no longer available.
Network News Transport Protocol (NNTP) features have been cut from Exchange 2010
completely.
Routing groups and routing group connectors are no longer required once you have
completely migrated to Exchange Server 2010. In a native Exchange 2010 organization,
the message routing topology is determined using the Active Directory sites in which the
Exchange servers are located. Message delivery between Exchange 2010 servers in different
Active Directory sites is handled automatically.
Mailbox databases no longer have a streaming database file (STM file). All mail, regardless
of its original source, is stored in the EDB database file.
The Recipient Update Service functionality has been replaced. Email proxy addresses and
address list membership is set on a mail recipient object at the time of creation. They can be
updated from the EMS.
X.400 connectors are no longer available.
ExMerge can no longer be run from the Exchange 2010 server console; it can continue to
be run against Exchange 2007 mailboxes, but it must be run from a computer with Outlook
installed.
Mail recipient management using the Active Directory Users and Computers console
extensions no longer works. All recipient management must be performed through the
EMC. A few exceptions exist, of course, but using the EMC or the EMS is preferred. This
will also keep you from accidentally doing something that is not supported.
Administrative groups are no longer available. All permissions delegation is handled via
either a series of b uilt-in groups or via the new role-based authorization control (RBAC)
feature.
Development APIs and tools, such as CDO v1.2, CDO for Workflow, CDOEXM, Exchange
WMI classes, Exchange Web Forms, Workflow Designer, ExOLEDB, store events, and
transport event sinks, are no longer available.