Difference between the Exchange Server 2010/2013 and Exchange 2016
Server
So in this article series, I am going to introduce you about the
Microsoft Exchange Server 2016 new enhancements and the features that have been
removed or replaced in Exchange 2016.
This is the first article of this series and here I am going to
introduce you about the features which are discontinued from legacy Exchange
versions, like: 2010 & 2013.
Finally after a long wait, Microsoft launch Exchange Server brand
new version called “Microsoft Exchange 2016” with lots of new features and also
remove some of previous version features.
Microsoft Exchange Server 2016 mostly focused on cloud
technologies and provide a fully compatibility with all the Microsoft cloud
services, like: Office 365, Microsoft Azure and many mores, which helps
organizations to reduce the cost.
What’s discontinued in Exchange Server 2016
Discontinued features from Exchange Server 2013:
CAS Server
Role: The Client Access
server role has been replaced by Client Access services that run on the Mailbox
server role. The Mailbox server role now performs all functionality that was
previously included with the Client Access server role.
MAPI/CDO library: The MAPI/CDO library has been replaced by Exchange Web Services
(EWS), Exchange ActiveSync (EAS), and Representational State Transfer (REST)* APIs.
If an application uses the MAPI/CDO library, it needs to move to EWS, EAS, or
the REST APIs to communicate with Exchange 2016.
The
following features are being de-emphasized in Exchange 2016 and may not be
included in future versions of Exchange.
Ø Third-party
replication APIs
Ø RPC
over HTTP
Ø Database
Availability Group support for failover cluster administrative access points
Discontinued
features from Exchange Server 2010:
There are lots of
features which were also discontinued from Exchange Server 2013 also but if we
compare with the Exchange 2016, this list increased more no of removal or
replaced features.
Here are the table
for the discontinued features in Exchange 2016 from Exchange 2010.
|
Features
|
Comments
and mitigation
|
|
HUB
Role
|
The Hub Transport server role has been replaced by
Transport services which run on the Mailbox server role. The Mailbox server role
includes the Microsoft Exchange Transport, Microsoft Exchange Mailbox
Transport Delivery, the Microsoft Exchange Mailbox Transport Submission, and
the Microsoft Exchange Frontend Transport service.
|
|
UM
Role
|
The Unified Messaging server role has been replaced
by Unified Messaging services which run on the Mailbox and Client Access
server roles. The Mailbox server role includes the Microsoft Exchange Unified
Messaging service and the Client Access server role includes the Microsoft
Exchange Unified Messaging Call Router service.
|
|
MAPI/CDO
library
|
The MAPI/CDO library has been replaced by Exchange
Web Services (EWS), Exchange ActiveSync (EAS), and Representational State
Transfer (REST)* APIs. If an application uses the
MAPI/CDO library, it needs to move to EWS, EAS, or the REST APIs to
communicate with Exchange 2016.
|
|
EMC
and ECP
|
The Exchange Management Console and the Exchange
Control Panel have been replaced by the Exchange Admin Center (EAC). EAC uses
the same virtual directory (/ecp) as the Exchange Control Panel
|
|
Legacy
Outlook 2003 version not supported
|
To connect Microsoft Outlook to Exchange 2016, 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 2016, Microsoft Outlook clients can
connect using Outlook Anywhere (RPC/HTTP) or MAPI over HTTP Outlook 2013
Service Pack 1 and later. If you have Outlook clients in your organization,
using Outlook Anywhere and/or MAPI over HTTP is required.
|
|
Linked
connectors
|
The ability to link a Send connector to a Receive
connector has been removed. Specifically, theLinkedReceiveConnector 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 a Hub Transport server, you could manage the anti-spam agents in
the Exchange Management Console (EMC). In Exchange 2016, when you enable the
anti-spam agents on a Mailbox server, you can't manage the agents using the
EAC. You can only use the Shell. For information about how to enable the
anti-spam agents 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 2016, when you enable the
anti-spam agents 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.
|
|
Managed
Folders
|
In Exchange 2010, you use managed folders for
messaging retention management (MRM). In Exchange 2016, managed folders
aren’t supported. You must use retention policies for MRM.
|
|
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 2016, 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 can use speech inputs using
Automatic Speech Recognition (ASR) to search for users listed in the
directory. Speech inputs could be also used in Outlook Voice Access to
navigate menus, messages, and other options. However, even if an Outlook
Voice Access user is able to use speech inputs, they have to use the
telephone key pad to enter their PIN, and navigate personal options.
In
Exchange 2016, authenticated and non-authenticated Outlook Voice Access users
can’t search for users in the directory using speech inputs or ASR in any
language. However, callers that call into an auto attendant can use speech
inputs in multiple languages to navigate auto attendant menus and search for
users in the directory.
|
I hope all of my reader will like this post, if you have any query or feedback, mail me: arunkalagarh@gmail.com
In next article I will explain you about the brand new features of
Exchange Server 2016……. So wait me J
About the Author and his contribution
Author,
Arun Chaudhary
MCP, MCTS, MCITP, MCTS, ITIL,
VCA-Cloud, VCP, MCSE
AD/ Exchange SME, Founder/ Owner of
Q-Lative Solutions
About
me: Hello dear readers, I
am working as an AD & Exchange SME and handling complex setup of 60K users
with hundreds of Email Servers. I am the founder and owner of “Q-Lative
Solutions”. Under this IT Training and Consultancy we offer only customized
course for my clients who are from across the world. I have already trained
more than 500+ students in customized training. We offer a complete package for
training on real world scenario and setup by SME’s. We offer a full package of
products, Eg:
Messaging
Expert: This package include
Exchange 2010, 2013, 2016, Office 365, Proof point Gateway, Blackberry, EOP and
Google-App, Migration and Office 365 Migration with Hybrid configuration wizard
and all the installation, configuration and functionality on a very cheaper
price in all the world.
Wintel
Admin: This package include
Windows Server 2008, R2, 2012, Basic of Active Directory, Hyper-V, SCVMM,
VMware (VCP), and Server Patching, monitoring and Backup / Restoring on real
world scenario.
AD
Admin/ Expert: Windows Server 2008, R2,
2012 including in-depth knowledge of Active directory and Windows Server Roles,
AD-DS, AD-CS, AD-FS, IIS, WDS, RRAS and VPN Server installation, configuration
and managing.
Note: We offer SCOM, ITIL, SNOW, Remedy training fully
free and mandatory with all the courses. We also offer live servers
troubleshooting and how to create Incidents/ Problem Tickets, Change Request
with complete ITIL Process, which used by all MNC.
No comments:
Post a Comment