Hub Transport server role

The features provided by the Hub Transport server role in Exchange 2010 are now handled by the Transport service on Mailbox servers, the Mailbox Transport service on Mailbox servers, and the Front End Transport service on Client Access servers. For more information, see Mail Flow.

Unified Messaging server role

The features provided by the Unified Messaging server role in Exchange 2010 are now handled by the Unified Messaging service. The Unified Messaging service has components that run on both the Client Access server and the Mailbox server. For more information, see Voice Architecture Changes.

Exchange Management Console and Exchange Control Panel

The Exchange Management Console and the Exchange Control Panel have been replaced by the Exchange admin center. For more information, see Exchange Admin Center in Exchange 2013.

Outlook 2003 is no longer supported

To connect Microsoft Outlook to Exchange 2013, the use of the Autodiscover service is required. However, Microsoft Outlook 2003 doesn’t support the use of the Autodiscover service.

RPC/TCP access for Outlook clients

In Exchange 2013, all Microsoft Outlook client access is provided through Outlook Anywhere (RPC/HTTP). If you have Outlook clients in your organization, Outlook Anywhere is required.

Spell check

Outlook Web App no longer has built-in spell check services. Instead, it relies on the spell check services provided by web browsers.

Linked connectors

The ability to link a Send connector to a Receive connector has been removed. Specifically, the LinkedReceiveConnector parameter has been removed from New-SendConnector and Set-SendConnector.

Anti-spam agent management in the EMC

In Exchange 2010, when you enabled the anti-spam agents on the Hub Transport server, you could manage the anti-spam agents in the Exchange Management Console (EMC). In Exchange 2013, when you enable the anti-spam agents in the Transport service on a Mailbox server, you can't manage the agents in the Exchange admin center (EAC). You can only use the Exchange Management Shell. For information about how to enable the anti-spam agents on a Mailbox server, see Enable Anti-Spam Functionality on a Mailbox Server.

Connection Filtering agent on Hub Transport servers

In Exchange 2010, when you enabled the anti-spam agents on a Hub Transport server, the Attachment Filter agent was the only anti-spam agent that wasn't available. In Exchange 2013, when you enable the anti-spam agents in the Transport service on a Mailbox server, the Attachment Filter agent and the Connection Filtering agent aren't available. The Connection Filtering agent provides IP Allow List and IP Block List capabilities. For information about how to enable the anti-spam agents on a Mailbox server, see Enable Anti-Spam Functionality on a Mailbox Server.

Managed Folders

In Exchange 2010, you use managed folders for messaging retention management (MRM). In Exchange 2013, managed folders aren’t supported. You must use retention policies for MRM.

Note:
Cmdlets related to managed folders are still available. You can create managed folders, managed content settings and managed folder mailbox policies, and apply a managed folder mailbox policy to a user, but the MRM assistant skips processing of mailboxes that have a managed folder mailbox policy applied.

Port Managed Folder wizard

In Exchange 2010, you use the Port Managed Folder wizard to create retention tags based on managed folder and managed content settings. In Exchange 2013, the Exchange admin center doesn’t include this functionality. You can use the New-RetentionPolicyTag cmdlet with the ManagedFolderToUpgrade parameter to create a retention tag based on a managed folder.

Directory lookups using Automatic Speech Recognition (ASR)

In Exchange 2010, Outlook Voice Access users and callers who dialed into UM auto attendants could use speech inputs using Automatic Speech Recognition (ASR) to search for users listed in the directory. In Exchange 2013, this feature isn't supported. However, all other Outlook Voice Access and auto attendants can use speech inputs to navigate Outlook Voice Access and auto attendant menus.

Exchange Best Practice Analyzer

In Exchange 2010, the Exchange Best Practice Analyzer examined your Exchange deployment and determined whether the configuration was in line with Microsoft best practices. In Exchange 2013, the Exchange Best Practice Analyzer has been retired.

Mail flow troubleshooter

In Exchange 2010, the mail flow troubleshooter assisted you in troubleshooting common mail flow problems. In Exchange 2013, the mail flow troubleshooter has been retired. You can now use the messaging tracking feature in EAC in Exchange 2013. For more information, see Track Messages with Delivery Reports.

Performance monitor

In Exchange 2010, the Performance Monitor was included in the Exchange toolbox to allow you to collect information about the performance of your messaging system. Performance Monitor is commonly used to view key parameters while troubleshooting performance problems. In Exchange 2013, the Performance Monitor has been retired from the toolbox. You can still find the Performance Monitor under Administrative Tools in Windows Server 2008.

Performance troubleshooter

In Exchange 2010, the Performance Troubleshooter helped you to locate and identify performance-related issues that could affect an Exchange server. In Exchange 2013, the Performance Troubleshooter has been retired from the toolbox.

Routing Log Viewer

In Exchange 2010, you could use the Routing Log Viewer to open a routing log file that contained information about the routing topology. The tool consisted of a parser and a public user interface. In Exchange 2013, the routing log viewer has been retired.

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.

Storage groups

Exchange 2010 uses database copy functionality. For information, see 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 Backup, Restore, and Disaster Recovery.

User Datagram Protocol (UDP) notifications

Support for User Datagram Protocol (UDP) notifications is removed from Exchange 2010. This impacts the experience when Outlook 2003 clients connect to their mailboxes on Exchange 2010 server. For more information, see Microsoft Knowledge Base article 2009942, In Outlook 2003, e-mail messages take a long time to send and receive when you use an Exchange 2010 mailbox.

Cluster continuous replication (CCR)

Exchange 2013 uses database availability groups (DAGs) and mailbox database copies. For information, see High Availability and Site Resilience.

Local continuous replication (LCR)

Exchange 2013 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience.

Standby continuous replication (SCR)

Exchange 2013 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience.

Single copy cluster (SCC)

Exchange 2013 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience.

Setup /recoverCMS

Exchange 2013 uses Setup /m:recoverServer. For information, see Recover a Database Availability Group Member Server.

Clustered mailbox servers

Exchange 2013 uses DAGs and mailbox database copies. For information, see High Availability and Site Resilience.

Client authentication using Integrated Windows authentication (NTLM) for POP3 and IMAP4 users

NTLM isn't supported for POP3 or IMAP4 client connectivity in Exchange 2013. Connections from POP3 or IMAP4 client programs using NTLM will fail. If you’re running the RTM version of Exchange 2013, the recommended POP3 and IMAP4 setting alternatives to NTLM are:

• Kerberos (GSSAPI)
  
  
• Plain Text Authentication with SSL
  
  

If you’re using Exchange 2013, to use NTLM, you must retain an Exchange 2007 server in your Exchange 2013 organization.

Document access

Outlook Web App can’t be used to access Microsoft SharePoint document libraries and Windows file shares.

S/MIME

S/MIME isn’t supported in Outlook Web App.

Spell check

Outlook Web App relies on the web browser to provide spell check services.

Export-Mailbox and Import-Mailbox cmdlets

In Exchange 2013, use export requests or import requests. For more information, see Mailbox Import and Export Requests.

Move-Mailbox cmdlet set

In Exchange 2013, use move requests to move mailboxes. For information, see Mailbox Moves in Exchange 2013.

ISInteg

In Exchange 2013, use New-MailboxRepairRequest.

Managed Folders

In Exchange 2007, you use managed folders for messaging retention management (MRM). In Exchange 2013, managed folders aren’t supported. You must use retention policies for MRM.

Note:
Cmdlets related to managed folders are still available. You can create managed folders, managed content settings and managed folder mailbox policies, and apply a managed folder mailbox policy to a user, but the MRM assistant skips processing of mailboxes that have a managed folder mailbox policy applied.

Directory lookups using Automatic Speech Recognition (ASR)

In Exchange 2007, Outlook Voice Access users and callers who dialed into UM auto attendants could use speech inputs using Automatic Speech Recognition (ASR) to search for users listed in the directory. In Exchange 2013, this feature isn't supported. However, all other Outlook Voice Access and auto attendants can use speech inputs to navigate Outlook Voice Access and auto attendant menus.