Chat now with support
Chat with Support

Migration Manager for AD 8.14 - Resource Kit User Guide

OCSMigrator

The OCSMigrator utility helps you migrate OCS/LCS accounts after you migrate the corresponding Active Directory accounts. The utility also migrates contact lists including groups and block lists.

Caution: The utility does not migrate Access Level settings for the contacts.

To map the accounts, the utility uses the vmover.ini file generated by Migration Manager. All migration parameters are specified in the command line.

OCSMigrator System Requirements

The OCSMigrator utility requires the following:

  • Microsoft .Net Framework 2.0
  • Microsoft Office Communications Server 2007 or Microsoft Live Communications Server 2005
  • Microsoft SQL Server 2000 or higher

Caution: All procedures described below refer to both Microsoft Office Communications Server 2007 and Microsoft Live Communications Server 2005 (unless the certain product is specified explicitly).

The SQL Server hosting migration database must be created manually before you run the utility and must be available for access both from the source and target OCS/LCS servers.

The account under which you run the utility must be a member of the RTCDomainUserAdmins group in the current domain (for LCS 2005) or a member of the RTCUniversalUserAdmins group (for OCS 2007).

Using OCSMigrator

The OCSMigrator utility package includes files as follows:

  1. OCSMigrator.exe (version 8.6.0.1) - OCS/LCS Migrator utility
  2. default.values.txt - text file with object properties' default values; required for migration from LCS 2005 to OCS 2007 (see Importing User Data topic for details)

Using the Utility in Inter-Forest Migration

The utility currently supports for LCS to OCS account migration.

To migrate user accounts, take the following steps:

  1. Export user data to the migration SQL database - for that, run the utility on the source server as described in the Exporting User Data topic.
  2. Generate the mapping file (Vmover.ini) as described in the Generating Vmover.ini File topic.
  3. Import user data as described in the Importing User Data topic; use the –external key. Wait until these changes take effect (you can check the dbo.resource table in LCS/OCS Database).
  4. Import user data once again with OCSMigrator; use the – external key.
  5. Update the contacts that point to migrated users - for that, run the utility locally on each server that keeps user accounts whose contacts must be updated, as described in the Updating the Contacts That Point to Migrated User Accounts topic.

Caution: When supplying command line parameters to the utility, you should enter the same value for <session name> parameter regardless of the use case - export, import, update or cleanup.

 

NOTE: During the first import, a contact list is usually imported only partially, so import should be run once again after LCS/OCS User Replicator processes the objects, and Active Directory replication is complete. During the consequent import, the following messages can appear in the log:

Put MSFT_SIPESUserSetting HRESULT:-1007911672. Exception.

These messages occur due to the attempts to re-create a user account in LCS/OCS; they can be safely ignored.

Using the Utility in Intra-Forest Migration

The utility currently supports for intra-forest migration from LCS to LCS.

To migrate user accounts, take the following steps:

  1. Export user data as described in the Exporting User Data topic.
  2. Generate the mapping file (Vmover.ini) as described in the Generating Vmover.ini File topic.
  3. Delete source user accounts from LCS/OCS.

Caution: Wait for LCS/OCS User Replicator to process the objects and for Active Directory replication to complete.

  1. Import user data as described in the Importing User Data topic; use the –external key and the –sourcesip key.
  2. Wait until these changes take effect (you can check the dbo.resource table in OCS Database).

Caution: Wait for LCS/OCS User Replicator to process the objects and for Active Directory replication to complete.

  1. Import user data once again with OCSMigrator; use the – external key and the –sourcesip key.

Caution: When supplying command line parameters to the utility, you should enter the same value for <session name> parameter regardless of the use case - export, import, update or cleanup.

 

NOTE: During the first import, a contact list is usually imported only partially, so import should be run once again after LCS/OCS User Replicator processes the objects, and Active Directory replication is complete. During the consequent import, the following messages can appear in the log:

Put MSFT_SIPESUserSetting HRESULT:-1007911672. Exception.

These messages occur due to the attempts to re-create a user account in LCS/OCS; they can be safely ignored.

Exporting User Data

To export user data to the migration database, do the following:

  1. Copy the utility to the source OCS/LCS server.
  2. Run the utility from the command line in the following format: 
OCSMigrator.exe -export <session name> -log <logfile.txt> -domain <source domain or dc> -sql <SQL server> -db <Database> [-sqluser <SQL username> -sqlpass <SQL password>]

Where:

  • <session name> - character string identifying current migration, for example: SOURCE_OCS_SERVER-TARGET_OCS_SERVER
  • <logfile.txt> - log file name
  • <source domain or dc> - name of the source domain or DC
  • <SQL server> - name of the SQL server hosting the migration database
  • <Database> - name of the migration database
  • <SQL username> - account name to connect to the SQL Server (If not specified, SQL Integrated Security will be used)
  • <SQL password> - account password
Related Documents