Converse agora com nosso suporte
Chat com o suporte

Migration Manager for AD 8.15 - Resource Processing Guide

Introduction to Resource Update Distributed Updates in Resource Updating Manager Common Resource Update Workflows Active Directory Processing Exchange Server Processing SMS Processing SQL Server Processing Cluster Server Migration Command-Line Resource Update SharePoint Processing

Using Preconfigured Resource Updating Manager

In some highly distributed environments, the geographically dispersed administrators in charge of post-migration resource processing can benefit from having a dedicated resource updating console detached from the rest of the migration tools. For such purposes, Resource Updating Manager can package itself into a setup file, which can be sent to any administrator who needs it. The resulting setup file automatically contains all of the relevant configuration for the ongoing migration project, such as the ADAM/AD LDS database connection settings.

To create a dedicated, preconfigured Resource Updating Manager setup file, select Tools | Create Resource Updating Manager setup.

Next, grant resource updating privileges to the user or users that you expect to use the preconfigured console. For that, right-click the Resource Updating node and select Delegate. You will be prompted to specify the account to give the privileges to. Note that a user will not be able to use the console unless they have been granted the privileges in this way.

Before You Update Resources

Before you start processing resources in your network, you should complete the following tasks:

Important: For a successful resource update, trusts should be established between source and target domains.

Obtaining Administrative Rights over the Computers

For a successful resource updating you must have administrative rights over the computers involved in the process.

Resource Updating Manager uses two service accounts when performing resource updating tasks. These accounts are:

  • Migration Manager RUM Controller service account, used to:
    • Run the Migration Manager RUM Controller Service on the console computer
    • Access a computer to install or uninstall the Resource Updating Agent, if no other account is explicitly specified for domain
  • Migration Manager RUM Agent service account used to run the Migration Manager RUM Agent service on the computers to be processed

Caution: Migration Manager RUM Agent cannot work with multiple instances of Resource Updating Manager console or Migration Manager RUM Controller service.

Migration Manager RUM Controller Service Account

By default, the Migration Manager RUM Controller Service uses the auxiliary account. You can change the Migration Manager RUM Controller Service account using the Tools | Manage Controller Credentials option in the Resource Updating Manager console menu.

The Migration Manager RUM Controller service account must have the following permissions:

  • Member of the local Administrators group on the computer running the Resource Updating Manager
  • Full Admin access rights on ADAM/AD LDS database. Right-click the migration project node in the Migration Manager console management tree and select Delegate from the shortcut menu to assign these rights to the Migration Manager RUM Controller service account.

NOTE: By default, the Domain Admins group of the domain the computer is a member of a computer’s local Administrators group. You will get administrative access to the computer if the account you are using is a member of the source Domain Admins group.

Migration Manager RUM Agent Service Account

To specify the Migration Manager RUM Agent service account for Migration Manager RUM agents installed using the Resource Updating Manager console, use the Tools | Manage Domains Credentials option in the console menu.

The Migration Manager RUM Agent service account must be a member of the local Administrators group on the computers running the Migration Manager RUM Agent.

Caution: If the Migration Manager RUM Agent service account is not specified, the Local System account (default) will be used.

Deciding on the Use of Agents

In most situations, resources are updated by Resource Updating Manager agents that are installed locally on the computers you want to process. However, agents are not always required for successful resource update. Resource Updating Manager can perform the necessary operations remotely without agents if the network environment permits this.

The following table shows the differences between the two operation modes:

Comparison Criteria With Agents Without Agents
Resource updating and computer moving works over a firewall Yes No
Network traffic Insignificant High when many computers are processed at once
Additional software needs to be deployed on the local computers Yes, the agent No
NAS resources can be processed No Yes
Recommended for computers that are online only occasionally (for example, laptops) Yes, with group policy or similar methods used for agent deployment No

Agents are installed automatically in the following situations:

  • As part of a computer discovery task (see Discovering Computers for details)
  • When a task with the Perform the task remotely (without agents) option disabled starts running on a computer that has no agent

For details about other ways to install Resource Updating Manager agents, see the next section.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação