Chat now with support
Chat with Support

Migration Manager for AD 8.14 - 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

Common Resource Update Workflows

This section describes common procedures that help update the resources on different types of production servers after an Active Directory migration. These suggestions will work across the different resource updating wizards:

  • Exchange Processing Wizard
  • Active Directory Processing Wizard
  • SQL Processing Wizard
  • SMS Processing Wizard
  • SharePoint Permissions Processing Wizard

Selecting Objects for Processing Explicitly

By default, a resource processing task processes the resources for all objects migrated by the time the task is created. However, you can manually select objects you want to update the resources for. This is done by creating a custom map for the resource processing task.

To create a custom map

  1. Select the resource processing task under the Tasks node.
  2. Click Select Objects to Process Resources in the right pane.
  3. In the dialog that appears, select the objects you want to update the resources for.
  4. Click OK.

NOTE: A custom map is applied only to the task for which it was created. If no custom map is defined for a task, the resources processed by that task will be updated for all migrated objects.

To delete a custom map

  1. Select the resource processing task under the Tasks node.
  2. Click Delete Custom Map in the right pane. Click Yes.

Delegating Resource Update

In a distributed migration project management model, Migration Manager can greatly facilitate resource update at a site or in resource domains where you cannot get administrative access to computers. Decentralizing resource update is also useful if computers to be updated are located across a slow WAN connection and therefore sending multiple agents, no matter how small, would consume too much of the available bandwidth.

In these scenarios, you can delegate the resource updating tasks to the remote site or to other domain administrators who have the required level of access and are located within an area of good connectivity to the computers to be updated.

Resource update can be delegated by either of the following methods:

  • Creating a setup package for a preconfigured Resource Updating Manager console.
  • Creating a setup package for a resource processing task.
  • Exporting an INI file and performing resource update using this file by running the updating tools in stand-alone mode or running resource update from the command line.

These techniques are described in more detail in related topics.

Resource Update Using Task Setup Packages

If you need to delegate a resource processing task, you can create a setup package for the task. The setup package is a standard MSI installation file. There are two types of the setup packages:

  • Containing the task configuration only—for administrators with Migration Manager installed on their workstations
  • Containing the task configuration and executables needed to run this task—for administrators without Migration Manager installed

To create an MSI installation file, take the following steps:

  1. Right-click the task in Migration Manager.
  2. Click Create Setup on the shortcut menu.
  3. Select the replica of the ADAM/AD LDS instance that contains your migration project.
  4. Specify the output folder for the package.
  5. Select the type of MSI installation package.
  6. Click Start.

When you have successfully created the task setup package, locate the MSI file in the specified folder and send it to the delegated administrator.

The delegated administrator should then install the package and perform the resource processing as specified in the task configuration. He or she cannot change the configuration of the task. Note that the custom packages must be installed using an administrative account with elevated privileges.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating