Migration Manager for AD 8.14 - Resource Kit User Guide

Generating Vmover.ini File

To generate the vmover.ini file, do the following:

1. In the Resource Updating Manager console, create a new collection.
2. Right-click on the collection and choose Create Task | Processing.
3. In the Create Processing Task wizard, specify the processing settings. Do not start the task.
4. Click on the Tasks tab in the right pane.
5. Right-click on the newly created task and select Export Settings to File.
6. Save the INI file in the desired location as vmover.ini.
7. Open the INI file in any text editor and verify that the settings are accurate and the file contains the desired objects only.
8. Finally, copy the vmover.ini file to the network share specified above.

Importing User Data

To import user data from the migration SQL database to OCS/LCS, do the following:

1. Copy the utility to the target OCS/LCS server.
2. Run the utility from the command line in the following format:

OCSMigrator.exe -import <session name> -map <vmover.ini> -log <logfile.txt> -domain <target domain or dc> -sql <SQL server> -db <Database> [-sqluser <SQL username> -sqlpass <SQL password>] [-pools <pools mapping text file>] [-external] [-default <default.values.txt>] [-sourcesip] [-errorretry <number of retries>] [-errorwait <time interval>]

Where:

• <session name>—character string identifying current migration, for example: SOURCE_OCS_SERVER-TARGET_OCS_SERVER
• <logfile.txt>—log file name
• <target domain or dc> - name of the target 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
• <pools mapping text file>—text file containing pool pairs in the following format: <source pool FQDN> = <target pool FQDN>. Each pool pair you specify must be located in a separate line.

• external—sets whether the source user contacts (pointing to the users of the other domains) must be added to the target user profile
• <default.values.txt>—text file containing default values of the properties that target objects have but source objects have not; this file is required for migration from LCS to OCS because source LCS objects miss some properties that target OCS objects should have.

The file must contain a list of values (one per line) in the following format: <WMI class name>.<property name>=<value>

For example:

MSFT_SIPESUserSetting.EnabledForEnhancedPresence=true

• <-sourcesip>—sets target user's SIP URI to the same value as source user's. This key facilitates intra-forest migration - if used with the utility, then the procedure of updating user data can be omitted.
• <number of retries>—the default number of retries in case of error is 5; you can set a higher value if you get many errors
• <time interval>—the default time interval between retries is 60000 milliseconds (that is, 1 minute); you can set a shorter interval if the import takes too long

The following contacts are added to the target user profile:

1. Contacts pointing to the target users which have matching source users included in the vmover.ini file.
2. If the -external key is used:
   • the source user contacts pointing to the user accounts from other domains, which are not involved in the migration process, and
   • the source user contacts (in the source domain) which are not included in mapping (without any contact modification)

There is no need to run the OCSMigrator utility for every source-target pair. To export users from all the forest pools to the temporary database, run the user data export on one of the servers. Next, run the user data import on one of the servers and specify the source-target OCS/LCS matching in the pool mapping file.

The -pools option is mandatory for the intra-forest migration, otherwise the target users can get into on of the source pools.

During the intra-forest migration an issue may occur when the target users are created, but the corresponding contacts are not processed. This is resulted by the delay in data replication between the OCS/LCS servers. To resolve the issue, wait until the newly created users are available in the OCS/LCS snap-in, and run the utility in the import mode once again on the target OCS/LCS server.

After the computer is moved to the target domain, the user must manually change the OCS server name in the OCS connection settings. This can be done automatically by logon script. The names of the internal and external OCS servers (for the Microsoft Office Communicator 2007) are stored, respectively, in the ServerAddressInternal and ServerAddressExternal values of the HKEY_CURRENT_USER\Software\Microsoft\Shared\UcClient registry key.

Updating the Contacts That Point to Migrated User Accounts

If run with the parameters described in this section, the OCSMigrator utility replaces the migrated source users' SIPs (in the contact lists of all users) with the corresponding target users' SIPs. This operation should be performed right after importing target users' data (see above).

To update the contacts pointing to migrated users, do the following:

1. Copy the utility to the OCS server for which the contacts should be updated.
2. Run the utility from the command line with the following syntax:

OCSMigrator.exe -update <session name> -log <logfile.txt> -domain <domain or dc> -sql <SQL server> -db <Database> [-sqluser <SQL username> -sqlpass <SQL password>]

Where:

Clearing the Migration Database

To clear the migration database, run the utility with the following syntax:

OCSMigrator.exe -delete <session name> -log <logfile.txt> -sql <SQL server> -db <Database> [-sqluser <SQL username> -sqlpass <SQL password>]