Configuration container. For details about migrating global settings to the Configuration container, see .
2.Mature Exchange implementation
Do you have a mature Exchange implementation for which you have been able to assess the impact of replication traffic on your network? If so, Exchange configuration settings are already replicating forest-wide, so adding Office Communications Server global settings to the Configuration container should not significantly impact your network. Choose the Configuration container.
Do you have a distributed forest that has Active Directory domains or sites without fast, reliable connections to a domain controller in the root domain? If so and you plan to deploy servers running Office Communications Server (except Edge servers, which are not joined to the domain) in these locations, choose the Configuration container.
4.Empty root domain
Does your forest have a root domain that does not host users or servers? If so, are there any child domains without a fast, reliable connection to a domain controller in the root domain? If so and you plan to deploy servers running Office Communications Server (except Edge servers, which are not joined to the domain) in such a domain, choose the Configuration container. This situation is similar to the distributed forest situation described above.
Are you performing a new, straightforward installation, in an environment without Live Communications Server, Exchange, or a complex forest? If so, choose the System container to reduce Active Directory replication traffic on your network.
In This Section
Migrating Global Settings Container
With Office Communications Server 2007 R2, the recommended container for Office Communications Server global settings is the Configuration container, which is the default container. In previous versions of Office Communications Server, the default container was the root domain System container. Although storing global settings in the System container has advantages, such as faster replication and fewer replicated copies, in centralized topologies, this approach might not perform as well in geographically distributed topologies if root domain availability is insufficient. If you deployed Live Communications Server 2005 with Service Pack 1 (SP1) or Office Communications Server 2007 with global settings stored in the System container and experience performance problems, such as long service start time or long replication delays when you manage global settings, you can migrate from the System container to the Configuration container. The Microsoft Office Communications Server 2007 Global Settings Migration Tool is designed for this purpose. This tool is available at the Microsoft Download Center .