When attempting to use Resource Updating Manager (RUM) to update computers, there is a significant delay between when the process is started, and when the agents begin processing data on the computers. It may appear that the agents are not running in parallel, as they may start on some computers earlier than others.
This behaviour can be caused by:
1. Processing computers over a slow network link. Though the files copied usually not large, on slow links (such as 128kbits/sec) it can sometimes take several minutes for the agents to copy and start.
2. If you have a large number of migrated users/groups. The more objects in the ADAM database, the longer it will take RUM to generate its vmover.ini mapping file.
1. If you have a slow network link, you can:
- Deploy a remote RUM instance at the remote location, so that the computers being processed are on the same local LAN. See SOL15336: How to install a second instance of Resource Updating Manager (RUM) for details:
- Pre-deploy the agents on the computers to be processed (Actions->Install Agents). This will reduce the time required to start processing since it no longer has to copy the agents.
2.If you have a large number of migrated users/groups:
If your bottleneck is the generation of the vmover.ini file (you can identify this bottleneck by checking whether the Creating INI file... step is displayed at the bottom of the RUM interface for a long period), you can manually generate an INI, and have RUM use it each time you perform Resource Updating, removing the delay associated with generating the file.
Please note : You must export a new INI file each time that you migrate a new user or group, or that user/groups permissions will not be updated.
To Export an INI file for use with RUM:
- In the main QMM interface, select Tools->Export to->INI file
- Select Resource Updating in the Wizard Name drop-down
- Accept the default path, select the desired options, and click OK.
- Return to RUM, and select Process as specified in the exported INI settings file.
RUM will now use the file you exported, and will not generate a new file each time Start is clicked. If this is still slow, please launch RUM from the direct location by double clicking the RUManager.exe(by default the RUManager.exe is under C:\Program Files\Common Files\Aelita Shared\Migration Tools), not from Migration Manager console.