Exchange 2016 is no longer providing multiple Exchange roles. Instead everything is packaged in a single server.

I am writing this post with a grin on my face after seeing a comment of mine being censored at the MS Exchange Team blog.

My comment for Exchange Server 2016 Architecture went something like this (don't remember the exact wording sorry):
Happy to see the return of the Exchange 2003 architecture. Can we have the Exchange System Manger back now?

My comment was just a joke with a pinch of truth in it. Exchange has certainly evolved a lot since 2003 and there is little comparison between the two.

On the other hand most small/medium Exchange installations never went beyond the single server setup. So for most Exchange Organizations the basic architecture never really changed since Exchange 4. Even the Exchange Edge role (which remains distinct also in Exchange 2016) was not as widely adopted as I would have expected.

The reference to the Exchange 2003 System Manager was intended to remind them that on-premises Exchange users are still not happy with the Exchange Administrative Centre. We all know that the cloud guides all decisions. So the return of a rich client administrative interface is not a priority. But feedback should still be welcome!!

And now that I mention the cloud, I cannot help pointing out something else. I have no doubt that the only reason why the Exchange Architecture is changing, is to satisfy the cloud. Quite certainly the Office 365 Engineers identified the most cloud efficient architecture and this is what Exchange 2016 will deliver.

Although I am no cloud evangelist, hope this does not sound like some anti-cloud rant. It only makes sense for Microsoft to stay focused on its cloud ambitions. I just thought this was a funny way how I could post about the changes in Exchange 2016 architecture and to pull the ear of those censoring the Exchange Team Blog.