Export (0) Print
Expand All

Discontinued Features

Exchange 2010
 

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2013-01-10

This topic discusses the components, features, and functionalities that have been removed, discontinued, or replaced in Microsoft Exchange Server 2010. For information about API and development tool changes, see Migrating from Earlier Technologies to Exchange 2010.

Contents

Discontinued Features from Exchange 2010 RTM to Exchange 2010 SP1

Discontinued Features from Exchange 2007 to Exchange 2010

Discontinued Features from Exchange 2003 to Exchange 2010

This section lists the Microsoft Exchange Server 2010 RTM features that are discontinued in Microsoft Exchange Server 2010 SP1.

 

Feature Comments and mitigation

Export-Mailbox and Import-Mailbox cmdlets

Use export requests or import requests. For more information, see Understanding Mailbox Import and Export Requests.

Enable-AntispamUpdates

Use Forefront Security for Exchange Server to obtain automatic anti-spam updates. For more information, see Forefront Online Protection for Exchange.

Federated Delivery

Use Tenant Mail Flow control. For more information, see Understanding Transport Options.

ISInteg

Use New-MailboxRepairRequest or New-PublicFolderDatabaseRepairRequest.

Managed folders in the Exchange Management Console (EMC)

In Exchange 2010 SP1, use the Exchange Management Shell to administer managed folder features such as managed default folders, managed custom folders, and managed folder mailbox policies. You can use the EMC and the Shell to manage retention policies and retention tags, the new messaging records management (MRM) feature introduced in Exchange 2010. For more information, see Deploying Messaging Records Management.

This section lists the Microsoft Exchange Server 2007 features that are discontinued in Exchange 2010.

 

Feature Comments and mitigation

Exchange WebDAV

Use Introduction to Web Services or Differences between the EWS Managed API and EWS. 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 to Exchange 2010.

 

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.

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 an Exchange 2010 server. For more information, see Microsoft Knowledge Base article 2009942, Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode.

noteNote:
Support for User Datagram Protocol (UDP) notifications is added in Microsoft Exchange Server 2010 Service Pack 1 (SP1) Rollup 3 (RU3). To obtain Exchange 2010 SP1 Update RU3, see Microsoft Knowledge Base article 2009942, Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode.

 

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.

 

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 in the RTM version of Exchange 2010. Connections from POP3 or IMAP4 client programs using NTLM will fail. If you’re running the RTM version of Exchange 2010, the recommended POP3 and IMAP4 setting alternatives to NTLM are:

  • Kerberos (GSSAPI)

  • Plain Text Authentication with SSL

If you’re using the RTM version of Exchange 2010, to use NTLM, you must retain an Exchange 2003 or Exchange 2007 server in your Exchange 2010 organization.

Support for NTLM authentication for POP3 and IMAP4 connectivity has been brought back in Exchange 2010 SP1. For more information, see Set-PopSettings and Set-ImapSettings.

 

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 RTM. This feature has been brought back in Exchange 2010 SP1.

User-selectable themes

Users can't change the theme in Outlook Web App RTM. This feature has been brought back in Exchange 2010 SP1.

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. This feature has been brought back in Exchange 2010 SP1.

 

Feature Comments and mitigation

Move-Mailbox cmdlet set

Use move requests to move mailboxes. For information, see Understanding Move Requests.

Return to top

This section lists the Exchange Server 2003 features that are discontinued in Exchange 2010.

 

Feature Comments and mitigation

Proxy address generators

Use the Shell.

ExCDO 1.2.1

Use Introduction to Web Services.

MAPI32

Use Introduction to Web Services.

CDOEX (CDO 3.0)

Use Introduction to Web Services.

Exchange WebDAV extensions

Use Introduction to Web Services.

ExOLEDB

Use Introduction to Web Services.

Store events

Use Introduction to Web Services.

Return to top

 

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 Introduction to 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.

User Datagram Protocol (UDP)

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 an Exchange 2010 server. For more information, see Microsoft Knowledge Base article 2009942, Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode.

 

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.

 

Feature Comments and mitigation

Calendar search

The search feature isn’t available for the Calendar folder in Outlook Web App.

Views in the Contacts folder

The Address Cards and Detailed Address Cards views are no longer available in Outlook Web App. The option is to use the Reading Pane when viewing Contacts. Contacts can’t be sorted by location.

Printing

Contacts and Tasks don’t include a print option in Exchange 2010 Outlook Web App.

 

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)

In Exchange Server 2010 RTM, use the Export-Mailbox cmdlet or the Move Request cmdlet set.

In Exchange Server 2010 SP1, use the Mailbox Repair Request cmdlet set or the Move Request cmdlet set. For information, see Recipient Cmdlets.

Mailbox Manager Policies

Use retention policies, the MRM feature introduced in Exchange 2010, or managed folder mailbox policies, the MRM feature introduced in Exchange 2007 (also available in Exchange 2010). For more information, see Understanding Messaging Records Management.

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.

 

Feature Comments and mitigation

Monitoring and status node

Use a monitoring solution such as System Center 2012 Cloud & Datacenter Management.

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

In Exchange Server 2010 RTM, use the Export-Mailbox cmdlet or the Move Request cmdlet set.

In Exchange 2010 SP1, use the Mailbox Repair Request cmdlet set 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

 © 2010 Microsoft Corporation. All rights reserved.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft