Chat now with support
Chat with Support

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

Moving Computers to Another Domain

Once you have completed the migration of users and collections, you can choose to move the source computers to another target domain. Actions that must be performed in these cases are described in the related topics:

Start Moving Computers

Follow these steps to move computers to another domain in Resource Updating Manager:

  1. In the Resource Updating Manager console management tree right-click the computer you want to move.
  2. Select Create Task | Move in the shortcut menu.
  3. On the Move Options step, specify where and how to move computers. For more details, see Configure Move Computers to Domain Settings.
  4. On the Grant Local Administrator Privileges step, select the accounts that will be added to the local Administrators group on the computers you are going to move.
  5. On the next step, specify when the computer will be restarted to complete the move operation. For more details, see Configure Move Computers to Domain Settings.
  6. On the Advanced Options step, you can use the Perform the task remotely (without agents) option to specify whether you want to use Resource Updating Manager agents for this task. Selecting this option will make sure that agents are not used on the computers where they are installed; instead, the task will be performed directly from the computer where this instance of Resource Updating Manager is installed. If the option is cleared, agents will be used; they will be installed on computers that do not have them.
    If you use agents, you also have the option of running custom scripts locally on the computers before and after the task.
  7. On the next step you can specify when the task starts. You can start the task immediately by selecting the Start now option or select the Start at option to specify the date and time to start the operation.

    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.

  8. On the Task Description step you can specify an optional task description.
  9. Click Finish to start processing.

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).

If there are any shared folders or printers published in Active Directory on the computer being moved to the target domain, they should first be migrated to the target domain along with the computer account they are pointing to using Migration Manager. This will allow Resource Updating Manager to automatically update the resources that reside in the source and target domains after moving the computer to point to the target computer account.

NOTES:

  • If there are only printers located under the computer account, there is no need to migrate them before moving the computer to the target domain. In this case, computer account will be created automatically, the spooler will be restarted and printers will be created pointing to the new account.
  • If a computer account in the source Active Directory has child objects with the Windows BitLocker Drive Encryption recovery information, then identical objects will be created for the corresponding computer account in the target Active Directory.

  • Resource Updating Manager cannot move domain controllers, cluster servers, non-Windows computers, and unknown computers between domains.
  • If you click Cancel during a computer move or stop the service, further processing will be stopped. In this case and in the case when processing is stopped due to an error, computers that have not been moved by that moment will be left intact.
  • See the Moving Exchange Servers to Another Domain topic for information on how to move Exchange Servers.
  • For information on how to move SMS servers to another domain, see the Moving SMS Servers Between Domains technical paper by Microsoft.

Configure Move Computers to Domain Settings

On the Move Options page, select the target domain from the list and the target organizational unit (optional). In addition, you have the following options:

  • Change last logged-in domain to the target domain
    If you want the last logged-in domain in the logon window to be changed to the target domain after moving the computer, select this check box.
  • Preserve computer account in source domain
    To ensure that valid accounts are available for logon in case of problems, select this check box. This option will cause the source accounts to be kept, but disabled.

NOTE: If you do not use the Resource Updating Manager console when moving computers with the Resource Updating agent installed between domains, please consider the following:

  • 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 both in the source and target domains.
  • The Migration Manager RUM Agent service account must have the Logon As Service right in target domain

On the Computer Restart Options page, the following additional settings are available:

  • The message to show to the currently logged-on user when the computer is about to restart.
  • The delay between the message and the actual restart (that is, how much time users have for saving their work).
  • Whether to forcibly close applications with unsaved data during restart.

If you select not to restart the computers after they join a different domain, you will need to tell the users to restart manually.

Moving Exchange Servers to Another Domain

If the target domain has never had an Exchange Server installed in it, you must take the following steps before you move the server. If the target domain already has (or has ever had) an Exchange Server installed, skip these steps.

  1. If you haven't already done so, run DomainPrep in the target domain. This will create the necessary groups for Exchange, including Exchange Enterprise Servers and Exchange Domain Servers.
  2. Use ADSIEdit and browse to Domain.com/Configuration/Services/Microsoft Exchange. Right-click Microsoft Exchange and add the target domain's Exchange Domain Servers group to this container with Read permissions. Make sure that this permission is applied to this object and all child objects.
  3. Browse to the Org container and add the target domain's Exchange Domain Server group with the Create all child objects and Administer information store rights. Again, make sure that this is applied to this object and all child objects.

    NOTE: The above permissions are normally added with the first installation of an Exchange Server to the domain.

  4. Follow the procedures in Microsoft KB article 297295.
Related Documents