Sunday, 7 August 2016

Understanding Role architecture in Exchange Server 2016

Ashwin Venugopal

The role architecture in Exchange Server 2016 is more simplified and reduced. Earlier in Exchange Server 2007 and Exchange Server 2010, there were five server roles, in Exchange Server 2013, there were three server roles. In Exchange Server 2016, all of the server role functionalities except for Edge Transport server are combined to only one role.
All key functionalities that existed in the Mailbox server role, the Client Access Server role, the Hub Transport Server role, and the Unified Messaging Server role are now added to Mailbox server.
  • The Mailbox server role interacts with Active Directory Domain Services (AD DS) domain controllers and global catalogs.
  • The Mailbox server of Exchange Server 2016 now includes the logic to route a specific protocol request to the correct destination endpoint, and this hosts all components required for processing, rendering, and storing the data.
  • The Mailbox server role also accepts client connections because it includes all client access components.
  • Clients still do not communicate with back-end services directly. Front-end client access services on the Mailbox server will accept all forms of client connections, and then proxy these connections to the back-end services on the Mailbox server that hosts the destination database.
  • Exchange Server 2016 uses proxy for most of the client request except telephony requests used for Unified Messaging functionality. For these requests, Exchange Server 2016 uses redirection.

Now with consolidated roles, Exchange Server 2016 provides following benefits:

  • The ability to use the same hardware and configuration for all Exchange servers in an organization.
  • Fewer physical or virtual servers that have Exchange Server deployed.
  • Easier management.
  • Better scalability and reliability.

No comments:

Post a Comment