Migration Manager for AD 8.15 - Resource Processing Guide

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.

Creating an INI File for Resource Update

You can create the INI files for the following resource updating tools:

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

To create an INI file for a resource updating tool

1. In the Resource Updating Manager console, create a new collection or choose an existing one.
2. Right-click on the collection and choose Create Task | Processing. In the Create Processing Task wizard, specify the processing settings you need.
3. Click on the Tasks tab in the right pane.
4. Right-click on the task and select Export Settings to File.
5. Save the INI file in the desired location.

Resource Update Considerations

Here are the factors to keep in mind when doing resource updates:

• The more objects a computer has (in most cases, this means the more files and folders), the longer it takes to process. Thus, it takes much longer to process a file server than a workstation. You may want to perform server processing during non-business hours to ensure that no users are affected by a possible server slowdown.
• Updating file system permissions requires a lot of disk access (I/O) operations and can slow the server for a period of time.
• Each computer in a set is processed by its own agent. Thus, all the computers are processed in parallel and it takes about as much time to process a dozen workstations as a thousand.
  

  Caution: Please consider that when resources are processed remotely, computers are handled in turns. In comparison with agent-based resource processing, remote processing takes significantly more time.

• Expect about 10% (depending on the environment) of your workstations to require troubleshooting due to various reasons: they may be offline, the Server service may not be running, the domain administrators may be absent from the local Administrators group, and so on.

It is recommended that you create separate lists for end-user workstations and servers, and process the workstations first and the servers next.

Active Directory Processing

Access to Active Directory objects is regulated with security descriptors (SDs) and group membership. After migration, the SDs and group membership of all objects must be modified so that the access that was granted to the source accounts is given to the target accounts as well.

Active Directory Processing Wizard allows you to update group membership, linked attributes, and Active Directory permissions to conform to the Active Directory reconfiguration after migration. Active Directory Processing Wizard uses mappings between the migrated source and target accounts stored in ADAM or AD LDS for updating permissions. Active Directory Processing Wizard also allows you to process Microsoft Exchange directory permissions and clean up SIDHistory of the migrated objects.