Prerequisites for a Resource Forest Deployment

Topic Last Modified: 2009-11-09

To support a resource forest topology, Office Communications Server must be deployed in your resource forest and configured at least with one-way trust between the resource forest and all user forests (such that the resource forest trusts all user forests).

Note

You must establish a two way trust between the resource forest and user forests to enable distribution group expansion when groups from user forests are synchronized as contacts to the resource forest.

If you have not deployed Office Communications Server, see the Office Communications Server 2007 R2 Planning Guide documentation and the Deploying Office Communications Server 2007 R2 documentation.

Figure 8 shows how an example organization, Contoso, configured an Enterprise pool in its resource forest.

Figure 8.   Example of a resource forest topology

Ee303781.fe59dfe4-593c-4aa7-bbd2-4e1b7ff4cb05(en-us,office.13).jpg

After you have deployed Office Communications Server in the resource forest, complete the following steps:

  • Create disabled accounts with the corresponding attributes for each user account in the user forests. This process will vary depending on whether or not you have Microsoft Exchange Server deployed in the resource forest, as explained in the topics that follow.
  • Enable these disabled accounts for Office Communications Server.