Exchange 2016 and its futures announced at ignite 2015. Many exciting futures are on the way. Here is summary of topology requirements and few of the highlights, what has changed with Exchange Server 2016.
- Single Role = Mailbox Server Role ( Prior to Exchange 2016, multi-role deployments were MS best practices, With E16 , there is no choice but single role (-:
- Edge Role will be released with RTM release.
- CAS Server role has been transitioned into Client Access proxy , service components. At this point all server roles collapse into single Mailbox Server role.
- DAG no longer requires administrative access point. Only two operation systems are required Windows 2012 and Windows 10 Server.
- Mailbox Connectivity the protocol instance is always local to the active database copy. Once the request reaches to correct mail Server all required connectivity stays on that server
- Rendering data will occur on the Server which hosts the active mailbox, OWA clients etc.
- Clients wont connect directly to MBX role, all connectivity will go trough Client Access Service located on the MBX Server. Entire CAS server role has been moved into CAS Service
- Maximum 16 Mailbox Servers Per DAG
- 100 database copies/Server
- Due to recent architectural changes done, Database failovers are 33% faster compared to Exchange 2013. How passive database copies are accessed is changed in Exchange 2016.