Chapter purpose
The supplied Mastering Exchange book devotes substantial space to needs assessment, network planning and deployment. That discipline remains valid, but the supported software and prerequisites have changed.
Learning objectives
- Use the supportability matrix before procurement.
- Explain why Exchange prepares the AD schema/configuration.
- Plan writable DC/GC availability and DNS.
- Define a controlled deployment sequence.
Why this matters in a real company
An unsupported Exchange deployment can turn routine maintenance into a company-wide outage. Planning reduces upgrade and recovery risk.
2.1 Start with supportability, not hardware shopping
Verify Exchange build, Windows Server version, .NET requirements, Active Directory support and coexistence before ordering or installing. Microsoft maintains a supportability matrix for this reason.
Exchange SE should be deployed only on supported configurations.
2.2 Exchange stores organization data in Active Directory
Exchange uses Active Directory for recipient and organization configuration. Preparing the forest extends schema and creates Exchange-related configuration. Directory health and replication therefore matter before setup.
Microsoft recommends installing Exchange on member servers rather than domain controllers.
2.3 Plan names and certificates before publishing services
Client and SMTP namespaces should be decided before certificates are purchased. DNS, firewall publishing and load balancing should follow the chosen service names, not invent competing names independently.
2.4 Deployment sequence
- Confirm supportability.
- Patch Windows and install prerequisites.
- Verify AD, DNS and replication health.
- Prepare AD where required.
- Install Exchange on supported member server.
- Apply current Exchange updates/security updates.
- Configure namespaces and certificates.
- Configure mail flow.
- Validate databases, recipients and clients.
- Run health checks and capture baseline.
Exchange and Active Directory preparation
Exchange preparation writes schema and configuration data into Active Directory. In multi-domain or large forests, the administrator must allow time for directory replication before assuming every site sees the same Exchange configuration. A clean AD replication baseline before setup prevents Exchange from becoming the first application to expose an existing directory problem.
The Exchange server should have reliable access to writable domain controllers and Global Catalog servers in the site. DNS resolution, time, network reachability and directory health belong on the preflight checklist.
Post-installation is part of deployment
Installation completing successfully is only the midpoint. Configure service namespaces, install the correct certificates, create or validate outbound mail flow, set accepted domains, review Receive connectors, create mailbox databases according to the design and confirm monitoring/backup/HA.
Record the initial healthy state. That baseline becomes extremely valuable later when an upgrade or network change causes a subtle problem.
Exchange setup readiness fails
The target server is ready, but its AD site has no writable Global Catalog and Windows updates are behind.
Decision: Stop the install and fix prerequisites rather than bypassing checks.
Evidence: Record supported versions, AD site/DC health, patch state and successful readiness checks.
Hands-on lab
Build a pre-install worksheet for a fictional Exchange SE deployment and map each requirement to evidence.
Troubleshooting exercise
- PrepareAD fails: verify permissions, schema-master health and replication.
- Installed server cannot locate directory services: check site and writable GC.
- Certificate plan does not match names: correct namespace design before deployment.
Field checklist
- Supportability checked.
- Member server used.
- Writable GC available.
- AD replication healthy.
- Namespaces defined.
- Certificate plan defined.
- Update/health-check process documented.
Current technical references
The supplied PDF books are used as a historical curriculum map. Current implementation guidance is checked against current Microsoft documentation.