To generate the vmover.ini file, do the following:
|
Caution: If new users or groups are migrated after the file is exported, a vmover.ini file needs to be re-exported in order to contain the new users or groups. |
|
|
To import user data from the migration SQL database to OCS/LCS, do the following:
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:
|
|
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
The following contacts are added to the target user profile:
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.
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:
OCSMigrator.exe -update <session name> -log <logfile.txt> -domain <domain or dc> -sql <SQL server> -db <Database> [-sqluser <SQL username> -sqlpass <SQL password>]
Where:
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>]
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy