Discontinued Features and De-Emphasized Functionality
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
| Feature | Comments and mitigation |
|---|---|
Exchange WebDAV |
Use Exchange Web Services or EWS Managed API. Alternatively, you can maintain an Exchange 2007 server for mailboxes that are managed by applications that use WebDAV. For more information, see Migrating from WebDAV. |
Architecture Features
| Feature | Comments and mitigation |
|---|---|
DSProxy |
Exchange 2010 uses the RPC Client Access service and the Address Book service to perform this functionality. For more information, see Understanding RPC Client Access and Understanding the Address Book Service. |
Storage groups |
Exchange 2010 uses database copy functionality. For information, see Understanding Mailbox Database Copies. |
Extensible Storage Engine (ESE) streaming backup APIs |
Exchange 2010 uses Volume Shadow Copy Service (VSS)-based copies, such as Windows Server Backup and the VSS-plug-in included with Exchange 2010. For information, see Understanding Backup, Restore and Disaster Recovery. |
High Availability Features
| Feature | Comments and mitigation |
|---|---|
Cluster continuous replication (CCR) |
Exchange 2010 uses database availability groups (DAGs) and mailbox database copies. For information, see High Availability and Site Resilience. |
Local continuous replication (LCR) |
Exchange 2010 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience. |
Standby continuous replication (SCR) |
Exchange 2010 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience. |
Single copy cluster (SCC) |
Exchange 2010 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience. |
Setup /recoverCMS |
Exchange 2010 uses Setup /m:recoverServer. For information, see Recover a Database Availability Group Member Server. |
Clustered mailbox servers |
Exchange 2010 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience. |
Client Access 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:
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. |
Outlook Web App Features
| 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
| Feature | Comments and mitigation |
|---|---|
Move-Mailbox cmdlet set |
Use move requests to move mailboxes. For information, see Understanding Move Requests. |
Return to top
Discontinued Features from Exchange 2003 to Exchange 2010
This section lists the Exchange Server 2003 features that are discontinued in Exchange 2010.
Architecture Features
| 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. |
Connector Features
| 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. |
Protocol Features
| 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. |
Public Folder Features
| 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. |
Client Access 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:
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
| Feature | Comments and mitigation |
|---|---|
Monitoring and status node |
Use a monitoring solution such as System Center Operations Manager. |
Message Tracking Center node and tracking mechanism |
Use the Tracking Log Explorer and Message Tracking tools. For information, see Understanding Message Tracking. |
Mailbox Recovery Center |
Use the Restore-Mailbox cmdlet. |
Mailbox Management Service |
Use messaging records management (MRM) or retention policies. For information, see Understanding Messaging Records Management and Understanding Retention Tags and Retention Policies. |
Clean Mailbox tool |
Use the Export-Mailbox cmdlet or the Move Request cmdlet set. For information, see Recipient Cmdlets. |
Migration wizard |
Use the New-MoveRequest cmdlet or the Local Move Request and Remote Move Request wizards to move mailboxes from Exchange 2003 to Exchange 2010. For information, see Understanding Move Requests. |
Exchange Profile Redirector tool (ExProfRe) |
Use the Autodiscover service. For information, see Understanding the Autodiscover Service. |
Return to top
Deemphasized Functionality from Exchange 2003 to Exchange 2010
This section lists the Exchange 2003 features that are deemphasized in Exchange 2010.
| Feature | Comments and mitigation |
|---|---|
Proxy address generators |
Use the Shell. |
CDO 1.2.1 |
|
MAPI32 |
|
CDOEX (CDO 3.0) |
|
Exchange WebDAV extensions |
|
ExOLEDB |
|
Store events |
|
Exchange 2003 Virus Scanning Application Programming Interface (VSAPI) |
If you need this functionality, retain an Exchange 2003 server in your Exchange 2010 organization. |
Return to top