[This topic's current status is:
Content Complete.]
Topic Last Modified: 2010-01-26
This topic discusses the components, features, or functionality that has been removed, discontinued, or replaced in Microsoft Exchange Server 2010. For information about API and development tool changes, see Migrating from Older Technologies.
Contents
Discontinued Features from Exchange 2007 to Exchange 2010
Discontinued Features from Exchange 2003 to Exchange 2010
Deemphasized Functionality from Exchange 2003 to Exchange 2010
Discontinued Features from Exchange 2007 to Exchange 2010
This section lists the Exchange Server 2007 features that are discontinued in Exchange 2010.
APIs and Development Features
High Availability Features
|
Feature
|
Comments and mitigation
|
|
Client authentication using Integrated Windows authentication (NTLM) for POP3 and IMAP4 users
|
NTLM isn't supported for POP3 or IMAP4 client connectivity. The recommended POP3 and IMAP4 setting alternatives to NTLM are:
-
Kerberos (GSSAPI)
-
Plain Text Authentication with SSL
Connections from POP3 or IMAP4 client programs to Exchange 2010 will fail.
If you need this functionality, retain an Exchange 2003 or Exchange 2007 server in your Exchange 2010 organization.
|
|
Feature
|
Comments and mitigation
|
|---|
|
Document access
|
Can't use Microsoft Office Outlook Web App to access Microsoft Office SharePoint document libraries and Microsoft Windows file shares.
|
|
Web Parts
|
Web Parts aren't supported in Exchange 2010.
|
|
User-selectable themes
|
Users can't change the theme in Outlook Web App.
|
|
Reading pane at the bottom of the page
|
There is no option to display the reading pane at the bottom of the Outlook Web App window.
|
Recipient Related Features
Discontinued Features from Exchange 2003 to Exchange 2010
This section lists the Exchange Server 2003 features that are discontinued in Exchange 2010.
|
Feature
|
Comments and mitigation
|
|---|
|
Routing groups
|
Exchange 2010 uses Active Directory site-based routing. For information, see Understanding Message Routing.
|
|
Administrative groups
|
Exchange 2010 uses the Exchange 2007 split permissions model that's based on universal security groups. For information, see Understanding Split Permissions.
|
|
Intelligent Message Filter
|
Exchange 2010 uses anti-spam agents in the Hub Transport and Edge Transport server roles. For information, see Understanding Anti-Spam and Antivirus Functionality.
|
|
Link state routing
|
Exchange 2010 uses Active Directory site-based routing. For information, see Understanding Message Routing.
|
|
Routing objects
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
Network-attached storage
|
Exchange 2010 supports Internet SCSI (iSCSI).
|
|
Exchange Installable File System (ExIFS)
|
Use Exchange Web Services or MAPI.
|
|
Event service
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
Recovery storage group
|
Exchange 2010 uses the recovery database. For information, see Recovery Databases.
|
|
Feature
|
Comments and mitigation
|
|---|
|
Microsoft Exchange Connector for Novell GroupWise and migration tools
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
Microsoft Exchange Connector for Lotus Notes
|
Use the appropriate tools for coexisting and migrating from Lotus Notes. These tools are available at the Interoperability Bridges and Lab Center Web site.
|
|
Feature
|
Comments and mitigation
|
|---|
|
Network News Transfer Protocol (NNTP)
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
POP3 or IMAP4 graphical user interface (GUI) management
|
Use the Exchange Management Console (EMC) or the Exchange Management Shell. For information, see Managing POP3 and IMAP4.
|
|
X.400 message transfer agent (MTA)
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
SMTP virtual server instances
|
Use Exchange 2010 SMTP connectors. For information, see Understanding Send Connectors and Understanding Receive Connectors.
|
|
Feature
|
Comments and mitigation
|
|---|
|
Non-MAPI top-level hierarchies in a public folder store
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
Public folder access by using NNTP
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
Public folder access by using IMAP4
|
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization.
|
|
Feature
|
Comments and mitigation
|
|
Client authentication using Integrated Windows authentication (NTLM) for POP3 and IMAP4 users
|
NTLM isn't supported for POP3 or IMAP4 client connectivity. The recommended POP3 and IMAP4 setting alternatives to NTLM are:
-
Kerberos (GSSAPI)
-
Plain Text Authentication with SSL
Connections from POP3 or IMAP4 client programs to Exchange 2010 will fail.
If you need this functionality, retain an Exchange 2003 or Exchange 2007 server in your Exchange 2010 organization.
|
Recipient-Related Features
|
Feature
|
Comments and mitigation
|
|---|
|
Exchange extensions in Active Directory Users and Computers
|
Exchange 2010 includes recipient management in the EMC. For information, see Managing Mailbox Servers.
|
|
Exchange Server Mailbox Merge wizard (ExMerge.exe)
|
Use the Export-Mailbox cmdlet or the Move Request cmdlet set. For information, see Recipient Cmdlets.
|
|
Recipient Update Service
|
Use the Update-AddressList and Update-EmailAddressPolicy cmdlets. To replace the full functionality of the Recipient Update Service, you can use the Task Scheduler to schedule these Shell commands. For information, see Task Scheduler.
|
Tools and Management Features
Deemphasized Functionality from Exchange 2003 to Exchange 2010
This section lists the Exchange 2003 features that are deemphasized in Exchange 2010.
Return to top