You hear from us pretty often. While we absolutely want you to read Ross’ blog and factor in transaction log space in your capacity planning or listen to Perry talk about how we’ve shifted to a ser...
Published Nov 30, 2011
Version 1.0
Blog Post
OK, I have a couple general Tips for the Exchange builders out there:
1. Resist the temptation to use your load balancers for Hub Transport roles, instead leverage the native resilience available with multiple destination IPs and/or MX records. Because most Load Balancers are deployed in a Proxy configuration they re-write the IP headers and will wreck havoc on your receive connectors and anti-spam engines (very difficult to isolate traffic when it all appears to come from a single IP).
2. Even if you are planning to publish all services to a single FQDN, go ahead and "reserve" generic names for HTTP, SMTP, and RPC services in your new UCC/SAN certificate request. Companies grow and change, and Exchange may need to grow and change with it. Being able to adapt to new TLS requirements, add a new OWA site for FBA while keeping the original default at IWA, and a host of other "tweaks" could force you to go back to the "re-provisioning your certificate" well much earlier than you'd like (and not all providers let you re-provision for free).
3. PowerShell. PowerShell. PowerShell.