To start discovery of a particular computer or collection, right-click it and select Create Task | Discovery.
In the Task Schedule dialog box you can specify when the task starts. You can start the task immediately by selecting the Start now option or select the Start task at option to specify the date and time to start processing. On the same step, you can specify the pending timeout for the task operation in case some computers are not accessible at the task start time (some computers may be turned off, or behind the firewall, or you just deploy an agent to the host via Group Policy, Systems Management Server or manually).
|
NOTE: To decrease network traffic it is recommended that you discover and process your resources during off-peak hours. |
This step is not required, but before you start resource processing you may want to revise your collections, depending on the statistics collected during computer discovery.
Create new collections if necessary, as described in the Specifying the Processing Scope topic, and use drag-and-drop to reorganize computers.
After migrating the Active Directory data of the selected users and groups, you must update resources in Resource Updating Manager for the new users and groups so that they have the same permissions as the corresponding users and groups in the source domain.
|
NOTE: For a successful resource update you must have administrative rights over the computers involved in the process. See Obtaining Administrative Rights over the Computers for details. |
In Resource Updating Manager, updates usually involve the followings steps:
This is done by applying tasks to computer collections. Tasks can be either scheduled or queued directly one after another. If you want to run an uninterrupted series of tasks on a collection, create these tasks for it in the order you want them to run, and use the Start now option as the schedule for each task. Alternatively, schedule these tasks in the correct order with very short intervals between them. This will queue the tasks individually for each computer in the collection.
|
Caution: There is a separate task queue for each instance of Resource Updating Manager. Your Resource Updating Manager console displays tasks created in other console instances, but cannot queue additional tasks after them. |
Note that a queued task will wait for the preceding task to end, but if one of the tasks fails, then subsequent queued tasks will be cancelled.
Follow these steps to process the resources in Resource Updating Manager:
|
NOTE: If you are not using agents (the Perform the task remotely (without agents) option is selected on the Advanced Options step), the same step lets you specify the pending timeout for the task operation in case some computers are not accessible at the task start time (some computers may be turned off, or behind the firewall, or you just deploy an agent to the host via Group Policy, Systems Management Server or manually). If the task is not able to start before the deadline you set, then Resource Updating Manager will cancel this task and all subsequent queued tasks for the inaccessible 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.
For more details, see Configure Processing Settings.
While the resource update is in progress, you can safely quit Resource Updating Manager, because the tasks are performed on the remote computers. As soon as all the agents have finished performing the specified tasks, Resource Updating Manager will collect the logs from the processed computers.
By default, Resource Updating Manager will perform the updates for accounts (also referred to as security principals or objects) that were migrated by Migration Manager for Active Directory.
However, you can manually define the accounts you want to update the resources for. You have two options how to do that:
To manually select accounts to process resources for, right-click the collection or category node in the console management tree and click Operate with Selected Accounts. After that select the specific set of accounts to process.
To specify an account matching file with accounts to process resources for, right-click the collection or category node in the console management tree and click Operate with Accounts from File. In the opened dialog box click Browse and select an account matching file.
The account matching file must contain a list of migration pairs in the following format, one pair per line:
SourceNetBIOSDomainName\SourceUserName,SourceUserSID,SourceUPN,SourceDomainDNSName,TargetNetBIOSDomainName\TargetUserName,TargetUserSID,TargetUPN,TargetDomainDNSName
The following is an example of possible account matching file:
SOURCE1\user1.name,S-1-5-21-sourceUser1SID,user1@source1.principal.name,source1.com,TARGET1\user1.name,S-1-5-21-targetUser1SID,user1@target1.principal.name,target1.com
SOURCE2\user2.name,S-1-5-21-sourceUser2SID,user2@source2.principal.name,source2.local,TARGET2\user2.name,S-1-5-21-targetUser2SID,user2@target2.principal.name,target2.local
|
NOTE: To select all accounts migrated by Migration Manager for Active Directory for updating resources for, you need to right-click the collection or category node in the console management tree and click Update for All Migrated Accounts. Note that current account selection will be lost. |
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center