(UDP) 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.
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 POP3 and IMAP4. Managing 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 Receive Connectors. Understanding Send Connectors and Understanding
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:
z Kerberos (GSSAPI)
z 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 you can use the Task Scheduler to schedule these Shell commands. For information, see Update-AddressList and Update-EmailAddressPolicycmdlets. To replace the full functionality of the Recipient Update Service, Task Scheduler.
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 Management and Understanding Retention Tags and Retention Policies. Understanding Messaging Records Clean Mailbox tool
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.
Return to top
© 2010 Microsoft Corporation. All rights reserved. Legal Information
Applies to: Exchange Server 2010 SP2 Topic Last Modified: 2010-01-20
Because organizations tend to group their management tasks around a core set of server roles, Exchange 2010 maps Exchange Server management to this same approach. A server role is a unit that logically groups the required features and components needed to perform a specific function in the messaging environment. The requirement of a server role is that it is a server that could be run as an atomic unit of scalability. A server role is composed of a group of features.
Server roles, the primary unit of deployment, enable administrators to easily choose which features are installed on an Exchange server. Logically grouping features in server roles offers the following advantages:
z Reduces attack surface on an Exchange server.
z Allows you to install and configure an Exchange server the way you intend to use it. z Offers the ability to fully customize a server to support your business goals and needs. The following figure illustrates a domain with each server role deployed.
Exchange 2010 includes the following server roles:
z Mailbox Server This server hosts mailboxes and public folders. For more information about the Exchange 2010 Mailbox server role, see Overview of the Mailbox Server Role.
z Client Access Server This is the server that hosts the client protocols, such as Post Office Protocol 3 (POP3), Internet Message Access Protocol 4 (IMAP4), Secure Hypertext Transfer Protocol (HTTPS), Outlook Anywhere, Availability service, and Autodiscover service. The Client Access Server also hosts Web services. For more information about the Exchange 2010 Client Access server role, see Client Access.
z Unified Messaging Server This is the server that connects a Private Branch eXchange (PBX) system to Exchange 2010. For more information about the Exchange 2010 Unified Messaging server role, see Unified Messaging.
z Hub Transport Server This is the mail routing server that routes mail within the Exchange organization. For more information about the Exchange 2010 Hub Transport server role, see Transport and Overview of the Hub Transport Server Role.
z Edge Transport Server This is the mail routing server that typically sits at the perimeter of the topology and routes mail in to and out of the Exchange organization. For more information about the Exchange 2010 Edge Transport server role, see Transport and Overview of the Edge Transport Server Role.
© 2010 Microsoft Corporation. All rights reserved. Legal Information
Migration wizard Use the 2003 to Exchange 2010. For information, see New-MoveRequest cmdlet or the Local Move Request and Remote Move Request wizards to move mailboxes from Exchange Understanding Move Requests. Exchange Profile Redirector tool
(ExProfRe) Use the Autodiscover service. For information, see Understanding the Autodiscover Service.
Exchange Server 2010
Overview of Exchange 2010 Server Roles
Exchange Server 2010 > Getting Started With Exchange 2010 > Exchange Server 2010 Roadmap for Exchange Features
Exchange Server 2010 > Getting Started With Exchange 2010 >
Applies to: Exchange Server 2010 SP2 Topic Last Modified: 2011-10-13
This roadmap helps you get acquainted with all the features in Microsoft Exchange Server 2010. The first section lists all the features that can be managed by using either the Exchange Management Console (EMC) or the Exchange Management Shell. This section also shows you how to navigate to the feature in the EMC and provides a link to the corresponding management topic.
However, not all features and tasks can be managed in the EMC. Therefore, the second section lists the features that can be managed only in the Shell and provides links to the corresponding cmdlet reference topic.