Tag Archives: Mailbox Server

Exchange 2016 – What’s new?

Now that Microsoft has Exchange Server 2016 it’s time to have a closer look at what’s new in the product. It might not be a surprise that it looks a lot like Exchange Online. Not surprisingly since Microsoft is developing Exchange for the cloud, and Exchange on-premises is just a spin-off of Exchange Online, released on a quarterly basis.

It might be blunt to say, but Exchange 2016 is nothing more than Exchange 2013 Service Pack 2, if you look at the version numbering with PowerShell (Get-ExchangeServer | Select Name,AdminDisplayVersion) you’ll see that it’s actually a minor upgrade from 15.0 (Exchange 2013) to 15.1 (Exchange 2016).

The question can be raised why a new version? It’s all about the support lifecycle, and get rid of support for Exchange Server 2007. Customers need a new version, from a support point of view or from a license point of view (software assurance).

But, back to Exchange 2016… it is a new version, and with a new version also new features are introduced and other features are deprecated or removed.
Continue reading Exchange 2016 – What’s new?

Exchange 2013 Front-End Back-End

One of the major changes in 2013 is the new architecture. Exchange 2013 only has two server roles:

  • Client Access Server role;
  • Mailbox Server role;

The other server roles that were available in Exchange 2007 and Exchange 2010 still exist, but are now known as Services. The Client Access Server (CAS15) consists of the Client Access Front-End (café) and the Front-End Transport (FET). The Mailbox Server role consists of the Mailbox Service, Unified Messaging Service, Client Access service (ambiguous naming I’m afraid) and the Hub Transport Services. The only exception is the Edge Transport Server role. When Exchange 2013 goes to RTM there won’t be an Edge Transport Server, this will be released with SP1 of Exchange 2013.

Continue reading Exchange 2013 Front-End Back-End