Exchange 2013 Server Role Architecture
A must read blog for all Exchange gurus!
The Past: Exchange 2007 and Exchange 2010
In 2005, we set out developing Exchange 2007. During the preliminary planning of Exchange 2007, we realized that the server architecture model had to evolve to deal with hardware constraints, like CPU, that existed at the time and would exist for a good portion of the lifecycle of the product. The architectural change resulted in five server roles, three of which were core to the product:
- Edge Transport for routing and anti-malware from the edge of the organization
- Hub Transport for internal routing and policy enforcement
- Mailbox for storage of data
- Client Access for client connectivity and web services
- Unified Messaging for voice mail and voice access
Read the complete blog at https://blogs.technet.com/b/exchange/archive/2013/01/23/exchange-2013-server-role-architecture.aspx
Read my favorites blogs:
Designing a backup less Exchange 2010 Architecture
Microsoft Exchange 2010 CAS Array – Steps and Recommendations
Appear Offline in Microsoft Office Communicator Server 2007
Microsoft Exchange 2010 Test cases