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

Moving Cluster Servers to Another Domain

To move a cluster server where all nodes are member servers of some domain to a different domain, select all the nodes and move them simultaneously. After a couple of minutes all nodes and the virtual server will appear in the new domain.

NOTE:

  • Moving cluster server to another domain is not supported for Windows Server 2008 or higher.
  • Always move all cluster nodes to the new domain simultaneously. Do not move a virtual server to the new domain.

Resource Updating Manager can process file system permissions, shares, local groups, privileges, registry, cluster shares, cluster database (registry), and cluster printers. Here is the procedure:

  1. Select all of the nodes in Resource Updating Manager.
  2. Specify the processing settings and process the nodes as regular computers. This will process all resources except the cluster shares, cluster database, and cluster printers.
  3. Create the INI file and specify the required options.
  4. Use Vmover with command line options, as follows:
    Vmover.exe /c /system=<Cluster Name> /ini=<Vmover.ini path>

This will process the cluster shares, cluster database, and cluster printers.

NOTE: Vmover will not process a computer if it cannot verify whether it is a cluster server or a virtual cluster server. If the cluster node alias is specified as a computer name, Vmover cannot verify it is a cluster. In all other cases the cluster will be uniquely verified.

Renaming Computers

By default, when computers are migrated from the source to the target domain their names are not changed. However, you can choose to rename the computers in the target domain. For that, perform the following:

  1. In the Resource Updating Manager console management tree right-click the node of the collection or category where you want to run the rename task.
  2. Select Create Task | Rename from the short-cut menu.
  3. On the Old and New Names step, specify pairs of old and new computer names.
  4. On the Computers Restart Options step, specify whether computers should be restarted automatically to complete the rename task. Also, you can specify the following options:
    • 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.
  5. 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.
  6. 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.

  7. On the Task Description step, specify the task description for further reference and then click Next.
  8. Click Finish.

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

Task Scripting

You can create a custom task and run it using the Create Scripting Task wizard. To run the task, perform the following:

  1. In the Resource Updating Manager console management tree right-click the node of the collection or category where you want to run the custom task.
  2. Select Create Task | Scripting from the short-cut menu.
  3. On the Task Scripting step, specify the script to execute on the selected workstations. Click Browse to specify the script file (the following file types are supported: *.vbs, *.js, *.bat, *.cmd, *.ps1).
  4. 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 processing.
  5. On the Task Description step, specify the task description for further reference and then click Next.
  6. Click Finish.

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

Related Documents