After you have successfully copied the tree structure and global settings attributes, the next step is to set up the access control entries (ACEs) that allow the Office Communications Server service to access the new global settings tree.

For both Office Communications Server 2007 and Live Communications Server 2005 with SP1, the ForestPrepaction of the Lcscmd.exe command-line tool sets up the permissions. You must run the forest preparation step again to create the ACEs for administrators and for Office Communications Server services and to validate the new global settings tree. You cannot use the Prep Forest wizard for this migration step. For details about forest preparation for Live Communications Server 2005, see the Live Communications Server 2005 Active Directory Preparation Guide, available at http://go.microsoft.com/fwlink/?LinkId=154652 .

Important:
You must use the version of the command line tool LcsCmd.exe that is included with Live Communications Server 2005 to perform this step. You cannot use the version that is included with Office Communications Server 2007 R2.

For Live Communications Server 2005 with SP1, you also need to run domain preparation. In Live Communications Server 2005 with SP1, domain global groups control domain access. Most global settings permissions are created by either the DomainPrep or the DomainAdd action of the Lcscmd.exe command-line tool. Because global settings are located on every domain controller after deployment, it is not necessary to rerun DomainAdd. Therefore, rerunning DomainPrep for each Live Communications Server 2005 domain is sufficient to create the ACEs for the new global settings tree. For details about the domain preparation step for Live Communications Server 2005, see “Live Communications Server 2005 with SP1: All Technical Documents” at http://go.microsoft.com/fwlink/?LinkId=139639 .

This step is complete when all permissions have been created for the new global settings tree, and the new global settings tree is replicated to forest global catalogs. Depending on the topology and replication configuration, full replication can take anywhere from minutes to days.

See Also