A move operation includes the movement of all (successful) installation records and corresponding successful activation and configuration records. The installation history of successfully uninstalled software is not moved, and failed activation or configuration records are not moved, because they are not relevant to describe the current status of an agent. The move operation moves only the currently logged in user profile. This ensures that inactive users are not stored in the MDB forever. If the computer has multiple user profiles, you can move the required profiles by logging into each user account that you want to move.
Note: A move can be seen as a rather resource consuming operation, including connecting to the previous domain manager, enumerating all job records, and updating the job history for the target. In the case of a massive move operation covering at least many hundreds of computers, we recommend that multiple targets be moved from the same previous domain manager at the same time, because one connection can be shared for all the moves.
When the agent is reconfigured, it is imperative that the installation records for the agent are moved from the previous to the new domain manager for continued successful management of that particular agent.
A scalability server is not directly involved in permanent moves between domain managers. However, the moving agent can connect to the domain manager through a scalability server, and the scalability server itself can move to a new domain manager.
If a scalability server is moved, every delivery record is also moved. Even though the scalability server objects themselves are moved with their corresponding installation, activation, configuration, and delivery records, the targets connecting through that scalability server are moved on the next successful connection. This means that there can be a considerable time delay between the move of the scalability server and the targets connecting through that scalability server.
A move operation is a transaction. This means, that any failures during a move, like software exceptions or communication errors, will rollback the move operation. A new attempt will be made the next time the computer move operation is run.
For More information about agents and scalability servers move operations, refer to ITCM Implementation Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|