You've probably heard the saying, "The more you learn, the less you know." This adage certainly applies to Exchange Server 2003 and its many complexities, such as migration, storage, administration, and disaster recovery. Combine those complexities with the need to understand related technologies, such as Active Directory (AD), SANs, and third-party tools, and the challenge is obvious. Some Exchange 2003 intricacies, such as migration, the Recipient Update Service (RUS), or securely exposing Exchange access to and from the Internet, are expected. Others are less obvious. Specifically, let's consider two Exchange 2003 components—global size limit settings and public folder replication—and how each affects the other. We'll also look at related oddities that show up in the message transport system.
The Scenario
While recently working on a consulting engagement, I was reminded of how global size limits affect public folder replication. One of my clients built a pristine Exchange 2003 organization with the intent of moving the company's legacy Exchange Server 5.5 environment to the new Exchange 2003 infrastructure. The company has multiple, distributed Exchange 5.5 organizations. As part of its messaging-system consolidation, the company plans to consolidate its two data centers; planning and design for the new environment, including a migration strategy, has been finished. Exchange 2003 is functioning as the routing hub for all environments, essentially handling all inbound and outbound mail. . . .
Register
