X hits on this document

340 views

0 shares

0 downloads

0 comments

15 / 123

This section provides an overview of the steps required to migrate global settings. For details about how to use the Microsoft Office Communications Server 2007 Global Settings Migration Tool to accomplish the migration, see Using the Global Settings Migration Tool to Move to Configuration Container.

Important:

If you decide to migrate your global settings to the Configuration container and you plan to migrate from a prior version of Office Communications Server to Office Communications Server 2007 R2, you must perform the global settings migration first. Once you upgrade to the Office Communications Server 2007 R2 Active Directory schema, you can no longer use this tool to migrate your global settings.

You can migrate global settings in the following scenarios:

Live Communications Server 2005 with SP1, System container to Configuration container

Important:

For Live Communications Server 2005 with SP1, you can store global settings in the Configuration container only if you apply Windows update provided in the Microsoft Knowledge Base article 911996. For details, see Knowledge Base article 911996, "Description of the update for Live Communications Server 2005: February 10, 2006, rereleased July 11, 2006," at http://go.microsoft.com/fwlink/?LinkId=132177.

Office Communications Server 2007, System container to Configuration container

Important:

After you begin to migrate global settings, do not attempt to move or modify users until the final step in the process is complete.

Migrating global settings involves the following seven steps:

1.Copying the tree structure to the Configuration container.

2.Copying the global settings attributes.

3.Running forest preparation and, for Live Communications Server 2005 with SP1, also running domain preparation to set permissions.

4.Updating distinguished name (DN) references to the global settings tree.

5.Updating msRTCSIP-PrimaryHomeServer DN references for user, contact, and inetOrgPerson objects.

6.Verifying that the migration was successful.

7.Removing the original global settings tree structure from the System container in the root domain.

1. Migrating the Tree Structure

The MigrateGlobalSettingsTree action of the MigrateOcsGlobalSettings command copies the global settings tree structure from the System container to the Services sub-container in the Configuration container. This step does not copy the global settings attributes because the new

Document info
Document views340
Page views341
Page last viewedThu Dec 08 17:02:55 UTC 2016
Pages123
Paragraphs2763
Words27811

Comments