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).
If you have not deployed Office Communications Server,
see the
Figure 8 shows how an example organization, Contoso, configured an Enterprise pool in its resource forest.
Figure 8. Example of a resource forest topology
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.