Assigning a schedule is one of the steps to create a Resource Updating Manager task. In some situations, you may need to run a task immediately instead of waiting for its scheduled time. For that, right-click the task and select Start Now.
Note that tasks are one-off operations. Using the Start Now command resets the task's current schedule so that the task starts straight away. Once the task has started, it cannot be rescheduled any more. If you want to repeat the task later, use a copy of it.
Objects are processed according to the following algorithm:
If you choose to process local profiles, user profiles will be shared between source and target user. No copying of profiles ever occurs.
The processing of Access Control Lists is comprehensive: not only permissions, but also ownership and auditing are processed, which ensures the completeness of the update. A relevant example would be Mac volumes that use ownership to control client access. These volumes are handled correctly by Resource Updating Manager.
Another notable Resource Updating Manager feature is that it will traverse and process all child directories and files, regardless of the ownership and permissions of the parent directory.
The Categories node of the Resource Updating Manager console management tree contains several pre-installed categories which might help you to sort computers and find a particular computer among the processed resources. After a computer was added to any collection under the collections node, discovered, processed (successfully or not), it immediately appears under the corresponding category.
However, actions of the same type will stay unsorted.
To create your own category, right-click the Categories node and select the Create Category option. In the Create Category dialog box provide the name and optional description for new category and configure query settings and node properties.
When creating a category, you actually create an LDAP filter for the ADAM or AD LDS database.
The Migration Manager RUM Controller service stores all information about its functions in its log file. The log file is called RUMController.log and stored in the %ProgramFiles(x86)%\Common Files\Aelita Shared\Migration Tools\Resource Updating folder (on 64-bit Windows) or in the %ProgramFiles%\Common Files\Aelita Shared\Migration Tools\Resource Updating folder (on 32-bit Windows) on the console computer
NOTE: The Discover computer information, Process computer resources, Move Computer to domain and Cleanup computer actions create log files in the %Program Files%\Common Files\Aelita Shared\Migration Tools\Resource Updating\Logs\[computer_name] folder. Use the View Logs option to view these logs.
The Migration Manager RUM Agent service also stores all information about its activity in its log file. This log file is called RUMAgent.log and stored in the %WINDOWS%\Quest Resource Updating Agent folder on the computer where the agent is installed.
As soon as all the agents have finished performing the specified tasks, Resource Updating Manager will collect the logs from the computers. To view the collected logs right-click the computer in the right pane of the Resource Updating Manager console and select View Logs.