I’m posting a set of Sample Architectural Design documents that were adapted from a real-world Multi-site Hybrid Exchange deployment. The documents are built entirely on Best Practices and I’ve taken the liberties of updating elements of the design to reflect changes in the Exchange 2013 Architecture (and of course to remove and sensitive confidential information).
This was a fairly large implementation and took the combined efforts of a large team of engineers to complete all of the deliverables, who inspired me and continue to do so. You may not need all of these document components, but it’s good to see how a large Messaging Environment can be broken down into its constituent components and architected in detail.
Read First: These design documents were derived from detailed research and consulting with expert engineers. Feel free to use as a reference, but always verify the requirements of your project against the data in these guides. Roadchimp takes no responsibility for any implementation issues that you encounter. Make sure that you implement licensed copies of Microsoft Software with valid Microsoft Support in place prior to making any changes to a production environment. Further more, make sure that you consult with Microsoft’s resources to ensure that your hardware is fully supported by Microsoft for deploying Exchange 2013, Windows Active Directory and other architectural components.
I will start posting links to these templates here:
- Part 1: Implementation Scenario
- Part 2: High-level Architectural Design Document
- Part 3: Exchange Design Overview and Virtualization
- Part 4: Exchange Mailbox Server Design
- Part 5: Exchange CAS Build
- Part 6: Exchange Hybrid Design
- Exchange Anti-virus Protection
- Disaster Recovery
- Backup and Restore
- Exchange Server Management Functions
- Design Validation
- Build Sequence
- Server Build Requirements