After successful resource processing, you can remove any references to the source accounts and then disable or delete the source accounts. Also, you can remove the Resource Updating Manager agent from the processed computers.
Once your users have started to log on under their new accounts in the target domain and are not experiencing any problems with access to resources, you may want to remove unnecessary references to the original source accounts in collections, user rights, and object security descriptors. Take the following steps:
|
NOTE: The Leave Source accounts' permissions check box will have no effect on this operation. |
|
NOTE: After the cleanup, users from the source domain will lose their access rights. If cleanup is done before running Resource Updating Manager with the Reassign local group membership, user rights, and object permissions to target users option selected, there will be no way to get these permissions back, nor will there be a way to reassign permissions to target users. |
Follow these steps to remove the Resource Updating Manager agent from the processed computers:
You can review and edit the schedule and other settings for any task that has not started. For that, right-click the task and select Edit Properties. In addition, you can run any task immediately, regardless of its schedule (see the Running Tasks Immediately topic).
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.
|
NOTE:
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center