Connecting for the Move and Moving Target Records
On a successful connection between the two domain managers, the previous domain manager is queried for the existence of a record of the currently processed target (for example, the user account and user profile), as follows:
cla140
On a successful connection between the two domain managers, the previous domain manager is queried for the existence of a record of the currently processed target (for example, the user account and user profile), as follows:
- If the previous domain manager does not hold a record for the target, the move is ignored.
- If the previous domain manager holds a record for the target, a comparison of the reference counters of the two target records is performed. If the previous domain manager stores a newer reference counter, the move is aborted. Otherwise, the move operation continues.
- The attributes of the target on the previous domain manager are not moved, since the ones that were currently reported are assumed to be more up to date.
- If the target record on the previous domain manager is locked by a move operation, a check is made to find out if the two domain managers are waiting to move records between each other. If this is the case, the target with the highest (that is, latest) reference counter is assumed to be valid and the move operation continues, if the current domain manager holds the record. If the move operation on the previous domain manager is waiting to move records from a third domain manager, the move operation is postponed until the other move is completed.
Next, the previous domain manager is inquired for its current time. The returned time is compared with the time of the current domain manager, and the time deviation (time zone) is determined. For every installation record associated with the target on the previous domain manager, a new record is created on the current domain manager, maintaining its completion date and time by applying the calculated time deviation. Any successful activation and configuration records associated with a moved installation record are also moved. Software items not registered in the current domain manager's Software Package Library are marked as detected. The output file is not moved due to performance reasons.
After a successful move of all the records, the target record on the previous domain manager is deleted together with all associated installation, activation, configuration, and un-installation records.
After a move has been successfully performed and completed, the target is unlocked.
The move operation is a transaction. If an error occurs during the move, the whole operation is rolled back to be reattempted the next time the computer move operation is run.